SAP ABAP IMG Activity MMSRV_SM_ARCHIVE (BAdI: Service Master Check Prior to Archiving)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
MM-SRV (Application Component) External Services
⤷
MASB (Package) Service master

⤷

⤷

IMG Activity
ID | MMSRV_SM_ARCHIVE | BAdI: Service Master Check Prior to Archiving |
Transaction Code | S_AC0_52000630 | (empty) |
Created on | 20050302 | |
Customizing Attributes | MMSRV_SM_ARCHIVE | Service Master Check Prior to Archiving |
Customizing Activity | MMSRV_SM_ARCHIVE | Service Master Check Prior to Archiving |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | MMSRV_SM_ARCHIVE |
Use
This Business Add-In (BAdI) is used in the component External Services Management (MM-SRV).
This enhancement enables you to apply your own usage checks and thus specify the criteria for the archiving of a service master record yourself. If a service master record fails to satisfy your self-defined criteria, its archiving will not be allowed.
The method Service Master: Prevent Archiving Steps (CHECK_ARCHIVABLE) is executed during the archiving process.
Requirements
You should run the usage checks only if archiving is active for the service master record.
Standard settings
In the standard system, the BAdI is not active.
The BAdI is not filter-dependent and is usable multiple times.
Activities
- After invoking the IMG activity, you are first presented with a dialog box, in which you can enter a name for the implementation.
Enter a name for the implementation in the Implementation field and confirm your input with Adopt. - If implementations have already been created for this BAdI, they are shown in a further dialog box. Choose Create in this box. The initial screen for the creation of BAdI implementations appears.
- Enter a short text for the implementation in the appropriate field.
- Choose the Interface tab page.
The system generates the name of the implemented class on the basis of your implementation. You can change this class name. - Save your input and make the assignment to a development class.
- Position the cursor on the method in each case and branch to method processing by double-clicking.
- Enter your desired code between the statements method <interface name>~ <name of method>. and endmethod.
- Save and activate your code and navigate back to the Change Implementation screen.
- On the Change Implementation screen, with the aid of the activation, you can stipulate as of when the newly created implementation is to be valid.
- Save your input.
- When the application program is executed, the code you created is not run through until you activate the implementation via the relevant button. You can carry out the activation either immediately or at a later point in time.
Example
See also:
Methods
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 | MMSRV_SM_ARCHIVE | 0 | HLA0100762 | Master Data |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20050302 |
SAP Release Created in | 600 |