How To Fix RPM_UTILITIES017 - No entry in derived attributes table &

SAP Error Message - Details

• Message type: E = Error

• Message class: RPM_UTILITIES - Messages for Tools and Utilities

• Message number: 017

• Message text: No entry in derived attributes table &

What causes this issue?

Each project and project template in table CGPL_PROJECT has to have a
corresponding entry in table RPM_PROJECT_DER. This table contains all
derieved attributes of a project (e.g. risk status). If the entry in
table RPM_PROJECT_DER is missing then the dashboard will display '?'.
Source table of this check:
Table: CGPL_PROJECT
GUID: &V2&

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Target table of this check:
Table: &v1&
GUID: &V2&
<ZH>Error: A record with this GUID does not exist. </>

System Response

In the project dashboard this project will show '?' instead of the
appropriate statuses (e.g. for the scheduling and staffing status).

How to fix this error?

This error can be corrected by executing program
RPM_PROJECT_SAVE_DERIVED_DATA for the project &v3&.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RPM_UTILITIES017 - No entry in derived attributes table & ?

  The SAP error message RPM_UTILITIES017 indicates that there is "No entry in derived attributes table." This error typically occurs in the context of SAP's Resource and Portfolio Management (RPM) module, particularly when the system is trying to access or process derived attributes that are not defined or missing in the relevant tables.
  Causes:
  
  Missing Configuration: The derived attributes may not have been configured properly in the system.
  Data Inconsistency: There may be inconsistencies or missing entries in the database tables that store derived attributes.
  Incorrect Customization: If there have been recent changes or customizations to the RPM module, it may have led to the removal or alteration of necessary entries.
  Transport Issues: If the system has recently undergone a transport of changes, it’s possible that the derived attributes were not included or were not transported correctly.
  
  Solutions:
  
  Check Configuration: Verify the configuration settings for derived attributes in the RPM module. Ensure that all necessary attributes are defined and correctly set up.
  Data Validation: Use transaction codes like SE11 or SE16 to check the relevant database tables (e.g., derived attributes table) for missing entries. If entries are missing, they may need to be added manually or through a data migration process.
  Review Customizations: If there have been recent changes, review the custom code or configurations to ensure that they are not causing the issue. Revert any changes if necessary.
  Transport Check: If the issue arose after a transport, check the transport logs to ensure that all necessary objects were included and transported correctly. If not, you may need to re-transport the missing objects.
  Consult Documentation: Refer to SAP documentation or notes related to RPM and derived attributes for any specific guidance or known issues.
  Contact SAP Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They may provide patches or additional insights into the problem.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE16 (Data Browser), and SPRO (Customizing).
  SAP Notes: Search for SAP Notes related to RPM and derived attributes for any known issues or fixes.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed.
  
  By following these steps, you should be able to identify the root cause of the RPM_UTILITIES017 error and implement a suitable solution.