SAP MDG · UTILITIES
How do I configure and execute MDG GL account creation with rejection, rework by primary approver, and final approval in SAP MDG?
Use the MDG Fiori governance app to create the GL account CR, send it first to the Primary Approval team, let MDG reject it with a reason, let the Primary Approver revise the company code details, and then resubmit for MDG final approval. After final approval, verify the GL account in the S/4 master data app.
Use the MDG Fiori governance app to create the GL account CR, send it first to the Primary Approval team, let MDG reject it with a reason, let the Primary Approver revise the company code details, and then resubmit for MDG final approval. After final approval, verify the GL account in the S/4 master data app.
In this SAP MDG scenario, the requestor creates a G/L account change request in Manage G/L Account Centrally - Governance, supplies the mandatory change request reason and notes, and routes it to Primary Approval. MDG then rejects the request with a reason, which sends the CR back to the Primary Approver for revision and resubmission before final approval by the MDG team.
Process flow
- Log on to the Fiori launchpad as the GL account requestor.
- Open Manage G/L Account Centrally - Governance.
- Create a new GL account change request and enter a description.
- Verify the defaulted GL account fields.
- Run Check and supply the mandatory change request reason and notes.
- Choose Primary Approval as the change request reason.
- Add CR notes in the Notes tab.
- Run Check again and submit the CR to Primary Approval team and then to MDG team after rework as applicable in the workflow flow in the source scenario context; general guidance — verify exact routing rules in your MDG workflow configuration
Governance
Source-supported Fiori app used to create and submit the G/L account change request.
Source-supported app used by approvers to find CRs in status To be Processed by Me.
Source-supported app listed in the scenario metadata for reviewing change requests.
Source-supported verification app used to confirm the approved G/L account exists in the target master data app.
Referenced tables
| Object | Purpose |
|---|---|
USMD120C | Change request type/process mapping used in MDG workflow logic. |
USMD1210 | Change request notes table shown in the related ABAP utility example. |
USMD1601 | Change request type to process mapping shown in the related ABAP utility example. |
CVI_VEND_LINK | Partner-to-vendor lookup used in the related ABAP utility example. |
BUT000 | Business partner lookup used in the related ABAP utility example. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- How does the TC6 MDG GL account creation workflow work?
- What are the steps for rejected MDG GL account creation followed by primary approver rework and final approval?
- Which apps and statuses are used in MDG GL account creation with rejection and re-approval?
Possible questions
- How do I configure and execute MDG GL account creation with rejection, rework by primary approver, and final approval in SAP MDG?
- What are the workflow steps for MDG GL account creation after MDG rejection?
- Which Fiori apps are used to process rejected GL account CRs in MDG?
- How are notes, rejection reasons, and company code data handled in this scenario?
- How is the created GL account verified in S/4HANA after approval?