Hierarchy

⤷

⤷

IMG Activity
ID | SIMG_ICL_HI_CHECKKEY | BAdI: Define Foreign Key Relationships for Display of Change History |
Transaction Code | S_ANI_08000789 | (empty) |
Created on | 20050311 | |
Customizing Attributes | SIMG_ICL_HI_CHECKKEY | Display of Change History |
Customizing Activity | SIMG_ICL_HI_CHECKKEY | Display of Change History |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | ICL_HI_CHECKKEY_GET |
Use
You can use this Business Add-In in the display of the change history to create external key relationships between two tables that have no foreign key definition with one another in the data dictionary.
The system uses the determined foreign key to assign the associated objects to the right claim subobject in the display hierarchy of the change history and display them there.
The BAdI is called for each entry in the change history.
Requirements
Standard settings
The BAdI has default coding. If no active implementation exists, this default coding is processed.
The BAdI is not filter dependent.
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.
Example
You can use this BAdI, for example, to assign question sequences of structured facts capture to the right subclaim or right claim item.
See also
Method:
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 | 20050406 |
SAP Release Created in | 600 |