Convert the Configuration Scheme 

Use

You can use the report /SAPAPO/CONFR_CFGREL_MAINTAIN to change the configuration scheme of the system or remove the setting for selected products.

This may be necessary if the business model is to be changed or the configuration scheme was not sufficiently considered while setting up the system. The report is intended for the project phase and is time-intensive.

The report removes all configuration and CDP data from the relevant objects, and specifies data that you must postprocess manually. You normally need to carry out additional process steps after the report has been executed.

The configuration scheme conversion can have serious effects on the system data; you should therefore only carry out the report after checking the data carefully!

Data may be lost when you convert the configuration scheme. You must postprocess master and transaction data of your products manually.

Do not execute the report during processing; this prevents any possible changes being made to the master and transaction data during the conversion.

The report supports the following three scenarios:

·        Remove the settings for certain products

This may be necessary to delete the class assignment to products if classes were transferred incorrectly from the R/3 system.

·        Convert the client from Variant Configuration (VC) to Characteristics-Dependent Planning (CDP)

·        Convert the client from CDP to VC

Prerequisites

Before conversion, you must remove active ATP visualization profiles as well as characteristics-dependent planned independent requirements at orders as these cannot be converted automatically.

Before converting the data, the report runs a where-used list. The where-used list contains a detailed list and evaluation of the data found.

Bestimm...

The configuration scheme can only be converted if the where-used list was run with the maximum scope of the check and no data inconsistencies were found.

Features

Convert CDP to VC

Scope of Check

·        The report checks for transaction data with characteristics-dependent forecasting and active ATP visualization profiles.

·        CDP data at transaction data are deleted.

The characteristics requirements and value assignments at orders or stocks cannot be used for the setting VC.

·        The system logs the use of production data structures (PDS).

·        The report checks the product usage in PPM plans with characteristics propagation and deletes the characteristics propagation.

You should use production data structures for setting VC. However, you can continue working with PPM plans that had configuration data removed.

The system cannot convert a PPM plan into a PDS.

·        The system deletes the class assignment with class type 400.

·        The settings at the product are removed.

·        The VC indicator is set in the product master if the product is marked as configurable in the product master.

There can be no assignment of a class with class type 400.

·        The CDP-relevant data is deleted from the pegging areas.

·        The configuration scheme is changed to VC in Customizing for the entire system if all checks were successful.

Manual Postprocessing

·        The class assignment and configuration data of products must be transferred from the R/3 system.

·        Check if you can replace the PPM plans with production data structures.

It is recommended to transfer a PDS from the R/3 system for the setting VC, or to generate a PDS from iPPE in APO.

·        The transaction data (such as orders with configuration) must be transferred again from the R/3 system.

Convert Configuration Scheme from VC to CDP

Scope of Check

·        The report checks for transaction data with characteristics-dependent forecasting and active ATP visualization profiles.

·        VC data at transaction data are deleted.

The report deletes references to configuration data.

·        The system logs the use of production data structures (PDS).

·        The settings at the product are removed.

·        The configuration scheme is changed to CDP in Customizing in the entire system.

Manual Postprocessing

·        Transfer the products again from the R/3 system to SAP APO. The products are assigned a class with class type 400 in SAP APO.

·        Check if the system is to generate a PPM plan or PDS for the product master data. If you are working with PPM plans, you must maintain the characteristics propagation.

·        The transaction data (such as orders with configuration) must be transferred again from the R/3 system.

Remove Configuration Relevance for Certain Products

·        The report checks for transaction data with characteristics-dependent forecasting and active ATP visualization profiles.

·        CDP and VC data at transaction data is deleted.

·        The system logs the use of production data structures (PDS).

·        The system checks the usages in PPM plans and deletes the characteristics propagation.

The characteristics propagation is deactivated for output components.

The system checks if there are parameters or rules for input components. The Only Rules/Params indicator is set (see Define Characteristics Propagation). If there are no rules or parameters, the characteristics propagation is deleted.

·        The variant configuration is deleted from the product master.

·        The system deletes the class assignment with class type 400.

·        The settings at the product are removed.

·        The CDP-relevant data is deleted from the pegging areas.

Manual Postprocessing

·        Check the consistency of the master data (PPM plan or PDS).

·        The transaction data (such as orders with configuration) must be transferred again from the R/3 system.

Actions

Choose Advanced Planning and Optimization → APO Administration → Reorganization → Production Planning → Convert Configuration Relevance for Products, and specify the required data.