SAP MDG · UTILITIES
How does the SAP MDG corporate supplier creation process work when MDG rejects the change request and the L1 approver resubmits it for final approval?
In this MDG BP corporate supplier scenario, the requestor creates and submits the supplier change request, L1 approves it, MDG final rejects it with a reason, and the same L1 approver updates the data from the rejection notes and resubmits it for final approval. The final outcome is status 'Final check approved' after the MDG final approver approves the revised request.
In this MDG BP corporate supplier scenario, the requestor creates and submits the supplier change request, L1 approves it, MDG final rejects it with a reason, and the same L1 approver updates the data from the rejection notes and resubmits it for final approval. The final outcome is status 'Final check approved' after the MDG final approver approves the revised request.
The TC37 scenario covers a corporate supplier BP creation in SAP MDG where the requestor submits the change request, the L1 approver sends it onward, MDG final rejects it with a rejection reason, and the L1 approver resubmits the corrected request for final approval.
Process flow
- Requestor logs on to Fiori launchpad and opens Manage Business Partner Governance.
- Requestor creates an organization supplier BP change request.
- Requestor enters BP details and vendor data, then runs Duplicate check.
- Requestor adds role FLVN00 and maintains ERP vendor/company code details.
- Requestor clicks Check and Submit; status becomes 'To be considered and approved'.
- Level 1 approver opens My Change Request and approves the request.
- MDG Final approver opens My Change Request monitoring and rejects the request with a reason.
- Status changes to 'To Revise: Perform Changes' and rejection mail is sent to L1 approver.','L1 approver opens the request again, reads the Notes tab, corrects the data, and submits it again.','MDG Final approver reviews the corrected data,.
Fiori app: Manage Business Partner Governance
Used by the BP requestor to create the supplier business partner change request.
Fiori app: My Change Request
Used by the Level 1 approver to review, correct, and resubmit the rejected change request.
Fiori app: My Change Request monitoring app
Used by the MDG Final approver to process the change request in the final approval stage.
Fiori app: Display Change Requests
Referenced in the scenario index as a related app for monitoring or display.
Referenced tables
| Object | Purpose |
|---|---|
USMD1210 | Stores change request notes; the related ABAP utility example inserts a rejection or note text record here. |
USMD120C | Used in the related ABAP utility logic to determine the change request type and process from the change request number. |
USMD1601 | Joined in the related ABAP utility logic to derive workflow process information for a change request. |
CVI_VEND_LINK | Used in the related ABAP utility logic to resolve vendor number from business partner information. |
BUT000 | Used in the related ABAP utility logic as the business partner master data source. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- How do I configure and test MDG BP supplier creation with MDG rejection and L1 resubmission?
- What is the workflow sequence for corporate supplier creation in SAP MDG after rejection by MDG?
- How do the Fiori apps and statuses behave in an MDG supplier creation rejection/resubmission scenario?
Possible questions
- What are the exact workflow statuses in this MDG supplier rejection/resubmission scenario?
- Which Fiori apps are used by requestor, L1 approver, and MDG final approver?
- How do rejection notes get visible to the L1 approver in MDG?
- What is the end-to-end process for corporate supplier creation with resubmission?
- How do I validate the change request after revising rejected data?