First, I'll say, I'm am not a JDE user nor am I an accountant, but my position is responsible for the costs in the system. It has come to my attention that when a change is made to Component A's routing, which changes it's cost, the Simulated cost of Component A changes but the frozen (standard) does not until the user rolls and freezes it. However, if you then freeze the Standard Cost on the Parent Part that has Component A in it's BOM, Component A will automatically be rolled and frozen to the simulated costs! The way JDE is working the standard cost is meaningless, as every time a new assembly is created the Standard Cost of it's components are potentially being automatically reset! Is this JDE's design on do we have options set to cause this to happen? This is unlike any system I have ever dealt with. JDE's Simulated cost is what I would call a Current Cost but it should not be the Standard Cost for the remainder of the year. In previous systems I've worked with you always have to roll from the lowest part up if you want all Current Costs captured. A Standard Cost is golden and is not to be changed at whim.