Ansicht
Dokumentation

APO_SDP_PA_COPY - Copy/Version Management

APO_SDP_PA_COPY - Copy/Version Management

Vendor Master (General Section)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

Use this Business Add-In (BAdI) to modify data when copying from one planning area to another or from one version to another.

The BAdI consists of four methods

CHANGE_DATA_AFTER_READ

In this method, the selection and grouping conditions (aggregated level) can be changed after the data are loaded from a planning area. If they are changed in the tables CT_SELECTION_FR and CT_GROUP_BY_FR, the combination values in the table CT_PLOBV must be updated by calling the function module '/SAPAPO/TS_DM_MASTERDATA_GET'. The planning object IDs and key figure values should be updated in the tables CT_LINES_FR and CT_TAB_FR.

Sample coding is available for this method.

CHANGE_QUANTITY _UNIT

In this method, converting the quantity unit can change the key figure values in the table CT_TAB_TO. If the quantity unit is changed, the flag CV_CHANGE_UNIT must be set to 'X' so that the standard conversion of quantity unit is not executed.

The messages from the implemented BAdI (Table ET_MSG_TAB) can be saved in the application log.

MAP_DATA

If the source and target planning object structures are different, the data must be mapped. After that, the selection and grouping conditions (aggregated level) can be changed again. If they are changed in the tables CT_SELECTION_TO and CT_GROUP_BY_TO, the combinations values in the table CT_PLOBV_TO must be updated by calling the function module '/SAPAPO/TS_DM_MASTERDATA_GET'. The planning object IDs and key figure values should be updated in the tables CT_LINES_TO and CT_TAB_TO.

If the flag CV_CHANGE_COMBI is set as 'X', the consistency is checked after the changed data are sent back to the main program. The performance should be considered if this flag is set as 'X'.

The messages from the implemented BAdI (Table ET_MSG_TAB) can be saved in the applica-tion log.

CHANGE _DATA_BEFORE_SAVE

In this method, the key figure values can be changed in the table CT_TAB_TO before they are saved in a planning area.

The messages from the implemented BAdI (Table ET_MSG_TAB) can be saved in the applica-tion log.

The BAdi is not active in the standard system

The BAdi is not filter-dependent

The BAdi cannot be used more than once.






General Data in Customer Master   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 2492 Date: 20240524 Time: 002757     sap01-206 ( 54 ms )