MDGbeginner
Change Requests
This topic covers Change Requests (CRs) in SAP Master Data Governance: the core object that packages proposed master data changes, drives workflow-based approval, enforces validation and duplicate checks, and controls when data becomes active in the governance and consolidation layers. Lessons progress from foundational concepts to configuration and processing details needed for real MDG implementations on S/4HANA.
Overview
This topic covers Change Requests (CRs) in SAP Master Data Governance: the core object that packages proposed master data changes, drives workflow-based approval, enforces validation and duplicate checks, and controls when data becomes active in the governance and consolidation layers. Lessons progress from foundational concepts to configuration and processing details needed for real MDG implementations on S/4HANA.
Lessons in this topic
- SAP Change Requests Tutorial (Part 1)Introduces the Change Request as the core governance object in SAP MDG, explaining why raw master data edits are not allowed and how a CR bundles data, workflow, and audit trail together.
- Understanding the Role of Change Requests in MDG Governance (Part 2)Introduces what a Change Request is in SAP MDG, why it exists, and how it enables controlled, auditable master data changes across create, change, and mark-for-deletion scenarios.
- Change Request Types, Steps, and Core Configuration Building Blocks (Part 3)Explains how CR types are configured with entity types, processes, and workflow steps, and how these building blocks combine to control what a requester sees and who must approve.
- Configuring Workflow Steps and Agent Determination for Change Requests (Part 4)Learn how MDG change request types are linked to workflow templates, how processing steps are sequenced, and how agent determination rules assign the correct approvers and processors at each step.
- Configuring Change Request Types and Linking Workflow for Processing (Part 5)Explains how to configure Change Request types, associate them with workflow templates, and understand the runtime processing flow from creation through approval and activation.
- Change Request Runtime Flow: Status Management, Agent Determination, and Troubleshooting Stuck Requests (Part 6)Understand how a change request moves through its lifecycle at runtime, how agents are determined for each workflow step, and how to diagnose and resolve requests that get stuck, skip steps, or fail to route correctly in production.
- Advanced MDG Change Request Lifecycle and Parallel Governance (Part 7)Design change requests around business risk, parallel review and restartable workflow so governance stays controlled without creating unnecessary cycle time.
Interview questions covered
- What are the core concepts of Change Requests, and how would you explain them clearly in an SAP interview?
- How would you apply Change Requests in a real SAP project? Walk through the design or implementation approach.
- A production issue is reported in Change Requests. 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 Change Requests?
- Suppose you inherit an existing Change Requests solution. How would you review it before making a change?
- A senior architect is reviewing Change Requests. The project situation is: A vendor change required both tax and procurement review, but sequential approvals doubled cycle time. What design changes, validation evidence and production controls would you require before approving the solution?
- A project encounters this situation while working on Change Request Types, Steps, and Core Configuration Building Blocks: During a private cloud S/4HANA rollout for supplier master governance, the business wanted a fast path for updating a supplier's phone number without going through the same three-level approval used for new supplier creation with banking details. 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 Workflow Steps and Agent Determination for Change Requests: During an S/4HANA private cloud MDG rollout for a multinational manufacturer, the project team configured a two-step approval for cost center changes: data steward review followed by controlling approval for financially sensitive fields. 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 material master governance found that store managers were used to editing materials directly in the legacy system — explain What a Change Request Is and Why MDG Uses It. What should happen, which concepts or process steps matter, and what common mistake would you avoid?
- A project encounters this situation while working on Configuring Change Request Types and Linking Workflow for Processing: A utilities company governing business partner master data configured two CR types: 'BP Create - Customer' with a single steward approval, and 'BP Change - Bank Details' with a mandatory two-step approval (data steward then treasury) because bank detail changes are a fraud risk. 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 Change Request Runtime Flow: Status Management, Agent Determination, and Troubleshooting Stuck Requests: A global consumer goods company using MDG for material governance noticed that roughly 5% of change requests for a specific plant region were sitting untouched for days with no visible approver. 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 consumer goods company implementing MDG for material master governance found that plant buyers were directly changing purchasing views in the ERP backend, causing inconsistent valuation classes across plants — explain Understanding the Role of Change Requests in MDG Governance. What should happen, which concepts or process steps matter, and what common mistake would you avoid?