Ansicht
Dokumentation

DEP_STORE_BA_010 - BAdI: Control of Locking Procedure for Plants

DEP_STORE_BA_010 - BAdI: Control of Locking Procedure for Plants

Addresses (Business Address Services)   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

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.

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).

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.

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.

Method CHANGE_PLANT_BLOCKING






ROGBILLS - Synchronize billing plans   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 3906 Date: 20240606 Time: 071315     sap01-206 ( 67 ms )