Hierarchy

⤷

⤷

IMG Activity
ID | IERI_INST_REMOV_SAVE | BAdI: Actions Before/After Saving (Database Update) |
Transaction Code | S_ALN_01001054 | SAPLS_CUS_IMG_ACTIVITY |
Created on | 20020211 | |
Customizing Attributes | IERI_INST_REMOV_SAVE | BAdI: Actions Before/After Saving (Database Update) |
Customizing Activity | IERI_INST_REMOV_SAVE | BAdI: Actions Before/After Saving (Database Update) |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | IERI_INST_REMOV_SAVE |
Use
This Business Add-In (BAdI) was designed for multiple uses within transaction IE4N. This means that you can create several active implementations, which can all be processed. However, the processing sequence is not defined, therefore you cannot implement any interdependent steps.
Documentation for BAdI methods:
- Actions before installation (database update)
- Actions before removal (database update)
- Actions after installation (database update)
- Actions after removal (database update)
Requirements
Standard settings
Recommendation
Activities
After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.
If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:
- In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.
The screen for creating BAdI implementations is now displayed.
- Enter a short text for the implementation in the Short text for implementation field.
- From the tab index, choose Interface.
The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.
- Save your entries, and assign the implementation to a development class.
- Place the cursor on the method, and double-click to enter method processing.
- Enter the code for the implementation between the statements
method <Interface name> ~ <Name of method>
andendmethod
. - Save and implement your code. Return to the Edit Implementation screen.
- Save the entries on the Edit Implementation screen.
Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.
- Choose Activate
The code you stored in the method will be run when the application program is executed.
Example
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 1 | 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 | IERI_INST_REMOV_SAVE | 0 | HLA0006642 O | |
SIMG | IERI_INST_REMOV_SAVE | 1 | ALR0000082 | Basic Data |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20020314 |
SAP Release Created in | 110 |