Ansicht
Dokumentation

FVD_ALOI_CLERK - BAdI: Determine Activity Type for Administrator

General Material Data   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

This Business Add-In (BAdI) is used in the Loans Management (FS-CML) component, and is only deployed when reading from and writing to the index table Loans: Search Index for Correspondence (Document Finder) (VDCORR_ALOI).

An administrator can either be stored as an administrator in the table VDZSB or as a business partner in the table VDGPO.
To read the table VDZSB you need an activity type (such as P for rollover, for example). In order to read the business partner you also need the corresponding role category. You will find both fields in the IMG activity Define Activity Type.

You can use this BAdI in conjunction with a particular correspondence type to determine which activity type is used to read the IMG activity Define Activity Type. This also determines whether the respective administrator has been stored as an administrator or as a business partner.

If no correspondence type is indicated, the system selects a random data record from the IMG activity Define Activity Type. This enables you to determine whether the administrator is normally stored as a business partner in table VDGPO or as an administrator in table VDZSB.

The Business Add-In is active in the standard system. The default coding is carried out automatically.

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.

Methods

Determine Activity Type and/or Role Category

CL_GUI_FRONTEND_SERVICES - Frontend Services   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 3831 Date: 20240523 Time: 194947     sap01-206 ( 62 ms )