Object documentationIssue

 

An issue is a problem or project situation that affects project goals. An issue may result in changes to scope, budget, time line, or resources.

Example Example

In the construction industry, a site supervisor can log issues to request for additional resources or report the damage of materials caused by weather.

End of the example.

 

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

  • General issue

  • Technical issue

  • Issue requesting for information (RFI issue)

  • Risk issue

You can also define issue types relevant to your business. For example, you can define an issue type Quality Issue to categorize issues reported for quality-related defects. For more information, see Customizing for Project Issue and Change Management under Start of the navigation path Processing of Issues and Change Requests Next navigation step Define Issue and Change Request Types End of the navigation path.

Project Issue and Change Management also allows you to process issues with references to change requests. For more information, see Processing of Issues (with Change Requests) and Creating Change Requests (with References to Issues).

Structure

You can also specify values, add attachments, or assign related objects to an issue, 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 an issue that is being processed. Note that you can specify user-defined statuses and status maps in Customizing for Project Issue and Change Management under Start 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 an issue 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 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 an issue 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 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.

  • Attachments

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

  • Solution

    If you have recommendations on how a specific issue can be resolved, you can enter a free text proposal in Proposed Solution.

  • Related Reference Objects

    You can assign relevant issues, change requests, documents from Document Management System (DMS), or subobjects of the project hierarchy, to an issue. 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 issue. In such a deployment, you cannot assign project definitions to the issue, 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 issue. In such a deployment, you can assign project definitions since they are subobjects of the master project.

    End of the note.

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

  • Partners

    You can assign partners who are involved in the issue 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 underStart 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 Workspace (CA-CPD-WS); therefore the roles and responsibilities specified for a master project are also applicable in the processing of issues. For more information, see Teams and Roles.

  • Activities

    You can add and edit activities to an issue and can further set the status of each activity.

More Information

Integration with SAP Business Partner