Ansicht
Dokumentation

R3CIF_APOCIF - BAdI: Influence Order-Specific Inbound Processing

Fill RESBD Structure from EBP Component Structure   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Influence Order-Specific Inbound Processing

You can use this Business Add-In (BAdI) to

• Define that the activity dates are retained

• Switch off proportional quantity adjustment

• Change planned and manufacturing orders in SAP APO after merging with the liveCache data

The BAdI is used in the application component Interfaces (SCM-APO-INT).

The BAdI comprises the following methods:

• Decision to Adopt Activity Dates/Times per Order (ORDER_INB_PROCESSING_DECIDE)
  The method is called in SAP APO in the function module /SAPAPO/DM_ORDER_MERGE_CIF_APO before R/3 data is merged with liveCache data, before the order data is posted in the liveCache.

• Decision for Quantity Adjustment and Fixing of Activities (ORDER_INB_REDET_DATES_DECIDE)
  This method is also called before R/3 data is merged with liveCache data.

• Adjustment of APO Data After Comparison with CIF Data (ORDER_INB_MODIFY_AFTER_MERGE)
  The method is called in SAP APO in the function module /SAPAPO/DM_ORDER_MERGE_CIF_APO after R/3 data is merged with liveCache data, before the order data is posted in the liveCache.

• Adjustment of X Fields for Relationships
  The method is called per order before relationships are created in function module /SAPAPO/DM_ORDER_MERGE_CIF_APO.

The BAdI is not active in the standard system.
The BAdI is reusable.

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.

To see example coding for the method ORDER_INB_REDET_DATES_DECIDE or ORDER_INB_PROCESSING_DECIDE, choose Goto -> Example Coding.

For example coding, to transfer a change of work center that has been made in SAP R/3 to SAP APO using the method ORDER_INB_MODIFY_AFTER_MERGE for example, see SAP Note 629366 or the notes relevant to the BAdI.

Methods

Decision to Adopt Activity Dates/Times per Order (ORDER_INB_REDET_DATES_DECIDE)
Documentation

Decision for Quantity Adjustment and Fixing of Activities (ORDER_INB_PROCESSING_DECIDE)
Documentation

Adjustment of APO Data after Reconciliation with CIF Data (ORDER_INB_MODIFY_AFTER_MERGE)
Documentation

Adjustment of X Fields for Relationships (ORDER_INB_REL_X_CHANGE)
Documentation

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

Length: 5352 Date: 20240523 Time: 203908     sap01-206 ( 60 ms )