Ansicht
Dokumentation

R3CIF_ORDERCHG - BAdI: Create SNP Planned Orders From R/3 and Change Category

Vendor Master (General Section)   PERFORM Short Reference  
This documentation is copyright by SAP AG.

This BAdI allows the category assigned by the system to be changed, if planned orders are transferred in an initial data transfer from SAP R/3 to SAP APO and are created as SNP planned orders.

SAP APO creates SAP R/3 planned orders that fulfill specific prerequisites as SNP planned orders. The category EE is automatically assigned to the receipt for the primary product in the SAP APO inbound. The category EM is assigned to the co-products and the category EL is assigned to the dependent requirements.

If an individual planning area with different categories for primary product, co-product, or dependent requirement is used for planning, you have to replace the automatically assigned category with the other category used. You use this BAdI to do this.

Only change the category if you are using a planning area that varies from the standard, and in which a category other than the standard category is assigned to the primary product, co-product, or dependent requirement of the planned order. You should be aware that errors can arise in planning if you use this BAdI to assign the SNP planned orders a category other than the one defined in the planning area for the SNP planned orders.

An active integration model for planned orders must be available in SAP R/3.

The indicator Create Planned Orders as SNP Planned Orders must be set in the Activate or Deactivate Integration Model screen (transaction CFM2) in SAP R/3.

The BAdI is not active in the standard system.

After you have called the IMG activity, proceed as follows:

1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.

If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.

1. In the corresponding field, enter a short text for implementation .
2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
3. Choose the tab Interface.

The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.

If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.

1. Save your entries and assign a package.
2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
4. Save and activate your coding, and navigate back to the screen Change Implementation.
5. Save on the screen Change Implementation.

Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.

1. Choose Activate.

When the application program is executed, the coding you have created will be run.

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

Length: 3887 Date: 20240523 Time: 215711     sap01-206 ( 69 ms )