How To Fix DPR_CALC016 - Cost/revenue rate &1, &2: incorrect plan version

DPR_CALC016 - Overview

• Message type: E = Error

• Message class: DPR_CALC - cProjects Costing Integration

• Message number: 016

• Message text: Cost/revenue rate &1, &2: incorrect plan version

What causes this issue?

The active plan version for organizational management in the cProjects
system varies from the active plan version in the ERP system.

System Response

The system does not replicate the data record in question.

How to fix this error?

Use the same active plan version in both the cProjects system and the
ERP system. You can find the corresponding Customizing activity in the
ERP system in Customizing for Basis or in Customizing for SAP Web
Application Servers (in the cProjects system) under <LS>Business
Management</> --> <LS>SAP Business Workflow</> --> <LS>Basic Settings
(Organizational Management)</> --> <DS:SIMG.SIMG_WF14OOAP>Set Active
Plan Version</>.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DPR_CALC016 - Cost/revenue rate &1, &2: incorrect plan version ?

  The SAP error message DPR_CALC016 indicates that there is an issue with the cost/revenue rate in a specific planning version within the SAP Project System (PS) or the SAP Portfolio and Project Management (PPM) module. This error typically arises when the system is unable to find the correct planning version for the specified cost or revenue rate.
  
  Cause:
  
  Incorrect Planning Version: The planning version specified in the transaction or report does not exist or is not correctly set up in the system.
  Data Inconsistency: There may be inconsistencies in the data related to the planning version, such as missing entries or incorrect configurations.
  Authorization Issues: The user may not have the necessary authorizations to access the specified planning version.
  
  Configuration Issues: The configuration settings for the project or planning version may not be correctly defined.
  
  
  Solution:
  
  Check Planning Version: Verify that the planning version specified in the transaction is correct and exists in the system. You can