ChaRM for Beginners

Configuration in a Two-System Landscape

  • by Ameya Pimpalgaonkar, Senior SAP Architect
  • November 1, 2012
Working on Change Request Management (ChaRM) configuration can be tricky, especially for someone who is new to SAP Solution Manager. It takes time to understand the process flow and its application in business scenarios, and focusing on technical terminologies can distract you and stall your implementation. There are many documents and guides available for ChaRM, but they are rarely for beginners. This step-by-step guide explains ChaRM and takes you through each step of configuration, as well as potential error scenarios. Even if you are new to SAP Solution Manager, you can follow these steps to configure ChaRM in a two-system landscape.
Key Concept

Change management is one of the major components of any application management support project. A change tracking and management process is just as important as the implementation phase, and a project cannot survive without well-built change management. To address this, SAP Solution Manager has an optimized framework called Change Request Management (ChaRM). ChaRM provides a pre-defined tool to raise an issue, approve it, implement the change, test the change, and move it into production.

Change Request Management (ChaRM) is one of the most popular and widely used business processes of SAP Solution Manager. In most cases, ChaRM is implemented for a three-system landscape, and there are many guides available to help you through possible configurations. However, these guides rarely tell you what to watch out for and what not to miss, especially for readers who are working with SAP Solution Manager and ChaRM for the first time.

This guide is focused on ChaRM implementations for two-system landscapes. This kind of landscape is often used in SAP NetWeaver Business Warehouse (SAP NetWeaver BW), in which the test system is not as important as it is in other system landscapes. Therefore, development and testing are performed in one system and configuration is moved into production. I review possible error scenarios with ChaRM in a two-system landscape and how to tackle them because there is a thin line between configuration that SAP Solution Manager functional experts and consultants are required to do and configuration that is done by Basis teams. When SAP Solution Manager configuration is misunderstood for Basis tasks, you can make a misstep.

Ameya Pimpalgaonkar

Ameya Pimpalgaonkar is a senior SAP architect. He specializes in SAP Netweaver Portal, SAP BPM, BRM, MDM, and SAP Mobile. His interests include UI and front-end technologies, SAPUI5, Responsive Design, and integration of modern technologies with SAP UI. He has also worked on HTML5, CSS3, and jQuery. Ameya is also a certified usability analyst from HFI, USA.

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.