Hello,
I added 2 fields to the BOM Listing report where it shows the Std Total Cost and Last Total cost for each child part. Now I am asked to also show the parent total costs.
I did a sum of the lines for the parent but the costs do not add the same as what I see on the part tracker Costs tab.
Is there a way to reference the parent part’s costs showing in the PartCost table without doing a sum?
Any help is appreciated.
Thanks,
Shawn
The SUM of (Component’s Std Costs x Qty) might not equal the Std Cost of the parent, if the Cost rollup has not been done since any component part price has changed.
As for Last Cost, the parents Last Cost only gets updated when Inventory trans happen (or a manual cost adj). The SUM of (Component’s Last Costs x Qty) will only equal the Parents Last Cost, if the exact BOM was issued to the job, then the Parent received into stock. With no changes to the last costs of the components since they were issued to the job.
And how dow you want to handle multi-level BOM’s? Should the parent cost use the sub-assy’s costs, or the sum of the sub-assy’s components?
And why do you need to know both Std and Last? You should only be using one or the other.
Not really sure why they want last, was just asked to do it.
Is there a way to get the parent part cost to show also without calculating from the sub parts?
The Cost for the Parent is in the cost file as well. If you’re talking about the top level parent that is from PartCost where PartCost.Partnum = PartMtl.Partnum
The components are from PartCost where PartCost.Partnum = PartMtl.MtlPartnum
And FWIW - one would be interested in the costed BOM based on LAST cost, as that would most accurately show what the costs are. If the STD cost was calculated and set on Jan 1st, then a price increase happened to a component, you’d not see it in the costed BOM. That cost difference would appear as a MFG VAR, As the STK-MTL put more costs to the job than the STD cost of the parent part. Those extra $$ need to be accounted for.
The Cost for the Parent is in the cost file as well. If you’re talking about the top level parent that is from PartCost where
PartCost.Partnum = PartMtl.Partnum
The components are from PartCost wherePartCost.Partnum = PartMtl.MtlPartnum
I knew that. I just don’t know how to do both at once.
Any ideas?
I don’t think you can add the same table twice to an RDD. If you could you’d just add PartCost again, and link the Partnum to the Partnum.
The more I think of this, all of this might already exist in the Cost Roll-up processing. I think you can run a cost roll-up without actually updating the STD cost, and it shows the difference (I think).
That’s true. I think the only way you could do this is by storing the costs in multiple tables and then using a different table for each level in the report (thats a huge undertaking). You could also do a BAQ and use subqueries. Lastly, you could edit the report to directly connect to SQL and get the PartCost data for each level that way.
I think this would be a nice feature request, if Epicor could modify RDD to allow linking of the same table twice… or allow subqueries. It would not be a small task for sure.
Anyway, how about creating a dashboard or BAQ report for this? might save quite a bit of pain
I think the ability to handle an unkown number of BOM levels is what makes this most difficult. If you’r willing to set a limit on the number of levels, the BAQ wouldn’t be that hard.
But for every level your BOM has, you end up with many possible costs for the parent. Because each sub-assy can have its own cost, and the cost of the sum of its components. And if any of those are sub-assy’s, the can multiple costs, which cascade back up the BOM
For example
Part PAR-001 may have a STD cost of $110.
But if you sum up the STD cost of the level 1 parts ($10+15+90), you get $115
Now if you re-calc the costs for the Level 1 parts based on their componets, you get ($10 + $15 + ($20 + $22 + $50)) = $117
And going one more level down …
($10 + $15 + ($20 + $22 + ($23 + $30))) = $120