SAP MDG · UTILITIES

How does SAP MDG handle G/L Account creation when a primary or alternate approver withdraws the change request, and what is the expected workflow and status behavior?

In this MDG scenario, the requestor creates a G/L account change request, the approver reviews the CR notes, and then uses Withdraw to cancel the request after entering a withdrawal reason. The expected final status is "Final check rejected".

In this MDG scenario, the requestor creates a G/L account change request, the approver reviews the CR notes, and then uses Withdraw to cancel the request after entering a withdrawal reason. The expected final status is "Final check rejected".

This SAP MDG test scenario covers G/L Account creation initiated by a requestor and withdrawn by either the primary or alternate approver. The request starts in "Manage G/L Account Centrally - Governance", is routed to the approver through "My Change Requests Monitoring" or the email link, and after the approver clicks Withdraw and confirms the reason, the CR is closed with status "Final check rejected".

Process flow

  1. Log in to Fiori Launchpad with the G/L Account requestor user.
  2. Open "Manage G/L Account Centrally - Governance".
  3. Create a new G/L Account change request and enter the CR description.
  4. Review the defaulted G/L account details and ensure required fields are filled.
  5. Use Check to validate the CR.
  6. Maintain the change request reason and enter notes.
  7. Submit the CR so it is routed to the approver.
  8. Log in as the primary or alternate approver and open the CR from the email link or "My Change Requests Monitoring" with "To be Processed by Me" selected. Navigate to the CR notes tab and review the notes. Click Withdraw at the bottom of a
Manage G/L Account Centrally - Governanc

Fiori app

Create and submit the G/L Account change request in the governance process.

My Change Requests Monitoring

Fiori app

Open the routed change request as an approver and filter on "To be Processed by Me".

Display Change Requests

Fiori app

Review the change request during monitoring and verification.

Manage G/L Account Master Data

Fiori app

Post-withdrawal verification of the resulting master data state if needed.

Referenced tables

ObjectPurpose
USMD1210Change request note storage table used by the related utility method example.

The remaining configuration, implementation details, and testing guidance continue from this answer more…

Related questions and keywords

Alternative questions

  • What happens in MDG when the approver withdraws a G/L account creation request?
  • Which app and status changes are involved in the G/L account withdrawal scenario?
  • How do I test the withdrawal path for a G/L account creation change request in MDG?

Possible questions

  • What are the steps for MDG G/L Account creation withdrawal by primary/alternate approver?
  • How do I configure the withdrawal scenario for G/L account MDG approval?
  • What status is shown after the withdraw action in the G/L account workflow?
  • Which Fiori apps are used in the G/L account withdrawal test scenario?
  • How are notes and withdrawal reasons handled in the MDG workflow?

Keywords

SAP MDGG/L AccountChange RequestWithdrawalPrimary ApproverAlternate ApproverFioriMy Change Requests MonitoringManage G/L Account Centrally - GovernanceDisplay Change RequestsFinal check rejected