Start of Content Area

Function documentation Production Process Model Plans for CDP and Block Planning  Locate the document in its SAP Library structure

Use

You can display the BOM and routing of the R/3 system in production process model plans in SAP APO.

Note

In Characteristics-Dependent Planning (CDP), components are all elements or parts of a PPM plan, for which you can define characteristics propagation. Activities are also regarded as components.

If you are working with PPM plans, you use the characteristic propagation to define at which characteristics the values are copied from the configuration.

The object dependency in the ERP system at BOMs and routings is not transferred to the PPM plan. Therefore, you should not use an object dependency at APO-relevant components or operations. If you wish to carry out preliminary costing, you must create a separate costing BOM/routing.

Note

When transferring PPM plans for product variants, the object dependency is evaluated. Only the required components/operations are integrated in SAP APO. In each case, you should check if processing with CDP is required.

If you delete or replace components in BOMs or operations in the routings in the ERP system and transfer these changes to SAP APO, dependent CDP data are also deleted with the corresponding nodes in the PPM plan. The same applies to changed key dates in validities in BOMs and routings. In these cases, you must subsequently maintain the CDP data in SAP APO. If you make frequent changes to the BOM or routing in the ERP system, you can also use production data structures (PDS) instead of PPM plans.

Prerequisites

You have specified that you want to work with PPM in SAP APO when creating an integration model in the ERP system (plug-in).

The same prerequisites as described in Planning with CDP Characteristics are valid for characteristics-dependent planning.

The same prerequisites as described in Block Planning are valid for block planning.

Features

Define Characteristics Propagation

The class assignments for components and activities are displayed on the overview screen for characteristics propagation.

You define which characteristics are used for CDP for the output product. For logical components and the activities, you specify characteristics whose values are copied from the configuration by the system.

You can define valuations and characteristic requirements for characteristic propagation:

·        For characteristics selected under Valuation, the system copies the values from the configuration and uses them for pegging or for creating orders.

·        For characteristics selected under Characteristic Requirements, you can define selection criteria that the system uses for pegging. The characteristics must be defined as batch selection characteristics in a class of class type 023 in the ERP system (see Define Characteristic Requirements). If characteristic requirements have been defined, the system will not consider any entries made under Valuations during pegging. The receipt requirements must be compatible with the requirements valuation.

Define Rules

You use rules to control the selection of operations, activities, modes, and logical components that are required for the planned production step. These form the actual items of the production order that was created by the PPM (without access to the liveCache).

In the PPM plan, rules replace the object dependency that is required in the PPM plan.

The system takes the rules into account during the plan explosion.

Overwrite Planning Parameters

You can overwrite certain planning parameters for operations, modes, activities and logical components. To do so, you must define the value and class assignments of the next highest PPM level.

You can overwrite the following parameters:

PPM Level

Planning Parameters

Operation

Sequencing

Activity

Duration (must be entered in seconds for immediate transfer to the liveCache)

Scrap

Mode

Duration

Primary Resource (multi-activity resource)

Consumption of resources (capacity requirements)

Product

Material consumption for the respective product (component requirements)

 

 

 

End of Content Area