Kontakt

Ansicht
Dokumentation

/SAPAPO/CONFR_CFGREL_MAINTAIN - Convert Configuration Scheme

/SAPAPO/CONFR_CFGREL_MAINTAIN - Convert Configuration Scheme

rdisp/max_wprun_time - Maximum work process run time   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

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

This can have a variety of reasons, such as when the business model is to be changed, or the effects of the configuration scheme were not taken into consideration when the system was first structured. This report is time-consuming and intended for the project phase.

The report removes all configurations and CDP data from the relevant objects, and lists the data that must be postprocessed manually. Generally, you will need to carry out additional processing after the report has been executed.

Warning:
You should only carry out the report after checking the data carefully because the conversion of the configuration scheme can have serious effects on the data in the system!
Converting or removing the configuration scheme can lead to loss of data. You will need to postprocess the master and transaction data of your products manually or transfer these again from an external system.
Make the necessary adjustments in the integration models of the ERP system (plug-in) before the conversion is carried out; this will prevent a new initial data transfer from resetting the status of the master data before the conversion was carried out.

In particular, check the filter object settings for classes and characteristics.

Do not execute the report while the system is running; this will prevent master data and transaction data from being changed during the conversion.

The report supports the following three scenarios:

  • Remove the configuration relevance for specific products
This may be required to delete the class assignments to products if the classes were transferred incorrectly from the R/3 system.
  • Convert the client from VC to CDP
  • Convert the client from CDP to VC

Integration

Prerequisites

Before conversion, you must remove active ATP characteristic views and characteristic-dependent planned independent requirements at the orders as the views and requirements cannot be converted automatically.

The plan explosion in the product master cannot be set to Matrix Explosion.

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

The configuration relevance can only be converted when the where-used list is run using all available checks of the where-used list, and no data inconsistencies were found.

Features

The report covers the following:

  • Check for existing transaction data with characteristics-based forecasting and active ATP characteristic views.
  • Delete CDP data at transaction data.
The characteristic requirements and value assignments at orders or stock cannot be used for the setting VC.
  • Log the PDS usage.
  • Check the product usage in PPM plans with characteristic propagation, and delete the characteristic propagation.
It is recommended to use production data structures when using the setting VC. However, you can continue working with PPM plans where the configuration data was removed.
The system cannot convert a PPM plan into a PDS.
  • Delete class assignments for class type 400.
  • Remove the configuration relevance at the product.
  • The VC indicator is set in product master if the product in the product master is marked as configurable.
In order to do so, there must be no assignments to a class with class type 400.
  • Delete CDP-relevant data from the pegging areas.
  • Change the configuration relevance to VC in Customizing in the entire system if all checks were successful.

Manual postprocessing:

  • Transfer the class assignment and configuration data for the products from the R/3 system.
  • Check if the PPM plans still need to be used, or if these can be replaced by production data structures.
It is recommended to transfer a PDS from the R/3 system when using the setting VC, or to generate a PDS from iPPE in APO.
  • Transfer the transaction data (such as orders with configuration) from the R/3 system again.

The report covers the following:

  • Check for existing transaction data with characteristics-based forecasting and active ATP characteristic views.
  • Delete VC data at transaction data.
The report deletes the references to the configuration data.
  • Log the PDS usage.
  • Remove the configuration relevance at the product.
  • Change the configuration relevance to CDP in Customizing for the entire system.
  • Note: The system does not generate any planning file entries for changed objects.

Manual postprocessing:

  • Transfer the products again from the R/3 system to SAP APO. The products are assigned to classes with class type 400 in SAP APO.
  • Check if you need to create a PPM plan or a PDS for the master data of a product. If you are working with PPM plans, you may need to maintain the characteristic propagation.
  • Transfer the transaction data (such as orders with configuration) again from the R/3 system.

The report checks the following:

  • Check for existing transaction data with characteristics-based forecasting and active ATP characteristic views.
  • Delete CDP data and VC data at transaction data.
  • Log the PDS usage.
  • Check PPM plan usage, and delete the characteristic propagation.
The characteristic propagation is deactivated for output components.
The report checks if parameters or rules exist for input components. Then the Only Rules/Params indicator is set. If there are no rules or parameters, the characteristic propagation is deleted.
  • Delete the variant configuration from the product master.
  • Delete class assignments with class type 400.
  • Remove configuration relevance from product.
  • Delete CDP-relevant data from the pegging areas.
  • Note: The system does not generate any planning file entries for changed objects.
Manual postprocessing:
  • Check the master data for inconsistencies (PPM plan or PDS).
  • Transfer the transaction data (such as orders with configuration) again from the R/3 system.

Standard Variants

Output

Activities

Example






BAL_S_LOG - Application Log: Log header data   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 8055 Date: 20240418 Time: 215036     sap01-206 ( 91 ms )