Change Document
A change document is a transaction that documents the activities of the users that are involved in the change process, for example, developers, testers, and IT operators. A change document is created automatically by the system when a change manager or another employee responsible approves a request for change, and the status is set to “Being Implemented”.
In the work steps following the approval of the request for change, the change document forms the operational basis for developers, testers, and IT operators. The document passes through a series of statuses, which depend on the type of the change document.
You select the appropriate change document depending on the type of change. You can define your own change document types in Customizing or use the change document types supplied by SAP. By default, the following transaction types are available in Customizing. You can copy the transaction types and adapt them to your requirements:
Change Document Type | Transaction Type |
SMMJ | |
SMHF | |
SMAD | |
SMCG | |
SMTM |
Structure
The change document consists of the header details, which are organized in individual groups, and additional assignment blocks. You can adapt and customize the display of the assignment blocks according to your requirements.
Header Level (Details Assignment Block)
In the header details, you store general data that applies to the whole change document. This includes, for example, the following data:
General data such as the developer, tester, and ID
Processing data
Data for change planning, such as the project and the task list
Related data, such as the project for which the change document is created, including the phase of the project
Relationships, such as the related request for change
Reference object, where you have to enter the installed base component that represents the production system where the changes are to be transported to
Assignment Blocks
In the assignment blocks, you store additional data that controls further processing. You can use the following assignment blocks, for example:
Information about projects and solutions
Texts
Documents
Information about test management
Processing log
Information about transport requests, tasks, and the system landscape
Integration
Requests for change and change documents with their content features are summarized using the term change transactions. They are used for handling all change processes with SAP Solution Manager.
Change Request Management uses variants of the SAP CRM service transaction for the processing of change transactions in SAP system landscapes.
For more information about integration and the required settings, see the Customizing in 
SAP Solution Manager
Capabilities
Change Request Management
. Execution of a change document can be planned in detail and, if necessary, can be integrated with additional processes and functions.