Change Request Management (ChaRM)

Change Request Management (ChaRM) is an application within Solution Manager (SolMan) which is used to manage the SAP software (ABAP, JAVA, Process Orchestration, S/4 HANA, HCP, Business Object, Fiori, Hybrid and SAP Mobile) changes within your IT Landscape.  Changes are requested, approved, scheduled, assigned, test results tracked, and final implementation into production plus post activities are captured in this application.  The logging of the ChaRM application will provide an accurate audit log of who, when, where, why and how changes were implemented.  ChaRM Administrative changes can be leveraged to manage the modification of application component stacks.

The benefits of ChaRM

  1. SAP software changes management from development, testing and production are incorporated with transport management systems (TMS).
  2. ChaRM utilizes workflow-based management within Release Management to synchronize developed solutions 
  3. ChaRM utilizes quality-gate management (QGM) to ensure proper sign-off and approvals are given and documented thus ensuring better transparencies of changes made to SAP and non-SAP software
  4. ChaRM Retro-Fit functionality can ensure synchronization of Dual Landscapes with transports imported into production
  5. ChaRM Cross Systems Object Locking (CSOL) and Down Grade Protection (DGP) functionality prevents software modifications from leap-frogging within and between production support plus project landscapes
  6. ChaRM can be leveraged by the other SolMan applications such as:
    1. Business Process Change Analysis (BPCA) and Solution Documentation (SolDoc) modifications.  Enhancements of business processes documentation will be promoted for support.
    2. Defects detected in the Test Management workbench will trigger change request for development fixes.  These fixes will be managed through ChaRM documents 
    3. IT Service Management (ITSM) problem and defect documents can be transferred to Request for Changes once the service technician determines that a software or hardware change is required to resolve the problem

Our real life experience

We implemented a ChaRM solution which allowed our telecommunication client to work within the Agile project management methodology.  This solution aligned their three-week project sprints using two dual development instances, five Testing Instance and production plus retro-fitting.  By utilizing CSOL & DGP they reduced over-writes of older ABAP code.  Using the enhanced CTS we were able to move Java and HANA code through the same change documents.  We dramatically reduced the project import time in production by using the ToC technique.  We streamlined the workflow because we engineered the solution to allow developers to move Toc and final transports into Test thus eliminating emails and Basis’s help.

We implemented a four system ChaRM support landscape.  This allowed two systems to be leveraged for testing, first for QA/UAT Testing and second for Regression, End-to-End and Stress Testing.  Test Suite regression test scripts were engineered to run automatically during off-hours prior to Change Approval Board meetings to report that critical business will not be impacted by new scheduled modification.  This reduced daily production transports to once a week.  Additionally, the auto-scheduling was leveraged for off-hour imports into production.