Control the Request for Change Status Changes Based on the Related Change Documents Status

  • by Raquel Cunha, Independent SAP Solution Manager Consultant
  • September 21, 2012
Learn how to control the status change of a request for change based on the status of the lower-level documents — the related change documents included in the request for change scope.
Key Concept

A request for change is a formal proposal for a change in one or more configuration items, or to services, procedures, and items associated with the infrastructure, represented by Installed Base (IBase) components. The request for change is categorized, prioritized, and has a scope defined in which the change manager specifies which types of changes are implemented. Depending on the scope, the system creates one or more change documents linked to this request for change after its approval, and the implementation part of the change flow starts.

The goal of Change Request Management (ChaRM) in Solution Manager is to efficiently implement changes to SAP applications with minimal risks using standardized methods and procedures. ChaRM controls the process documentation and the processing of transports on the change level. It offers functions for managing, executing, and documenting all changes, requirements, and requests for change, which are proposals for changes made in the system (formerly called change requests).

Some companies can use the standard ChaRM processes without the need to develop or configure anything out of the box, but other companies may need to create their own procedures and methods, implementing new fields, status, and actions. For example, one company I worked with needed to include more approval levels in an urgent correction before the request went to production, and some statuses depended on the request for change status. Although there is a lot of documentation already available for standard ChaRM, it’s still a little bit difficult to find information on how to configure your own ChaRM system. I’ll show you one of the things you can do with ChaRM out of standard functionality.

Specify Status Attributes for Status Control

In some cases, you may need to control the status of the change documents based on the current status of the request for change that created them. Alternatively, you may need to control the status of the request for change based on the status of its successor change documents. This might be particularly necessary when configuring ChaRM out of the standard system, with new actions and new statuses created to adjust the standard process to the company’s needs. You may have a requirement to create one or more status values in the request for change and in the change documents, and configure those statuses in such a way that a status of one document depends on a status of another document.

Raquel Cunha

Raquel Cunha is an independent consultant who has worked with SAP solutions in Latin America and Europe since 1998. She started as an ABAP developer and has also worked as an ABAP team leader and HR application consultant. Raquel has a bachelor’s degree in computer science and is certified on ABAP and ITIL V2 and V3. She changed her focus to SAP Solution Manager, with particular emphasis on Service Desk and ChaRM, and has been implementing Solution Manager in four different countries since 2005. Raquel is currently an SAP Mentor.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.