SAP Solution Manager 7.2 SP05 is released . It contain ChaRM new transaction type standard change (SMSG) and enhanced transport of copies(Toc)action(COPY_ALL_ENH) available in Change Request Management(ChaRM).

SAP Introduced the Standard change(SMSG)transaction type in 7.2 SP05 workflow as shown below,

SAP ChaRM -Standard change workflow(SMSG): (Source image: SAP)

SAP ChaRM -Normal change Workflow(SMMJ): (Source image: SAP)

Main advantage of using standard change instead of Normal change:

SAP recommend to use Standard change to perform changes that are uncritical and frequently used. Standard changes are recommend to use for  no-risk or low-risk changes and can therefore be processed without phase cycle status change .

It contain transport of copies (ToC) similar like normal change but it does not required to change the phases status like “Test” , ” Go-Live” during the Integration testing and production import due to low risk changes.For ex..mainly this type of change will use similar like N landscape monthly transports. So it is speedy process to move the changes to PRD with out change manager phase cycle status change approval.

Able to process the standard change during the phase cycle status “Scope” or “Build”

Note: If the phase is “Scope” cannot export any changes.It allow to create transport requests and make changes in the development system, but cannot release transport requests .Similar like other changes.

New “Standard change” check box available in SP05 Rfc screen.

Make sure white list object updated in ChaRM admin cockpit for validation during the status ” To be tested”.

In SP05 SAP used COPY_ALL_ENH action in standard change to import ToC automatically in test system with out any manual schedule in task list or hourly background job schedule.

Upto 7.2 SP04 i have removed the phase restriction in view cluster and used the normal change for N landscape low-risk monthly change cycle.. But from SP05 it is very easy to use standard change for low-risk project changes with out any phase cycle status approval.I hope this workflow will going to helps lot of customers.

Normal change is used for all N+1 changes ( big enhancement and upgrade projects) .it required more testing and phase control for Development release, Integration testing and PRD import.Defect correction helps to record all the integration testing defects in “Test” phase.

In Request for change, new CRM_RFC_APPR approval procedure available SP05. It allows to use a personalized HTML (Mail form) email notification during Change Manager or CAB approval procedure.

Please check the below Wiki for more details:

https://wiki.scn.sap.com/wiki/display/SM/How+to+work+with+ChaRM+Standard+Changes+documents

 

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply