The Interface Between Cost Center Accounting and Production Plan (SAP Library

The Interface Between Cost Center Accounting and Production Planning (PP)

Use

This interface enables you to transfer the following data from Production Planning by plant, as plan figures to Cost Center Accounting and Activity-Based Costing:

Activity quantities from plan orders in requirements planning
Activity quantities from simulated plan orders from a planning scenario in long-term planning
Activity quantities from Sales & Operations Planning (SOP) orders in an SOP version

Prerequisites

You need to define the activity types in the work centers.

For the activity types, you need to maintain formulas for cost calculation in the work center.

You need to maintain the transfer control. (See also: Transferring Production Activity Requirements)

Features

The SAP R/3 System calculates these activity quantities using the routing or master recipe, which is structured by cost center / activity type. When activity quantities are transferred, each plan or SOP order is scheduled, and the activity quantities are assigned to one or more CO periods depending on the order dates.

This graphic is explained in the accompanying text

Activity quantities are determined in the work centers using activity types and related formulas. The activity quantity requirements determined in long-term planning are taken into account by the system when it reconciles the activity requirement with the activity provided by the cost centers/business processes. The SAP R/3 System uses the planned activity quantities and the planned costs to calculate the prices of the activity types. These prices are then used for product costing.

If you transfer the activity requirement from the SOP, then the system schedules and evaluates the production quantities created in the SOP using the routings or rough-cut planning profiles. It does this for the activity requirement calculation of each cost center.

Note

Using SOP for transferring activity requirements is recommended only under certain conditions for the following reasons:

It is not possible to assign resources to cost centers or activity types in the rough-cut planning profile. You cannot transfer data from rough-cut planning profiles.
The scheduling is set up so that the system ignores any additional work centers that the rough-cut planning profile may have. In this case, no activity quantities can be transferred.
The system does not determine any secondary requirements from BOMs in the SOP.

If you transfer the activity requirement from the SOP, then the system uses the routings to schedule and evaluate the plan orders for make-to-order production in long-term or requirement planning. It does this for the calculation of the activity requirement.

Note

As there is not yet any operative data in materials planning for annual planning in the planned year, it is normally not possible to transfer activity quantities from a requirements plan.

If you transfer the activity requirement from long-term planning then the system controls the transfer using a planning scenario. The planning scenario contains the planning timeframe and the plant in which planning was executed.

The activity requirements of long-term planning are not automatically updated in Cost Center Accounting and Activity-Based Costing. After the planning results have been reconciled, you can transfer the data to Cost Center Accounting and Activity-Based Costing using a special planning function.

Note

You should prioritize long-term planning when collecting activity quantities for Cost Center Accounting. If you want to use SOP, you should transfer the data from the corresponding SOP version to long-term planning, and then from there to Cost Center Accounting.

The SAP R/3 System determines the secondary requirements of activity quantities based on simulated planned orders. These orders create the long-term plan during a planning run or during multilevel planning for meeting these requirements.

Therefore, you need to execute a planning run or a multilevel single-item planning every time the primary requirements are changed. This ensures that the secondary requirements are updated.