Professional Documents
Culture Documents
Cost Rollup Basics: Author: Laura Miller
Cost Rollup Basics: Author: Laura Miller
The Phantom assemblies can be the parent assembly as well as the child
assembly. The cost rollup can include the resources and overheads from
both levels.
There are two Bill of Material parameters that are used to allow the Phantom
assemblies to be included in the cost rollup:
Inherit Phantom Operation Sequence - this parameter controls the
inheritance of the parents operation sequence;
Use Phantom Routings - this parameter determines if the resources and
overheads are recognized for costing
If these parameters are changed after a job is created and a rollup or an
update occurs, incorrect variances can be created.
Performance issues:
Cost rollup takes hours to complete
Apply patches 464107 and 674267. Apply these patches in this order to get
to later versions cstcsrol.sql and cstrbicr.rdf. Then rerun cost rollup.
If still having problems, check the extents size for the tables. If at 50 when
the error occurred it can be safely set to about 121.
If still having problems, get trace file with timed statistics. Verify the
expected performance.
Common Cost rollup errors:
MSG-01999 BOMPCEXP ORA-6502
REP-1825 Before report trigger returned False
APP-969 Program was terminated by Signal 1
APP-1825 Concurrent manager got error
These errors can indicate that max extents need to be increased.
MSG-01999 CST_LOCK_FAILED_CCID
REP-1825 Before Report trigger returned false
These errors indicate that the cost tables have a lock on them. Clear the
locks and rerun the cost rollup.
Only one cost rollup can occur at a time. If multiple rollups for single items are
being run in parallel, this error will occur repeatedly.
If trying to run two or more rollups at the same time, while one of the rollups
has the tables locked, the other rollup will wait and try to lock the table 10 times
and then error out.
Cost Rollup and Indented Bill of Materials are designed to run together but
there can be overlap of the clearing of the temp tables that can cause the tables to
lock and the error to occur.
Troubleshooting
No Cost for Manufactured Items:
Check these: BOM/Routing exists for the item
ItemCost screen Based on Rollup = Yes
Inventory Asset Value = Yes
WIP = Build in WIP = Yes (Org)
Item Attributes Main Status = Active (or similar)
Costing Cost Enabled = Yes (Master)
Item assigned to organization
No Cost for Purchased Items:
Check these:
ItemCost Screen enter a pending cost and perform a standard
cost update
if unable to enter pending cost, set Use Default
controls = NO and then enter a pending cost
and run standard cost update again.
BOM Structure be sure the Include in Rollup flag is checked
**if transactions exist for the item, then you will not be allowed to enter a frozen
(standard) cost***
Doubled Costs:
If there are costs in the (previous level) and in the user defined section
(this level), costs can double.
This happens if you change a cost type for an item from based on rollup
to not based on rollup and you don't delete the previous level costs, then
when you add your user defined costs (this level), you will get both costs
rolled up together.
One way to remove the rolled-up costs from the previous level is to set
Based on Rollup to YES, click on save, then set Based on Rollup = NO.
At this point you will be asked if you want to delete the rollup costs, click
on yes. Now you should have only your user defined costs(this level).
If they both say the same value (i.e. Active) then when Cost Rollup
runs, that item will be skipped. However, you could run the
Rollup for that specific item and it will work.
The easiest way to fix this problem is to change status for the bom
parameter to some other code (i.e. obsolete or inactive for instance).