Show TOC

Function documentationConverting Production Cost Collectors into Product Cost Collectors

 

Product cost collectors are available from Release 4.5A onwards. In earlier releases, the costs of repetitive manufacturing materials were collected on production cost collectors. From Release 4.5A onwards, production cost collectors are converted into product cost collectors.

Prerequisites

You were using repetitive manufacturing in a release before 4.5A. Only production cost collectors without a deletion indicator are converted.

Features

The conversion process uses XPRA RK_PKOSA_MLMV_X1. The conversion process converts the production cost collectors into product cost collectors. A production process is generated for each product cost collector. Default rule PP2 (Production Material Periodic Settlement) of the production cost collector is converted into default rule STR (strategy for tracing factor determination). This default rule is specified in Customizing for Product Cost by Period under Start of the navigation path Product Cost Collector Next navigation step Define Default Values for Order Types End of the navigation path in all relevant order types. The settlement rule for the product cost collector specifies the distribution rule 100% to material with settlement type PER (periodic).

<4.5A: Run Schedule Header with Automatic Creation of Production Cost Collector (Cost Collector Type PCC)
Initial situation in releases before 4.5A:

Each run schedule header has only one production cost collector assigned to it. There is therefore a one-to-one correspondence between production cost collectors and run schedule headers.

Conversion

For each production version for which run schedule headers exist, a production cost collector is converted into a product cost collector. The Controlling level of the production process is the production version. If there is more than one run schedule header for a production version, the validity periods of the run schedule headers determines which run schedule header is used.

  • The product cost collector was created for the current run schedule header. A run schedule header that only becomes valid in the future specifies the product cost collector that was created for the current run schedule header.

  • If there are future run schedule headers but no current run schedule header, the system converts the production cost collector of the run schedule header that is chronologically the closest. Any run schedule headers that are further in the future are linked to the converted product cost collector.

  • If there are neither current nor future run schedule headers, the production cost collector with the most recent previous run schedule header is converted.

    Note Note

    To execute the period-end closing activities, enter the number of the material, plant, and production process. To identify the relevant production process, use the possible entries function (F4). Use the possible entries function to determine the production process for the run schedule header number.

    The material, plant, and production process are also shown in reports in the information system.

    End of the note.

If you want to manufacture a new material in repetitive manufacturing after conversion, create a product cost collector for the material. It is recommended that you use the Controlling level Production Version for the product cost collector.

<4.5A: Run Schedule Header with Manual Creation of Production Cost Collector (Cost Collector Type PKMN)
Initial situation in releases before 4.5A:

You may have created production costs collectors of cost collector type PKMN with or without a version for a material. More than one run schedule header can be assigned to a production cost collector if the cost collector type is PKMN. In this case there is a 1:n correspondence between the production cost collector and the run schedule header.

Conversion

The system checks whether a current run schedule header exists. If no current run schedule header exists, the system checks whether a run schedule header with future validity exists. If no future run schedule header exists, the system uses the most recent run schedule header from the past.

If the system finds a production cost collector with version for the run schedule header, the Controlling level Production Version is used.

If the system finds only production cost collectors without a version and no production cost collectors with a version, the Controlling level Production Plant/Planning Plant is used – provided that the combination material/plant/production version is not assigned to any existing cost object hierarchy. If the combination material/plant/production version is assigned to a cost object hierarchy, the Controlling level Production Version applies to this material.

If there are both production cost collectors with a version and production cost collectors without a version, the system checks whether a current production cost collector with a version exists. If the system finds a production cost collector with a version, the production cost collector is converted into a product cost collector with the Controlling level Production Version. If the system cannot find a current production cost collector with a version but does find one without a version, it is converted into a product cost collector with the Controlling level Production Plant/Planning Plant. Production cost collectors whose validity does not start until the future then reference this <versionless> product cost collector even if the production cost collectors were originally created with reference to a version.

The XPRA searches first for current, then for future, then for the most recent past product cost collectors using the described logic. The XPRA first converts the production cost collector with a version into a product cost collector using the Controlling level Production Version.

With version

Without version

Current

1

2

Future

3

4

Past

5

6

1, 3 and 5: the system generates a product cost collector with the Controlling level Production Version.

2, 4 and 6: the system generates a product cost collector with the Controlling level Production Plant/Planning Plant.

If all or some of the criteria are met, the conversion rule that corresponds to the smallest number entered is used.

<4.5A: Run Schedule Header with Discrete Run Schedules (Cost Collector Type SA)
Initial situation in releases before 4.5A:

More than one production order is assigned to a run schedule header. The costs are collected on the production orders.

Conversion

No conversion takes place. It is recommended that you use product cost collectors in the future.

<4.5A: Production Cost Collector for Material in Sales Order or Project Stock (4.0A and 4.0B)

The system converts the existing production cost collector into a product cost collector for material with the Controlling level Production Plant/Planning Plant.

<4.5A: Kanban Production Cost Collectors
Initial situation in releases before 4.5A:

A kanban production cost collector exists.

Conversion

If a current kanban production cost collector exists, all run schedule headers are in the past, and you have specified cost collector type PKMN and cost collector search strategy <Material>, then the production cost collector is converted into a product cost collector with the Controlling level Production Plant/Planning Plant.

If these requirements are not met, existing kanban production cost collectors are converted into product cost collectors with the Controlling level Production Version.

More Information

For information on XPRA RK_PKOSA_MLMV_X1 refer to the report documentation for the XPRA.

For information on the default rule STR, see the IMG of Product Cost Controlling under Start of the navigation path Product Cost Collector Next navigation step Define Default Values for Order Types End of the navigation path.

For information on converting cost object hierarchies, refer to the following section:

Conversion of Cost Object Hierarchies