Hierarchy
⤷ FS-CML (Application Component) Loans Management
⤷ FVVD_CORR_PRINT (Package) Loans: Central Modules for Correspondence Tool
IMG Activity
ID | FVD_ALOI_CLERK | BAdI: Determine Activity Type for Administrator |
Transaction Code | S_ALN_01002343 | (empty) |
Created on | 20030416 | |
Customizing Attributes | FVD_ALOI_CLERK | BAdI: Determine Activity Type for Administrator |
Customizing Activity | FVD_ALOI_CLERK | BAdI: Determine Activity Type for Administrator |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | FVD_ALOI_CLERK |
Use
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.
Requirements
Standard settings
The Business Add-In is active in the standard system. The default coding is carried out automatically.
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.
See also:
Methods
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 |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | FVD_ALOI_CLERK | 0 | HLA0100077 | Correspondence |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20030416 |
SAP Release Created in | 200 |