成本滚算层级-Phantom Item Cost Is Not Rolling Up At End Item Cost (文档 ID 1184492.1)

摘自：https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=175601123787976&id=1184492.1&_adf.ctrl-state=j43v3z73c_52

 

Phantom Item Cost Is Not Rolling Up At End Item Cost (文档 ID 1184492.1)

转到底部

---

In this Document   Symptoms   Cause   Solution   References   APPLIES TO: Oracle Cost Management - Version 12.1.1 and later Information in this document applies to any platform. SYMPTOMS On : 12.1.1 version, Miscellaneous When attempting to roll up Item cost, the following error occurs. ERROR ----------------------- An invalid account is associated with the item being transacted. failure:Ele_Acct( 110 ): An invalid account is associated with the item being transacted. STEPS ----------------------- The issue can be reproduced at will with the following steps: 1. Responsibility: Cost Management 2. Supply Chain Costing 3. Supply Chain Cost Rollup 4. Supply Chain Cost Rollup - Print Report CAUSE The customer is missing Patch 7271694 in their 11.5.10 instance. The following justifies how the issue is related to this specific customer: The functionality is correct. It has been the right and designed system behavior for a long time. . Note phantom is a special sub-assembly and its routing cost is directly exploded under the final assembly as this-level cost. If you have a lot-based resource under a phantom, it should inherit the final assembly's lot size in calculating its contribution to the final assembly's cost. The phantom's lot size and phantom's quantity should not have an effect on a lot resource's cost to the final assembly. This is explained in the following bug: Bug 10014225 - PHANTOM ITEM COST IS NOT ROLLING UP AT END ITEM COST SOLUTION The functionality is correct. It has been the right and designed system behavior for a long time. . Note: Phantom is a special sub-assembly and its routing cost is directly exploded under the final assembly as this-level cost. If you have a lot-based resource under a phantom, it should inherit the final assembly's lot size in calculating its contribution to the final assembly's cost. The phantom's lot size and phantom's quantity should not have an effect on a lot resource's cost to the final assembly. The following example illustrates the design logic: . ass_1 (Final Assembly), Lot Size: 30, Resource Used: 10Hr @$10/Hr ass_2 (Phantom Sub Assembly), Lot Size: 20, Resource Used: 10Hr @$10/Hr ass_3 (Phantom Sub Assembly), Lot Size: 10, Resource Used: 10Hr @$10/Hr . Lets say the BOM looks like: ass_1 --> 5(ass_2) ass_2 --> 5(ass_3) . The correct resource cost at the final level(ass_1) should be: ass_1: $100.00/30 + 100/30.00 + 100/30.00 = 10.00 . In the customer's example, your phantom's lot size is 5000, so the lot-based resource cost for the phantom itself is: 3.60*24.67/5000=0.01776 . However, the final assembly's lot size is 1, so the lot-based resource cost for the final assembly should be converted back to (note a component yield of 0.98): 0.01776*5000/0.98=90.61224 . If you meant to achieve the same result of this lot-based resource for the final assembly as the phantom, you should set the final assembly's lot size to be the same as 5000 instead of 1. . The functionality is that for a lot-based resource under a phantom, it should inherit the final assembly's lot size in calculating its contribution to the final assembly's cost.   REFERENCES BUG:10014225 - PHANTOM ITEM COST IS NOT ROLLING UP AT END ITEM COST NOTE:429153.1 - Material Transactions with Error CSTPLCIN.COST_INV_TXN An Invalid Account Is Associated With The Item Being Transacted