Fix Pace

Fix Pace is a fix process for Focused Build releases in the Hypercare phase and Operate phase. Fix Pace uses the following change transaction types:

Focused Build request for change
Focused Build standard change
Focused Build urgent change

These change transactions apply to the same system landscape as the Focused Build release. The Fix Pace is used for corrections in a release in the phases Hypercare or Operate. When the follow-on release is switched to Hypercare, the Fix Pace is completed and all changes have to be completed.

The Fix Pace is supported by the My Request for Change and the My Change Documents app. Request for change and change documents can also be changed in the Mass Change Operations app.

Change Manager

The change manager is the business partner function that is responsible for validating and approving requests for change.

Release Manager

The release manager is the business partner function that is responsible for importing the changes into the production system.

Requests for Change

A request for change can be created for an incident message or directly in the WebClient UI or in the My Request for Change app.

The change manager validates the request for change and defines its scope by specifying which type of change document (standard change or urgent change) is required and the system in which the change has to be implemented. Several change documents of the same type can be assigned to a request for change. The request for change then must pass an approval process before any change can be made. After the change manager has approved the request for change, the change documents are created and linked to the request for change.

Standard Changes

Standard changes are used for low-risk changes that are uncritical and frequently used. Standard changes affect only Customizing objects that are defined as uncritical (allowlisted) on the Allowlist Objects tab of the Change Request Management Administration Cockpit.

Since standard changes have no technical impact, they can be processed without an approval procedure.

Urgent Changes

Urgent changes are used to quickly fix errors in existing functionality.

When urgent changes have been be made in the development system, they need to be successfully tested before the release manager can set them to Handover to Production to import them to the production system.

Approval Procedures

The delivered default approval procedure consist of only one approval step in which the change manager has to approve the request for change. In the My Request for Change app, you can assign approval procedures and approval steps that you have customized in the standard Change Request Management in SAP Solution Manager.

In My Requests for Change and My Change Documents, you can also implement the Electronic Signature extension to use a FDA-compliant digital signature for signing off requests for change or urgent changes.