Skip to Content
Author's profile photo Smita Kumar

ChaRM architecture & approach for project to Maintenance landscape

1                The Big Picture

  • We were implementing ChaRM in SolMan 7.0 for one of the Canadian customer with Global presence in more than 50 countries with total user base of more than 30K.
  • There were multiple projects which were going on and in future pipeline as well.
  • The requirement was to use ChaRM for any Program Change Request (PCR) which comes during UAT. All the PCR were supposed to be implemented and tested in Project landscape and then to be moved to Maintenance landscape.
  • The Challenge was that the ChaRM does not give any out of box feature to support more than 3 system landscape.
  • We proposed below solution and implemented it successfully.
  • This was finally used for many SAP Global rollouts projects.



2                Rollout/Project Transport Path

Pic1 ChaRM.png


3                ChaRM Process flow for PCR (Project Change Request)

Pic 2 ChaRM.png

All green color was the processes which were to be performed in SolMan or triggered within SolMan.


4                Highlights of Approach and Solution used

  • A new transaction type for project landscape was created.
  • A new status profile for project landscape was created.
  • Different relevant status was defined in the status profile.
  • New action profile and actions were defined.
  • New conditions for each custom action were defined.
  • For this transaction type custom status action and subject profile was assigned.
  • Also new partner functions were defined which were not available in standard SolMan.
  • Transport path for 5 system landscape was defined in SolMan.


Smita Kumar

SAP Lead consultant

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Shaswat C
      Shaswat C

      Hi Smita ,

      Just saw this post . Some queries came to mind :

      Did you define a separate project with virtual PROD for the implementation landscape (to be replaced with real PROD after the cutover) ? As the transport route doesn't exist between rollout/project QA system and PROD during this phase.

      Also , it seems from your requirement that the maintenance landscape used STMS to move changes outside of Charm .