Hierarchy

⤷

⤷

IMG Activity
ID | PPC_RESERV_DISTRIB | BAdI: Distribution of Post-Processing Records in Other Systems |
Transaction Code | S_KA5_12001283 | (empty) |
Created on | 20021122 | |
Customizing Attributes | PPC_RESERV_DISTRIB | BAdI: Provide Backflush Data in DB Table Form |
Customizing Activity | PPC_RESERV_DISTRIB | BAdI: Provide Backflush Data in DB Table Form |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | PPC_RESERV_DISTRIB |
Use
This Business Add-In (BAdI) is used in component Production Backflush (IS-A-PPC).
If some goods movements - synchronous and asynchronous - cannot be posted during a production backflush, postprocessing records are generated for the failed goods movements. These represent order-neutral dependent requirements. You can postprocess the failed goods movements at a later point in time, once the error has been fixed.
If dependent requirements have been created, changed or deleted, you can transfer the records for these dependent requirements with this Business Add-In (BAdI) PPC_RESERV_DISTRIB
.
Requirements
Standard settings
The Business Add-In is not active as standard.
The Business Add-In is filter-dependent.
The Business Add-In can be used in on multiple occasions.
Recommendation
Activities
After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.
If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:
- In the dialog box, enter a name for the implementation of the Add-In and choose Create.
The system displays the initial screen for creating Business Add-In implementations. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
- Save your entries and assign the Add-In to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the
method <Interface Name>~<Name of Method>.
andendmethod.
statements. - Save and activate your code. Navigate back to the Change Implementation screen.
Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step: - Choose Activate.
When the application program is executed, the code you created is run through.
If you want to use the filter functions of the Business Add-In, enter the desired filter specifications for the implementation.
Note that the Business Add-In can be used multiple times and therefore all active implementations are called and run through.
Further notes
Documentation for BAdI methods:
Create / change / deletion of postprocessing records in SAP APO
You can also call the documentation on the BAdI method via the menu, by carrying out the following steps:
- Choose the tab page Interface.
- Double-click on the relevant method.
- Click on the right mouse button and choose Component documentation.
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | PPC_RESERV_DISTRIB | 0 | KA50000071 | Production Backflush |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20030120 |
SAP Release Created in | 471 |