Show TOC

Object documentationChange 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 system administrators. 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 administrators. The document passes through a series of statuses, which depend on the type of the change document.

You select the appropriate change document type depending on the type of change.

Note Note

You can define your own transaction types for change documents in Customizing or use the transaction 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.

The following change document types and the corresponding transaction types are used by default in Change Request Management

End of the note.

Change Document Type

Transaction Type

Normal change

SMMJ

Urgent change

SMHF

Administrative change

SMAD

General change

SMCG

Defect correction

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

  • Change cycle data, such as the change cycle, the change control landscape, and the branch

  • Relationships, such as a 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:

  • Texts

  • Documents

  • Information about test management

  • Processing log

  • Information about transport requests, tasks, and the system landscape

  • Solution documentation

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 Start of the navigation path SAP Solution Manager Next navigation step Capabilities Next navigation step Change Control Management End of the navigation path. Execution of a change document can be planned in detail and, if necessary, can be integrated with additional processes and functions.