SAP MDG · UTILITIES
How does MDG Business Partner supplier creation work for a corporate supplier group when MDG rejects the change request and the L1 approver withdraws it?
In TC38, a corporate supplier BP is created in Manage Business Partner Governance, approved by the L1 approver, rejected by the MDG final approver, and then withdrawn by the L1 approver. The key user-facing statuses are 'To be considered and approved', 'To be processed by Master Data Governance team', 'To Revise: Perform Changes', and finally 'Final check rejected'.
In TC38, a corporate supplier BP is created in Manage Business Partner Governance, approved by the L1 approver, rejected by the MDG final approver, and then withdrawn by the L1 approver. The key user-facing statuses are 'To be considered and approved', 'To be processed by Master Data Governance team', 'To Revise: Perform Changes', and finally 'Final check rejected'.
TC38 covers an MDG BP supplier creation flow for a corporate supplier group: the requestor creates the change request in Manage Business Partner Governance, the L1 approver approves it, the MDG final approver rejects it, and the L1 approver later withdraws the rejected request. The documented flow also confirms the notes visibility and the status transitions used during rejection and withdrawal.
Process flow
- Login to Fiori launch pad as BP Requestor
- Open Manage Business Partner Governance
- Create new organization-based supplier BP change request
- Enter change request description and BP master data
- Run duplicate check and adjust address data if needed
- Add supplier role FLVN00
- Maintain ERP vendor, company code, accounting, payment, and automatic payment data
- Check and submit the change request and send it to L1 approval','L1 approver reviews the CR in My Change Requests and approves it','MDG final approver reviews the CR in My Change Request monitoring and rejects it with a reason','L1 approver
Fiori app / tile: Manage Business Partner Governance
Create and maintain the Business Partner supplier change request for the corporate supplier group
Fiori app / tile: My Change Requests
L1 approver processes the submitted change request and approves it
Fiori app / tile: My Change Request monitoring
MDG final approver rejects the change request and returns it for revision
Fiori app / tile: Display Change Requests
Referenced in the scenario header as a related application for change request review
Referenced tables
| Object | Purpose |
|---|---|
USMD1210 | Stores MDG change request notes; used in the ABAP note insertion example |
USMD120C | Used in the ABAP integration example to derive change request type from the change request |
USMD1601 | Used in the ABAP integration example to derive process information for the change request |
CVI_VEND_LINK | Used in the ABAP integration example to map business partner to vendor |
BUT000 | Used in the ABAP integration example to resolve business partner data |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- What is the end-to-end approval flow for MDG BP supplier creation with corporate supplier group rejection and withdrawal?
- How do I configure and test the rejection-by-MDG then withdrawal-by-L1 scenario in SAP MDG Business Partner governance?
- Which Fiori apps and status changes are used in the corporate supplier group withdrawal scenario after MDG rejection?
Possible questions
- What are the steps in the TC38 supplier creation scenario?
- Which Fiori apps are used for requestor, L1 approver, and MDG final approver?
- What statuses appear after approval, rejection, and withdrawal?
- How do I add a change request note programmatically in MDG BP?
- How do I call an external interface from an MDG BP change request?