Object documentationChange Request

 

A change request is a variation or deviation in the objective, form, nature, content, or the future course of a project. A change request is typically created and processed to resolve an issue that is analyzed and found to have a significant cost or schedule impact in the project.

 

You can create change requests for specific change request types. In the standard system, SAP delivers the following change request types for problems related to projects:

You can also define change request types relevant to your business. For example, if you have changes related to quality, you can define a change request type specifically for the purpose of quality. For more information, see Customizing for Project Issue and Change Management underStart of the navigation path Processing of Issues and Change Requests Next navigation step Define Issue and Change Request Types End of the navigation path.

It is not necessary that a change request is used only for resolving one issue. There are project situations where multiple changes can be addressed by one solution. In such cases, you can create a collective change request to resolve a set of related issues and changes. For example, if there are two change requests, each corresponding to the renovation of the two wings of a cafeteria, you can create a collective change request for the electrical work to be done in both the wings.

Structure

You can also specify values, add attachments, or assign related objects to a change request, so that the processors of the issue have all the information required for processing it. This information is documented or available in the following fields and UI blocks:

  • Status

    The status indicates the level of the progress of a change request that is being processed. Note that you can specify user-defined statuses and status maps in Customizing for Project Issue and Change Management underStart of the navigation path Processing of Issues and Change Requests Next navigation step Manage Statuses End of the navigation path .

  • Impact

    The impact indicates how critical a change request is with respect to the result, target, or function of the project. You can define impact codes that indicate the impact an issue can have on a project, if the issue is not resolved. SAP delivers the following impact codes in the standard system:

    • 1 (Minor)

    • 2 (Major)

    • 3 (Critical)

    You can also define impact codes relevant to your business. For more information, see Customizing for SAP Project Issue and Change Management under Start of the navigation path Processing of Issues and Change Requests Next navigation step Define Impact End of the navigation path .

  • Priority

    The priority indicates how time-critical a change request is for a project. You can define priority codes that indicate the priority with which an issue must be handled. SAP delivers the following priority codes in the standard system:

    • 1 (Very High)

    • 2 (High)

    • 3 (Medium)

    • 4 (Low)

    You can also define priority codes relevant to your business. For more information, see Customizing for SAP Project Issue and Change Management under Start of the navigation path Processing of Issues and Change Requests Next navigation step Define Priorities End of the navigation path .

  • Solution

    If you have recommendations on how a specific change request can be processed in order to resolve an issue, you can enter a free text proposal in Proposed Solution.

  • Cost estimation alternatives (relevant for integration with Project Cost and Revenue Planning (CA-CPD-FP))

    When you create a change request based on an approved plan version, it is possible that you need to plan detailed costs for one or more cost estimation alternatives on the active financial plan. Cost estimation alternatives allow you to maintain unique links between a change request and a financial plan.

  • Activities

    You can add activities to a change request and edit and set the status of each activity.

  • Related reference objects

    You can assign relevant issues, change requests, documents from Document Management System (DMS), or subobjects of the project hierarchy, to a change request. The assignment of project subobjects (Project Objects) allows you to identify the areas of the project that have problems.

    Note Note

    • If you use Project System (PS) projects, in a standalone deployment scenario, you have the possibility to assign work breakdown structure elements, networks, and network activities to the change request. In this type of deployment, you cannot assign project definitions to the change request, since project definitions are the top nodes of the hierarchy.

    • If you use master projects, in an integrated scenario with Project Workspace (CA-CPD-WS), you have the possibility to assign any subobject of the master project hierarchy to the change request. In such a deployment, you can assign project definitions since they are subobjects of the master project. Additionally, you can also assign purchase orders related to approved changes.

    End of the note.

    For more information about referencing and assigning objects, see Object Relationships: References and Assignments.

  • Attachments

    You can attach relevant documents or add URLs to a change request, so that the processor of the change request has sufficient reference material required for routing or resolving the required change. You can attach documents from your local system. For more information, see Attaching Documents and Linking to References (Change Request).

  • Partners

    You can assign partners who are involved in the change request and even specify roles for each partner. Note that you create partners using the Maintain Business Partner screen (transaction BP) and make settings for partners in Customizing for Project Issue and Change Management under Start of the navigation path Processing of Issues and Change Requests Next navigation step Define Business Partner Roles End of the navigation path. Project Issue and Change Management is integrated with Roles and Responsibilities from Project Workspace (CA-CPD-WS). Therefore the roles and responsibilities specified for a master project are also applicable in the processing of change requests. For more information, see Teams and Roles.

  • Document history

    The Document History button in a change request allows you to display the log of updates made to an existing change request. For example, when the status is changed or a business partner is assigned, the Document History feature logs these updates.

More Information

Integration with SAP Business Partner