Ansicht
Dokumentation

R3CIF_PUBCUSTORD - BAdI: Influence Publication of Sales Orders

CL_GUI_FRONTEND_SERVICES - Frontend Services   CPI1466 during Backup  
This documentation is copyright by SAP AG.

The Business-Add-In (BAdI) /SAPAPO/SMOY_PUB_APP can be used in a number of application components. You can use the BAdI to publish data from SAP APO via the APO Core Interface (CIF) to SAP R/3 that is not published as a default. This can be customer-specific data, as well as data that exists in SAP APO but which as a default is not transferred to SAP R/3.

The additional data is transferred in special parameters that are not filled or fully defined in the standard. To define the structure of the additional data you must first create customer includes. You can determine the names of these customer includes by navigating to the parameter of the current method. The names of the parameters reserved for customer enhancements end with APP, for example ORDER_HEADER_APP or ORDERHEADAPP.

The methods of this BAdI are called immediately before the corresponding method of the BAdI /SAPAPO/SMOY_ADAPTER, which is executed as a default when data is published. The names of the methods that correspond to one another start with APPEND (BAdI /SAPAPO/SMOY_PUB_APP) and PUBLISH (BAdI /SAPAPO/SMOY_ADAPTER).

For further information see the documentation on the individual methods:

• Influence Publication of Reservation Data

Documentation on the BAdI method APPENDRESERVATION

• Influence Publication of Scheduling Agreement and Shipping Plan

Documentation on the BAdI method APPENDDELIVERYPLAN

Documentation on the BAdI method APPENDSHIPPINGPLAN

• Influence Publication of Sales Orders

Documentation on the BAdI method APPENDCUSTOMERORDERPLAN

• Influence Publication of Sales Scheduling Agreements

Documentation on the BAdI method APPENDCONFSCHEDAGRMT

• Influence Publication of Planned Independent Requirements

Documentation on the BAdI method APPENDPRIMARYDEMANDPLAN

• Influence Publication of Procurement Scheduling Agreements

Documentation on the BAdI method APPENDPURCHASINGPLAN

• Influence Publication of Production Backflush

Documentation on the BAdI method APPENDAUTOCONFIRMATION

Documentation on the BAdI method APPENDAUTOCONFDELETION

Documentation on the BAdI method APPENDAUTOREPPOINTS

This BAdI is not active as a default.

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   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 5729 Date: 20240523 Time: 193348     sap01-206 ( 77 ms )