Hierarchy
EA-RETAIL (Software Component) SAP Enterprise Extension Retail⤷
LO-MD-MM (Application Component) Material Master⤷
WRF_DEPARTMENT_STORE (Package) Department Store / Shops
IMG Activity
| ID | WRF_DEP_STORE_BA_010 | BAdI: Control of Locking Procedure for Plants |
| Transaction Code | S_XB4_60000175 | (empty) |
| Created on | 20040519 | |
| Customizing Attributes | WRF_DEP_STORE_BADI | BAdIs for Department Store/Shops |
| Customizing Activity | WRF_DEP_STORE_BA_010 | BAdI: Control of Locking Procedure for Plants |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | BLOCKING_PLANT_E |
Use
This Business Add-In (BAdI) is used in the Plant Master (LO-MD-PL) component.
You can use IMG activity General Logistics -> Plant Master -> Control -> Reasons for Blocking to define reasons for blocking; in turn, these reasons can be saved for a plant in plant master maintenance to block that plant for a certain period. You can define application-specific reasons for blocking for each reason to determine which applications are affected (and how) by each reason. The defined block is also evaluated in the allocation table and listing checks; however, the application-specific definition is not possible here. This means you cannot define a reason for blocking that only affects the allocation table check and/or listing check.
To correct this, you can this BAdI to control in detail how the system responds to the individual reasons for blocking within the allocation table check or listing check.
The BAdI is called in the allocation check and the listing check.
Requirements
Before you can define an implementation for the BAdI, you have to define the reasons for blocking in Customizing (so you can refer to them in the implementation).
Standard settings
The BAdI is not active in the standard system. If no active customer implementation exists, there is no default coding that is executed.
The BAdI is not filter-dependent.
The BAdI does not support multiple use.
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.
Also see:
Example
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20040519 |
| SAP Release Created in | 111 |
