Derivations
Derivations in SAP MDG automatically populate or default field values on master data during create/change processing, reducing manual entry, enforcing consistency and encoding business logic such as defaulting account groups, purchasing organizations, tax classifications or region codes based on other attributes. This topic covers the purpose of derivation rules, how they are configured and executed (typically via BRF+ decision tables/rules integrated with the MDG rule framework), where they fit in the change request and UI runtime flow, common troubleshooting approaches, and differences across ECC-style DIMP/legacy defaulting versus S/4HANA on-premise and cloud rule frameworks.
Overview
Derivations in SAP MDG automatically populate or default field values on master data during create/change processing, reducing manual entry, enforcing consistency and encoding business logic such as defaulting account groups, purchasing organizations, tax classifications or region codes based on other attributes. This topic covers the purpose of derivation rules, how they are configured and executed (typically via BRF+ decision tables/rules integrated with the MDG rule framework), where they fit in the change request and UI runtime flow, common troubleshooting approaches, and differences across ECC-style DIMP/legacy defaulting versus S/4HANA on-premise and cloud rule frameworks.
Lessons in this topic
- SAP Derivations Tutorial (Part 1)Understand what a derivation is in SAP MDG, why organizations use it, and how it fits into the broader governance process alongside validations and workflow.
- Configuring and Troubleshooting Derivation Rules: Runtime Flow and Diagnostics (Part 2)Learn how derivation rules are configured using the MDG rule framework and BRF+, how they execute during the change request lifecycle, and how to troubleshoot when derived values are wrong, missing, or inconsistent.
- Configuring and Troubleshooting Derivation Rules with BRFplus in MDG (Part 3)Learn how derivation rules are built using BRFplus (or the rules engine available in your MDG release), wired into the data model and UI, executed at runtime, and diagnosed when values fail to populate as expected.
- Advanced Derivations: Architecture, Integration and Production Design (Part 4)Advanced capstone for Derivations, connecting the existing lesson areas: Why Derivations Matter and Where They Fit in MDG Data Governance; Configuring and Troubleshooting Derivation Rules: Runtime Flow and Diagnostics; Configuring and Troubleshooting Derivation Rules with BRFplus in MDG. The goal is to move from feature knowledge to architecture, integration, production support and governance decisions.
Interview questions covered
- What are the core concepts of Derivations, and how would you explain them clearly in an SAP interview?
- How would you apply Derivations in a real SAP project? Walk through the design or implementation approach.
- A production issue is reported in Derivations. What would you check first, and how would you troubleshoot it systematically?
- What are the most important design decisions, trade-offs, and best practices in Derivations?
- Suppose you inherit an existing Derivations solution. How would you review it before making a change?
- A senior architect is reviewing Derivations. The project situation is: A retail company implementing MDG for business partner governance wants every new customer created in Germany to automatically receive a default payment terms code and a default dunning procedure based on customer classification, instead of relying on data stewards to remember regional finance polic. What design changes, validation evidence and production controls would you require before approving the solution?
- A project encounters this situation while working on Configuring and Troubleshooting Derivation Rules: Runtime Flow and Diagnostics: During UAT for an MDG material governance rollout, testers report that valuation class is derived correctly for materials created in the base plant but comes back blank for a newly onboarded plant. Walk through how you would analyze the requirement or issue, what you would validate, and how you would test the solution before release.
- A project encounters this situation while working on Configuring and Troubleshooting Derivation Rules with BRFplus in MDG: A global chemicals company governs material master records in MDG and wants to auto-derive the default storage condition and hazardous material indicator based on material group and country of production, so plant data stewards do not have to look up this mapping manually. Walk through how you would analyze the requirement or issue, what you would validate, and how you would test the solution before release.
- Using this SAP project situation — A retail company implementing MDG for business partner governance wants every new customer created in Germany to automatically receive a default payment terms code and a default dunning procedure based on customer classification, instead of relying on data stewards to remember regional finance policy — explain Why Derivations Matter and Where They Fit in MDG Data Governance. What should happen, which concepts or process steps matter, and what common mistake would you avoid?