Detect and Resolve Project Intersections with ChaRM
- by Raquel Cunha, Independent SAP Solution Manager Consultant
- February 25, 2011
When performing maintenance or implementation projects in parallel, parts of the project can overlap or intersect, creating problems in the system. Learn how to use Change Request Management (ChaRM) in SAP Solution Manager to help you detect these project intersections, and then fix them.
Many companies work with multiple projects in parallel with the same production system or client as transport target, and face the problem of overlapping developments. Change Request Management (ChaRM) allows the user to detect critical transport objects and project intersections, and maintain predecessor relationships to avoid import problems. It helps control and organize changes.
One of the most common questions users ask me when implementing Change Request Management (ChaRM) in a multiple-projects environment — when projects are executed in parallel in the same system landscape — is how to deal with dependencies and critical objects that are part of more than one project. Users want to know, for instance:
- How to be aware of the existence of an object in a transport request from another project
- How to be aware of an object in a transport request being performed by another developer in the same project
- How to control the transport order so imports are executed accordingly
Some users only want to be informed that critical objects are included in the transports before they are released. One example is an object provided by SAP that can be repaired or manually corrected through SAP Notes. If it’s changed, it can create inconsistencies or modify a transaction. Each company can also have its own list of objects or table entries that must be considered critical for the company and need some special attention.
In some cases, users want to be informed about intersections to have a chance to avoid them. Intersections cannot always be avoided, however. Transports from different projects must be imported in such a way that they do not downgrade an object.
I will show you how to use ChaRM functions to deal with all the mentioned situations. This article is based on SAP Solution Manager 7.0 with enhancement package 1 and Support Package 23. I’m also assuming that you have completed ChaRM configuration.
Would you like to see this full item?