Ansicht
Dokumentation

APO_SPP_SOR_MANORD - BAdI: Surplus and Obsolescence Approval - Manual Orders

General Data in Customer Master   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

The Business Add-In (BAdI) /SAPAPO/SOR_MANORD is used in the Service Parts Planning (SPP) application component.

You can use this BAdI

• To define which follow-on activities you want the system to execute for the surplus decision codes that you defined.

You create surplus decision codes in Customizing for Advanced Planning and Optimizationunder Supply Chain Planning -> Service Parts Planning -> Surplus and Obsolescence Planning -> Define Surplus Decision Code.

For surplus quantities to which you have defined a surplus decision code other that "scrap", there are no follow-on activities implemented in the standard system. The system collects these surplus quantities in a list that you can see on the SAP Easy Access screen under Advanced Planning and Optimization -> Service Parts Planning -> Planning -> Inventory Planning -> Surplus and Obsolescence Planning -> Surplus Quantities to Be Processed Manually. However, you can only process the quantities listed here if you have implemented this BAdI and thus defined follow-on activities.

• To categorize a quantity that is displayed on the Surplus Quantity to Be Processed Manuallyscreen (/SAPAPO/SPPMSP) either as a scrap order quantity or as a demand over the product life cycle. This information is displayed in the Type column.

You can access the Surplus Quantity to Be Processed Manually screen on the SAP Easy Access screen by choosing Advanced Planning and Optimization -> Service Parts Planning (SPP) -> Inventory Planning -> Surplus and Obsolescence Planning.

The BAdI is not active in the standard system.

The BAdI is not filter-dependent.

The BAdI is not designed for multiple uses.

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.

This BAdI uses the interface /SAPAPO/IF_EX_SOR_MANORD. For more information, display the interface in the Class Builder.

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

Length: 4486 Date: 20240524 Time: 005613     sap01-206 ( 80 ms )