Show TOC

Component documentationCharacteristics-Dependent Planning (CDP) Locate this document in the navigation structure

 

You can use characteristics-dependent planning (CDP) to plan in-house production for products using characteristics. The products are configurable in the ERP system. You can configure planned orders and production orders for these products in SAP APO. The system includes the configuration when planning and consume requirements with the matching receipts (production orders, purchase orders, purchase requisitions, batch stock).

Example Example

There is an incoming sales order from the ERP system for the product Pipe that has the value red for the characteristic Color and the value 100 for the characteristic Length. In SAP APO, you have already created a production order for this material with the same valuation. If the sales order is now planned in SAP APO, the sales order is consumed with the production order.

End of the example.

CDP supports both make-to-order production and make-to-stock production.

Implementation Guidelines

You have created a configuration model in the ERP system that you can use for CDP in SAP APO. The classes and characteristics must exist in SAP APO. You should transfer the classes and characteristics from the ERP system to SAP APO, in order to ensure that this data is consistent in both the ERP and SAP APO system (see Transferring Classes and Characteristics).

You can use production data structures (PDS) or product process model plans (PPMs) as the source of supply for in-house production. These structures are used to map the BOMs and routings of the ERP system in SAP APO. In the integration model, you define which structure you would like to use (see Productions Process Model Plans for CDP and Block Planning and Production Data Structures (PDS) for CDP and Block Planning).

Constraints

  • If the components for subcontracting are planned with CDP, the characteristic values are not transferred to the ERP system.

  • Reference characteristics: It is necessary to transfer characteristics first, and then BOM and routings. It is therefore not possible to read SAP APO master data information in the BAdI implementation.

  • The use of different configuration schemes (CDP and Variant Configuration) within one client is not released except on request. With this function, the classification system can be defined on the product level; however, it is not possible to use VC below a component with CDP classification.

  • The integration of VC characteristics, both for the mixed scenario and for the VC-only scenario, requires an SAP ERP Release 4.6B or higher. In the delta report, the classification is verified for:

    • VC - regarding the same configuration reference

    • CDP - regarding the existence of characteristics

  • It is possible to perform an extended configuration check for the classification with the effect that the value of the characteristics is checked as well.

  • Consistency check in liveCache (Transaction OM17):

    • Consistency of information for characteristics-based time series is not checked.

    • Some checks do not prove full consistency, but only carry out important plausibility checks.

    • Checks for VC only apply to the active planning version (planning version 000).

    • Correction of inconsistencies may require subsequent execution of CIF delta report. There is no link between this function and CIF delta report.