Since Focused Build ST OST SP04, Fix Pace is introduced in Focused Build Requirements to Deploy process. Hence it is now possible to manage quick fixes with Focused Build in Hypercare phase. In this blog entry I will explain how you can utilize White List Object check for FB Fix Pace.
Uses cases supported by Focused Build as of ST OST SP04: Innovate and Fix
(Source: RIG, Customer Experience & Solutions, SAP SE)
FB Standard Change
In Fix Pace, FB Standard Changes are executed on a regular basis by the change management organisation and have no technical impact such as adding new currency, storage location, purchasing group, new plant, etc. Therefore no approval is needed for FB Standard Change. You should select the checkbox for Standard Change in Details tab of FB Request for Change. Then you can create FB Standard Change in Scope tab.
Creating a FB Standard Change via FB Request for Change
The objects that are maintained with FB Standard Change are customising objects and hence need to be transported. To indicate which objects are uncritical there is a white list to maintain in the Administration Cockpit.
White List Object Check
while utilising White List Objects check you can choose either when saving a change to a transport or when releasing the transport. In order to utilise upon-saving checks, make sure that the most recent Solution Tools Plug-In (ST-PI) installed in managed development system (minimum version is ST-PI 2008_1_7xx SP 16 or ST-PI 740 SP 6, respectively). In the Admin Cockpit select “On” option under the upon-saving checks column for the systems in which changes are to be made. Also make sure to implement SAP Note 2402504 “ChaRM: Back RFC check support” in managed development system.
Activating Upon-Saving Checks for managed system
Then you can click on White List Objects in order to activate the White List Object check and maintain the white list objects. By setting the switch you can globally activate or deactivate white list object check. Moreover, you can also activate or deactivate white list object check for single systems also.
Activating White List Object Check in Change Control Management – Administration Cockpit
Next, you specify which objects are allowed to be saved to a transport request of a FB standard change. Here you have the possibility to add the objects manually, directly from a transport request or from a selected object if it is already maintained. After maintaining the white list objects you can activate these objects for White List Object check.
Adding a white list object in Administration Cockpit
How to work with FB Standard Change
While a transport request of a standard change is being exported, the source and target system and the source and target client are determined. If the white list is active for the relevant client and system, the export program checks whether the objects on the transport request are on the white list. Objects that are on the white list are saved to the transport request.
If you try to save objects that are not part of the white list to a transport request of a standard change, you will receive an error message upon passing the Focused Build Standard Change to test. From the ui5 application you might come up with an error message like this:
Error message encountered in UI5 while trying to switch status of FB Standard Change “To Be Tested”
In this case close the message and click on the title of the Focused Build Standard Change to open the Expert view (CRM_UI):
Switching to Expert view (CRM_UI) for detailed error analysis
In expert view, developers can request that objects are added to the white list from the WebClient UI, in the transport-related checks dialog. When developers try to change the status of the FB Standard Change via Edit and Actions->Pass Standard Change to Test, you will come up with the White List Check pop-up. From the pop-up window, you can select the objects and request approval for the objects to be added on the White List:
Requesting the objects to be added to White List
You can click on Cancel after this step to wait for the approval.
Focused Build Change Manager opens the FB Standard Change in My Change Documents application and clicks on the title of the FB Standard Change. By role selection, select the FB Release Manager (or FB Architect).
From Expert view (CRM_UI), Release Manager or Architect can run the checks by opening the Transport Related Checks assignment block and add the corresponding objects to White List or reject the request:
Adding the requested objects to White List out of FB Standard Change
Once the objects are added to the White List, Developer can continue setting the status of FB Standard Change to “To Be Tested”:
Switching the status of FB Standard Change after the objects are added to White List
White List Object check can be utilised in Focused Build context only for Focused Build Standard Change in order to define no-risk or low-risk changes that are uncritical and frequently used. FB Standard Change can only be utilised in productive usage of a release and fix pace runs on the same landscape as of implementation landscape.
Hence by defining the white list objects, you can perform low-risk & frequent changes without additional approval in fix pace.
Here is the standard workflow for FB Fix Pace:
Focused Build Fix Pace Standard Workflow
(Source: RIG, Customer Experience & Solutions, SAP SE)
Additional Information & References: