Define cost collector strategy

In this step, you define which cost collector is to be used for backflushing per repetitive manufacturing profile and production type. At the moment, you can create cost collectors per material or per material and production version.

The following is valid for production type 01 (repetitive manufacturing):

• If the cost collector order type PKSA is assigned to the repetitive manufacturing profile, then no search strategy is required as for each run schedule header only one cost collector is created automatically by the system.
  

• If the cost collector order type PKMN is assigned to the repetitive manufacturing profile, you must use the search strategy to define which cost collector is to be used. The following strategies exist:
  

• Settlement of run schedule headers by one common cost collector, that is, all run schedule headers for one material are settled via one cost collector.
  

• Settlement of run schedule headers via several cost collectors, that is the run schedule headers for one material and one production version are settled per version using several cost collectors.
  

The following is valid for production type 03 (Kanban):

• Irrespective of the cost collector order type of the repetitive manufacturing profile, you must define the search strategy for the cost collector. Here, you also have the option of assigning production costs per material or per material and production version to the cost collector.
  

A similar solution will be available in future for the production type 02. At the moment, the costs for assembly orders are only settled via sales order CO objects. That is, entries for production type 02 are not used initially.

Activities

Define the cost collector search strategy per repetitive manufacturing profile and production type.

Further notes