In Release 4.5A, the
product cost collector in the Product Cost by Period component replaces the production cost collector as the cost-collecting object. In contrast to the production cost collector, the product cost collector is used not only in repetitive manufacturing but also for production orders in order-related production and for process orders in the process industries.
Product cost collectors are always created for a production process. Production processes and their associated production alternatives determine which characteristics define the quantity structure for procurement of a materials through production. These characteristics are determined in naming rules for the production processes or production alternatives. Release 4.5A supplies a standard naming structure that contains three naming rules for production:
XPRA converts the existing production cost collectors into product cost collectors. The standard naming structure is assigned to each plant in which the production cost collector is used. If there is more than one production cost collector for a material/production version, the system selects those to be converted into product cost collectors using the following strategy:
During conversion, the affected material is assigned to a naming group. As the naming rule, the system uses the rule that determines the material number and production version as the naming characteristics. In exceptional cases (production cost collectors for valuated sales order stock or for KANBAN control cycles with corresponding cost collector search strategy) the generic rule that only contains the material number as the name-forming criterion is used.
A production process with a production alternative is created for each converted production cost collector. Any existing 1:1 links between run schedule headers and production cost collectors are deleted - that is, the run schedule header number is deleted from the production cost collector.
The settlement rules of the converted production cost collectors are changed to default rule "with strategy" and the strategy is changed to the value 5 (delivery value with product cost collector).
In addition, in the cost object hierarchy those hierarchy nodes that contain the production version are linked to the affected process. The associated production process and the production alternative are created if necessary. The hierarchy nodes that contain a run schedule header number are also linked to the associated process and the run schedule header number is deleted from the hierarchy node.