SAP MDG · VALIDATION DERIVATION
How do I implement MDG BP default derivation in a BAdI or derivation exit?
Implement derivation as deterministic defaulting: read changed BP data from the delta buffer first, derive only initial target fields, use account group and BP kind as control inputs, and write back through the correct MDG buffer or governance API. Keep interface hooks small and entity-specific, and separate the orchestration method from the actual auto-derive methods.
Implement derivation as deterministic defaulting: read changed BP data from the delta buffer first, derive only initial target fields, use account group and BP kind as control inputs, and write back through the correct MDG buffer or governance API. Keep interface hooks small and entity-specific, and separate the orchestration method from the actual auto-derive methods.
Implement MDG BP default derivation by reading the changed data first, then populating only initial fields through the proper MDG buffer or governance API. The recommended pattern for `ZCL_MDGBP_BP_DEFAULTS`-style logic is to treat account group and BP kind as primary control inputs, keep interface hooks small and entity-specific, and document each method by entity, source API, derived fields, and suppression conditions.
Process flow
- Open SE18 and inspect the BAdI definition to confirm the interface, use type, and filter behavior.
- Create the implementation in SE19 with a Z* implementation name, package, and transport request.
- Assign or create the implementing class and activate the class skeleton.
- Implement the derivation method as thin orchestration plus focused defaulting logic.
- Read delta-buffer or model data first, then derive only initial fields.
- Use account group and BP kind as the main control inputs for branching.
- Write the derived values back through the correct MDG buffer or governance API.
- Activate the class and implementation, then test the scenario and debug the method call path.
Referenced tables
| Object | Purpose |
|---|---|
IF_USMD_DELTA_BUFFER_READ | Delta-buffer reader used to read changed data before derivation. |
IF_USMD_DELTA_BUFFER_WRITE | Delta-buffer writer used to persist derived values back to the MDG buffer. |
IF_USMD_MODEL_EXT | Model inspection API used to inspect the current BP state and entity structure. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- How should I build defaulting logic for MDG business partner entities?
- What is the implementation pattern for ZCL_MDGBP_BP_DEFAULTS-style derivation?
- How do I derive BP, vendor, company-code, and purchasing-org defaults in MDG?
Possible questions
- How do I create the MDG rule-service BAdI implementation for derivation?
- What is the recommended ABAP pattern for reading delta-buffer data and defaulting only initial fields?
- How do account group and BP kind control MDG default derivation?
- What should be checked before writing derived values back to the MDG buffer?
- How do I keep derivation hooks small and entity-specific?