Hierarchy

⤷

⤷

IMG Activity
ID | BADI_CCM_EXPL_ALWD | BAdI: Restrict Structure Explosion of Actual and Allowed Configuration |
Transaction Code | S_KA5_12001111 | (empty) |
Created on | 20020118 | |
Customizing Attributes | BADI_CCM_EXPL_ALWD | BAdI: Restrict Structure Explosion of Actual and Allowed Configuration |
Customizing Activity | BADI_CCM_EXPL_ALWD | BAdI: Restrict Structure Explosion of Actual and Allowed Configuration |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | BADI_CCM_EXPL_ALWD |
Use
You use this Business Add-In (BAdI) to restrict the explosion of a maintenance object's allowed configuration and actual configuration for configuration checks in the configuration control workbench. You can define your own logic to filter iPPE objects for the explosion of the allowed configuration and to filter technical objects from the execution of the configuration check. All technical objects are loaded and displayed in the navigation area, whereas filtered technical objects are not subject to the configuration check.
For example, you can determine that only iPPE objects belonging to the same product class should be loaded. For this case, SAP provides the implementation BADI_CCM_EXPL_ALWD. If you want to use this implementation, you have to activate it first.
If an implementation of this BAdI is active, two check buttons appear in the configuration check area of the user interface:
- If the user chooses Check , the system now performs a check against the filtered allowed configuration.
- If you choose Extended Check, the system performs a check against the complete exploded allowed configuration.
SAP provides the following methods:
- MPL_NODE_CHECK
Checks (and deletes) iPPE nodes during the explosion of the allowed configuration. In parameter IS_PNODID the current iPPE node is specified (next higher iPPE node). This parameter cannot be changed but be used to investigate properties like, for example, the product class of the next higher iPPE node. Parameter CT_STRUCT displays a list of iPPE nodes (key is GUID1). Each iPPE node that is deleted from the table will not be used for the configuration check.
- CONFIG_CHECK_FILTER_ELEMENTS
This method is called after the actual and the allowed configuration have already been loaded. It enables you to delete/add/change objects from the configurations by changing table CT_ACTUAL_ELEMENTS for the actual configuration and table CT_ALLOWED_ELEMENTS for the allowed configuration. This method is independent of user action (load completely or load partially).
SAP provides the following parameters:
- GV_BYPASS_BADI
This paramter is used to bypass any of the methods. The parameter is static and can be set from outside of BAdI methods using the CLASS cl_ex_badi_ccm_expl_alwd DEFINITION LOAD statement and by setting 'X' to cl_ex_badi_ccm_expl_alwd=>if_ex_badi_ccm_expl_alwd~gv_lbypass_badi. If an implementation of this BAdI is active (see also above), the parameter is set to 'X' if the user chooses the Load (Extended) button.
Example
Requirements
If the method CONFIG_CHECK_FILTER_ELEMENTS is empty, use this BAdI in conjunction with BAdI BADI_CCM_EXPLOSION, which enables you to restrict the loading of the object's actual configuration.
Standard settings
Recommendation
Activities
If you want to use the SAP implementation of this BAdI, you have to activate it first.
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_EXPL_ALWD | 0 | PLN0000023 | Configuration Control |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20030625 |
SAP Release Created in | 470 |