Standard change is used to perform low-risk changes that are uncritical and frequently used. This new change document is comming in SAP Solution Manager 7.2 SP05.
Standard Change documents supports ABAP changes only.
The process is perfectly explained in the SAP Application Help Processing Standard Changes.
In this wiki page I want to share some hints for using this change document type.
Since SP06 you can create standard changes for SMAI, SMIM and SMRE cycles.
Standard Change Scenario Overview
The decision about using standard changes, transaction type SMSG, is taken from the requestor when creating a request for change document or by the change manager when he processes or creates a request for change document.
There is a new “Standard Change” checkbox in the Detail assignment block of the request for change document.
Note: Check authorization object SM_FIELD for allowing the requester to select the “Standard Change” checkbox.
If this checkbox is selected then in the Scope assignment block AB you could only select standard change documents.
If this checkbox is not selected and different change documents than standard change documents are entered in the Scope AB, the checkbox is unchecked. Cannot be flagged.
Due to the nature of the low-risk changes the approval process is skipped. Action Release for approval will not be available for selection.
When the request for change is approved action “Implement the Request for Change” will create the standard change documents and the request for change goes into status "Being Implemented".
Note: If you have copied the request for change document (SMCR) to your customer namespace in SP05, the standard change (SMSG) is delivered as an out-of-the-box feature.
In the case that you created a request for change document in your customer namespace prior to SAP Solution Manager 7.2 SP05, there are several manual activities that you need to perform to adapt your request for change document to the current standard in SP05.
The activities include adapt the authorizations of the Template user, UI configuration, status-dependent UI control, and PPF action Customizing. See the details in solman_setup under Change Request Management -> Define Change Process -> Copy Transaction type -> Enable Standard Change guided procedure:
When the standard change document is created now the developer needs to start the processing by setting the standard change to status “In development” and triggering the creation of the transport requests in the development system of the managed landscape.
Developers goes to development system to make the required changes. Remember that these changes should be “low-risk changes that are uncritical and frequently used”.
The way that Solman has to know which are considered low-risk changes is by adding them in the “White list” tab in the Administration Cockpit.
When the developer saves an object to the standard change transport request or when developer switch the workbench into change mode after selecting an object, the upon-saving transport-related checks are processed and developer will receive the White List object check.
Note: This transaction type SMSG is using the action COPY_ALL_ENH. You can use the enhanced Change Request Management action COPY_ALL_ENH to release and immediately import the transports of copy (ToC) into the test system.
When triggering the imports from the task list notice that there is a flag called “Standard Change Only” to select only the standard changes documents.
If this flag is selected only the standard changes with transport requests will be showed in the import popup. Status driven customizing will also be considered here.
It is not required to be in phase Go live to be able to import the transport requests of the standard changes into production system.
Technical details indicated in the solman_setup
Ensure that you have performed in Solman_setup -> Change Control Landscape -> Change Request Management -> 3. Define Change Process-> 3.1. Copy transaction types -> Activity "Enable Standard Change"
This will open the ChaRM: Enable Standard Change guided procedure with different activities to perform
Then in Solman_setup -> Change Control Landscape -> Managed System Setup -> 8. Configure Extended Function -> 8.6.Set Up Transpor-Related checks
pay attention to activities: Enable Upon-Saving Checks and Maintain Objects for White List.
1. Activate upon-saving checks in the Administration Cockpit-> Landscape Overview for the development system:client where the changes are being done.
This is a prerequisite for using the standard change as the White List object check is included in the upon- saving transport-related checks.
You should select option On to be able to use the White List Object check.
Technically this ON option would require that:
- In the managed development system, SAP Note 2402504 - ChaRM: Back RFC Check Support is implemented.
- In the managed development system the most recent Solution Tools Plug-In (ST-PI) is installed. The required minimum version is ST-PI 2008_1_7xx SP 16 or ST-PI 740 SP 6, respectively.
2. Activate in the Administration Cockpit -> White List Object tab the global switch and system level switch.
3. Add a Workbench or customizing change for an ABAP system:client
Note: If you want to use wildcards ensure that you fill the Object Name and Table Key values.
Only if all of the above 4 conditions are satisfied, then the upon-saving White List Objects check will work.
Note: in the case that the development system does not meet any of the about prerequisites in point 1 the developer could save any change to the transport request of the standard change as not White List Object check popup will appear. Later it is the change manager who should add the objects to the White List if not the developer could not move the standard change to status “To be tested”.
To add the Transport request object to the White List Change manager should go to the Transport Related Checks Assignment Block ->select the “White List” tab ->select the row with the transport request which contains your object and click the button “Add to White List”.
The following authorization objects have to be adjusted:
• B_USERSTAT (status profile <XX>SGHEAD)
• SM_FIELD (business transaction type <XX>SG, field name STANDARD_CHANGE, APPROVAL_PROCEDURE)
• CRM_ORD_PR (business transaction type <XX>SG)
SAP Application Help Processing Standard Changes
Related SAP Notes
2402504 - ChaRM: Back RFC Check Support