Hierarchy
⤷ PM-EQM-CC (Application Component) Configuration Control
⤷ DI_CCM (Package) Configuration Control
IMG Activity
ID | BADI_CCM_INSTALL_CHK | Add-In: Perform All Checks During Equipment Installation |
Transaction Code | S_KA5_12001074 | (empty) |
Created on | 20010903 | |
Customizing Attributes | BADI_CCM_INSTALL_CHK | Perform All Checks During Equipment Installation |
Customizing Activity | BADI_CCM_INSTALL_CHK | Perform All Checks During Equipment Installation |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | BADI_CCM_INSTALL_CHK |
This is the main ("master") BAdI that is called before the equipment installation is performed. This exit is the correct place to implement all types of checks and validations that should be processed before an installation might be posted. The different types of check are also represented internally by BAdIs, which are called within this main BAdI.
Example
You want to perform a local configuration check against an MPL structure prior to the installation of an equipment. Therefore, you have implemented the BAdI BADI_CCM_I_STRCT_CHK (Structure check for Installlation). You can use the default implementation of CCM_INSTALL_CHK, which calls the structure check BAdI. With a customer-specific implementation of CCM_INSTALL_CHK you can control which sub-routines (see BAdI documentation) should be performed in which sequence for an installation
Requirements
Standard settings
The default implementation for removal calls the following check BAdIs:
- Local configuration check (CCM_I_STRCT_CHK.). Default code available.
- Inventory-based check (CCM_I_STATS_CHK). Default code available.
- Customer-specific check (CCM_I_CUSTR_CHK). No default code.
All messages are stored in an application log, the handle is usually filled from outside (calling application).
Recommendation
You may only need to overwrite the default implementation if you do not use 'Rotables Management' to setup/ control your part conditions on inventory level, or you do not want to call a local configuration check against the MPL. In such a case, you may only need to call the sub-BAdI for customer-specific checks in your implementation.
Activities
Further notes
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
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 | BADI_CCM_INSTALL_CHK | 0 | KAD0000001 | Aerospace & Defence Industry Solution |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20030225 |
SAP Release Created in | 46C2 |