Show TOC

 Preliminary Cost Estimate for Product Cost Collector Locate this document in the navigation structure

Use

You can use this function for make-to-stock repetitive manufacturing if you produce a material in one period using several production versions each with different routings. This function allows you to create a preliminary cost estimate per production version, creating the reference to the appropriate routing.

If you do not use this function, the system uses the standard cost estimate per period for the activity backflush. The standard cost estimate can only have one routing. If you work with several production versions and each production version has a different routing, this can lead to considerable differences between planned and actual costs.

Integration

The function is only available in the main Repetitive Manufacturing menu, but it can also be used for KANBAN.

Prerequisites

In the repetitive manufacturing profile, you must define that the activities are to be posted with reference to the preliminary cost estimate data for the product cost collector.

Features

You can create a preliminary cost estimate for every production version. The system then uses these specific cost estimates for the activity backflush. This means that different routings defined in the production versions are taken into account in the activity backflush.

Note Note

When carrying out the preliminary cost estimate, the system copies the routing which it then uses later in the activity backflush.

End of the note.

For more information, see also Preliminary Costing for the Product Cost Collector in the SAP documentation CO Cost Object Controlling .

Activities

Creating preliminary cost estimates for production versions

If you set the repetitive manufacturing profile to backflush activities using the preliminary cost estimate per production version, the system asks you whether it is to create a cost estimate for the production version automatically when creating the run schedule header.

A cost estimate can also be created when changing a run schedule header. Here, you must trigger the creation of the cost estimate by choosing   Edit   Cost.  

If no product cost collector exists for the run schedule header or if no run schedule header exists (for example, in KANBAN procedures), the system cannot create the cost estimate automatically. In this case, you have to use the CO transactions to trigger the creation of the cost estimate when manually creating or changing the product cost collector.

Creating/updating preliminary cost estimates collectively

A function also exists for collectively creating cost estimates for production versions. This function is also used to update existing cost estimates since changes to routings are not automatically updated in existing cost estimates .

To create or update cost estimates collectively, proceed as follows:

  1. Starting from the Repetitive Manufacturing menu, choose   Environment   Prelim. cost estimate for product cost coll.  

  2. The selection screen appears.

  3. Enter the selection criteria and choose Execute .

The cost estimates are created in the background. The system issues an appropriate message log.