Request for Change Validation

As we mentioned, request for change validation is one change to the former change request process. Validation involves
an extra step, which is setting the status to In Validation via an action as shown in Figure 11.12. The result is that the
request for change document status is updated to Validation in which approval can commence.
Validating a change can be considered the first approval layer, prior to the official request for change approval by the
CAB. Validation of a request for change, according to SAP, is to be administered by the change approver. The following
activities are examples of what the change approver may look for, verify, confirm, and/or update during this step in the
request for change process:
_Appropriate values have been maintained (e.g.,, impact, urgency, priority, category, and business partners).
_The request is actually a change and not a problem, incident, or training issue.

_Clarity and completeness of short and long descriptions have been maintained.

_All required documentation has either been described or uploaded as an attachment.

After the validation step is performed by the change approver, the request for change is released for CAB approval. The
request for change is updated to the ToBe Approved status, and the workflow continues.
The process diagram in Figure 11.13 provides a snapshot of the request for change process in which the validation and
remaining process is id

We mentioned already that the downgrade checks must be initiated. There are three ways in which downgrade checks can
be initiated or triggered from the change transactions:
_ManuallyDowngrade checks are administered from the Downgrade Protection assignment block by clicking the
Perform Downgrade Check button (Figure 11.22).
_AutomaticallyChecks can be triggered during the release or import of a transport request. Additionally, they can be
triggered automatically if a change document is reassigned to a different maintenance project.
 _From a task listAn option is available within the task list to trigger the downgrade check. If a conflict is discovered, a
dialog box identifies the conflict to the user and directs the user to the SAP CRM Web UI where the conflict can be
further analyzed.

Key Features
As we mentioned, there are three options in which downgrade checks can be triggered. If conflicts are reported, SAP
Solution Manager will issue a warning type depending on the criticality of the object. The following list identifies the
warning types associated with the downgrade checks:
_Downgrade warningThis warning will occur during the export of a transport request and notifies you if identical
objects have not yet been imported into the production system.
_Imminent downgradeThis warning will occur during the import of a transport request and notifies