Hierarchy
MDG_FND (Software Component) MDG Foundation⤷
CA-MDG (Application Component) Master Data Governance⤷
MDG_BS_COMMON_OBJECTS (Package) MDG: Common Objects (IMG, Switches, Roles, ...)
IMG Activity
| ID | FMDM_USMD_RULE_SERVE | BADI: Define Validations/Derivations |
| Transaction Code | S_BT6_63000002 | (empty) |
| Created on | 20110210 | |
| Customizing Attributes | FMDM_USMD_RULE_SERVE | BADI: Define Validations/Derivations |
| Customizing Activity | FMDM_USMD_RULE_SERV | BAdI: Define Validations/Derivations |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | USMD_RULE_SERVICE |
Use
This Business Add-In (BAdI) is used in the Master Data Governance (CA-MDG) component.
You can use this BAdI to create customer-specific checks on entities, change requests, and editions. You also can use this BAdI to define that certain field values are to be derived from the values of other fields in the master data.
Methods
- CHECK_ENTITY
When processing a change request, you call this method by choosing the Check function (pushbutton). When the system checks an entity, the system calls this method once for each entity type of the changed master data. In this method, you define all rules for checking the entities in the data model.
Note that error messages can be diminished to warning messages if this is so defined for the respective entity type in Customizing activity Create Change Request Type under Message Output.
If you want to prevent the activation when an error occurs, you need to define the check in the method CHECK_CREQUEST.
- DERIVE_ENTITY
- Within the context of a UI, the method is called for entities whose UIBBs are visible at the following event handlings:
- A) Floorplan Manager PBO event handling (Process Before Output) to enable defaulting of fields
- B) Floorplan Manager PAI event handling (Process After Input) to derive attribute values based on user input
- In all other contexts, this method is called at least once per entity for all changed entities.
- While it is possible to change rows and add additional rows to CT_DATA, deletion of rows will be ignored.
- Therefore use the BAdI: Derivations Across Entity Types (USMD_RULE_SERVICE_CROSS_ET) for the deletion of entities of storage and usage type 4.
- When you activate a change request, the system first processes the following methods in succession in the background before it activates the change request:
- CHECK_CREQUEST_START
- CHECK_CREQUEST (once for each entity type of the changed master data in the change request)
- CHECK_CREQUEST_FINAL
- When an edition is checked, the system calls the following methods in succession:
- CHECK_EDITION_START
- CHECK_EDITION (once for each entity type of the changed master data in the edition)
- CHECK_EDITION_FINAL
Requirements
Standard settings
In the standard delivery, the BAdI implementation USMDZ3_RULE_BADI is activated for data model 0F. The implementation is automatically executed for this data model.
The BAdI is filter-dependent. The data model (MODEL) and the entity type (ENTITYTYPE) serve as filters.
The BAdI is not designed for multiple use.
BAdI Implementations
USMDZ3_RULE_BADI
The BAdI implementation is located in the enhancement implementation USMDZ3_IMP_RULE_SERVICE_BADI.
Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
Example
See also
This BAdI uses the interface IF_EX_USMD_RULE_SERVICE. For more information, display the interface in the Class Builder.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20110210 |
| SAP Release Created in | 703 |
