SAP ABAP IMG Activity PLM_AUDIT_COR_UPDATE (Create, Change, and Delete Actions)
Hierarchy
☛
SAP_ABA (Software Component) Cross-Application Component
⤷
CA-AUD (Application Component) Audit Management
⤷
PLM_AUDIT (Package) Audit Management: Other Components

⤷

⤷

IMG Activity
ID | PLM_AUDIT_COR_UPDATE | Create, Change, and Delete Actions |
Transaction Code | S_ABA_72000210 | (empty) |
Created on | 20041213 | |
Customizing Attributes | PLM_AUDIT_COR_UPDATE | Create, Change, and Delete Actions |
Customizing Activity | PLM_AUDIT_COR_UPDATE | Create, Change, and Delete Actions |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | PLM_AUDIT_COR_UPDATE |
Use
You can use this Business Add-In (BAdI) or the corresponding methods to enter all changes to a corrective/preventive action (create, change, delete). You can then use it to replicate the changes in another system.
You can process changes at the following points in time:
- AT_SAVE
The user has called the function Save in the dialog. At this point in time, you can implement still implement a check of the data to be saved. If errors are found during this check, this information can be returned. The data is not saved and the user is informed. - BEFORE_UPDATE
The call is performed immediately before the data is updated. No messages can be output at this point. The save cannot be stopped. - IN_UPDATE
The call takes place during the update process. No messages can be output at this point.
Requirements
Standard settings
This BAdI is not active in the standard system.
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
See also:
Methods
- Create Action When Saving
- Create Action Before Update Task Is Called
- Create Action in Update Task
- Change Action When Saving
- Change Action Before Update Task Is Called
- Change Action in Update Task
- Delete Action When Saving
- Delete Action Before Update Task Is Called
- Delete Action in Update Task
- ########################################################################
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 | PLM_AUDIT_COR_UPDATE | 0 | AEC0000474 | Audit Management |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20050209 |
SAP Release Created in | 700 |