Calculation per production version
Up until now, it was only possible to backflush standard activities according to the standard cost estimate. This meant that during the backflush, the system always used the routing entered in the standard cost estimate (only one standard cost estimate is possible per period). In certain circumstances, this could lead to considerable variances between planned and actual costs.
It is now possible to create a standard cost estimate for each production version. This is controlled by the repetitive manufacturing profile. Here, you use the control parameters to control:
If you have set the first instance, the system will ask you whether a cost estimate is to be created for the production version when creating a run schedule header. When changing a run schedule header, you must trigger the creation of a cost estimate by selecting, Edit -> Cost estimate.
In this context, another function also exists that you can use to collectively create cost estimates for production vesions. This function is also used to update already existing cost estimates as changes to the routings are not automatically updated in the cost estimates. You can also use this function in KANBAN production procedures.
The CO transactions you use to automatically create or change cost
collectors are also adjusted. This means that a function has been introduced
that you can use to trigger the creation of cost estimates. These transactions
can also be used in repetitive manufacturing as well as in KANBAN production
procedures.
Default values for cost object controlling
The default values for cost object controlling were enhanced by the costing variant for the planned costs.
You make these settings in the Implementation Guide.
Cost estimage per production version
Function in Customizing for repetitive manufacturing
Proceed
Function in Customizing for Controlling
Proceed
Costing variant for planned costs
Function in Customizing for repetitive manufacturing
Proceed
Function in Customizing for Controlling
Proceed