Kontakt

Ansicht
Dokumentation

BADI_GPD_01 - Add-In: Check Whether Goods Movement Allowed

BADI_GPD_01 - Add-In: Check Whether Goods Movement Allowed

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In verifies whether the chosen movement type is supported by the GPD processes.

Example

A customer-specific enhancement could, for example, be the check whether goods issue takes place as scheduled or unscheduled or whether goods receipt is posted with reference to a purchase order or a production order. A message can be displayed or, in the case of an error, posting can be avoided.

In the standard set-up this Business Add-In is activated.

The default code is executed automatically when there is no active customer implementation.

The Business Add-In is neither filter-dependent nor multiple use.

The Business Add-In is implemented using the default implementation class CL_DEF_IM_BADI_GPD_01. This class contains one public instance method.

Public instance method:,,CHECK_MOVEMENT_TYPE

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.






CL_GUI_FRONTEND_SERVICES - Frontend Services   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 3110 Date: 20240607 Time: 184240     sap01-206 ( 46 ms )