SAP MDG · WORKFLOWS
How do I test an SAP MDG Cost Center creation workflow with approval, rejection, resubmission, and withdrawal?
Test the Cost Center change request through three paths: happy path approval, rejection/resubmission, and withdrawal. The workflow should route from requester to first approver, then to final approver, with step 95 for activation and step 96 followed by 99 for withdrawal.
Test the Cost Center change request through three paths: happy path approval, rejection/resubmission, and withdrawal. The workflow should route from requester to first approver, then to final approver, with step 95 for activation and step 96 followed by 99 for withdrawal.
Test the Cost Center workflow in three scenarios. For the happy path, create the CR, approve it at both levels, and confirm activation and replication. For rejection, verify that Send for Revision requires a mandatory note and that the CR returns to Sent for Revision; then confirm the requester can resubmit the corrected data. For withdrawal, check that the requester must enter a cancellation note before the CR can be withdrawn, after which the process ends permanently.
Process flow
- 1. Create a Cost Center change request using change request type `ZCCT1P1`.
- 2. Submit the CR and verify it enters `Waiting for Finance Review`.
- 3. In the first approval step, confirm `Approve` and `Send for Revision` are visible and that approval can still allow data changes.
- 4. In the second approval step, confirm `Complete` and `Send for Revision` are visible and that the UI is read-only.
- 5. Verify `Complete` triggers background step 95 (`Activate`) and ends with `Final Check Approved`.
- 6. Test rejection by clicking `Send for Revision` without a note and confirm the system blocks it.
- 7. Enter a mandatory note, reject, and verify the CR becomes `Sent for Revision`.
- 8. Open the requester queue, confirm `Resubmit` and `Withdraw`, correct the data, and resubmit to route back to first review.
BRF+ decision tables for the rule-based workflow
Maintain the workflow routing logic for condition aliases such as approval, rollback, and completion.
Referenced tables
| Object | Purpose |
|---|---|
Cost Center workflow example | Shows the example CR type `ZCCT1P1`, workflow template `WS60000086`, and two approval levels. |
Workflow test scenarios | Defines the happy path, rejection/resubmission, and withdrawal checks with expected outcomes. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- What are the test scenarios for the SAP MDG Cost Center workflow?
- How do I validate the Cost Center MDG workflow end to end?
- What should I check in the Cost Center creation workflow happy path and rejection path?
Possible questions
- What are the expected statuses in the Cost Center workflow?
- Which buttons appear at each workflow step?
- What happens when I reject a Cost Center change request?
- How is withdrawal handled in the Cost Center workflow?
- Do I need BAdI code for this simple workflow?