Change Request Management with SAP Solution Manager – Configuration — Lesson 2: Transaction Types, Change Cycles, Statuses, and Approvals

Learning Objectives

• Explain how Transaction Types, Change Cycles, Statuses, and Approvals supports controlled SAP change governance.
• Complete the workflow and produce a reviewable ChaRM workflow and lifecycle evidence pack.
• Evaluate the condition where a change advances without the required approval or target phase and select a supported response.

Detailed Topics

• Request for change and change documents: document sequence, decision points, and handoffs required for correct transaction execution.
• Change cycle creation and phases: determination logic and master-data influences that shape the resulting SAP document flow.
• Status profiles and actions: status changes, confirmations, messages, and operational evidence produced during processing.
• Partner, approval, and scope determination: exception paths and recovery choices needed when normal processing cannot continue.

Instructor Demonstration

The instructor models an end-to-end decision path covering Request for change and change documents, Change cycle creation and phases, Status profiles and actions, Partner, approval, and scope determination. Navigation, documents, configuration influences, authorization boundaries, and retained evidence are connected to ChaRM workflow and lifecycle evidence pack, including a controlled test where a change advances without the required approval or target phase.

Hands-On Exercise

Complete a controlled activity covering Request for change and change documents, Change cycle creation and phases, Status profiles and actions, Partner, approval, and scope determination and preserve the final result in ChaRM workflow and lifecycle evidence pack.

1. Confirm the business objective, organizational scope, required roles, source data, and expected SAP result.
2. Execute the workflow in sequence while recording settings, transactions, documents, messages, and observations.
3. Introduce the stated exception and isolate the earliest point where observed behavior differs from expectation.
4. Correct or contain the issue, retest the outcome, and document ownership, evidence, and follow-up.

Scenario Analysis

• Which SAP object, rule, master record, or process step most strongly influences the observed result?
• What evidence distinguishes a configuration problem from data, authorization, integration, or timing causes?
• How should the ChaRM workflow and lifecycle evidence pack be approved, retained, monitored, and updated after handover?

Troubleshooting Guidance

Start at the earliest point where expected SAP behavior differs from the observed result. Review process sequence, master data, organizational assignments, configuration, authorization, integration, and timing separately. Treat “a change advances without the required approval or target phase” as a testable hypothesis until settings, documents, logs, reports, and retest outcomes confirm the cause.

Validation Checklist

• Required structures, master data, roles, settings, and dependencies for Transaction Types, Change Cycles, Statuses, and Approvals are present.
• The ChaRM workflow and lifecycle evidence pack connects each conclusion to objective, reviewable SAP evidence.
• Normal processing, the stated exception, integration behavior, and access boundaries were tested.
• Corrections, retest criteria, ownership, documentation, monitoring, and operational handover are complete.

Lesson Outcome

Learners can apply Transaction Types, Change Cycles, Statuses, and Approvals, explain the resulting SAP behavior, and defend the outcome through ChaRM workflow and lifecycle evidence pack.