How To Fix K3062 - Partner version & of additive costs is no longer current

K3062 - Overview

• Message type: E = Error

• Message class: K3 - Material Cost Estimate

• Message number: 062

• Message text: Partner version & of additive costs is no longer current

What causes this issue?

You are executing a cost estimate with quantity structure. In the
<DS:GLOS.3526B726AFAB52B9E10000009B38F974>costing variant</>, it is
specified that additive costs are to be included.
Although the
<DS:GLOS.3526B71BAFAB52B9E10000009B38F974>additive cost estimate</> was
executed using the same costing variant, the
<DS:GLOS.3526B73AAFAB52B9E10000009B38F974>partner version</> specified
in the
<DS:GLOS.3526B71FAFAB52B9E10000009B38F974>costing type</> has since
changed.

System Response

The system cannot cost the material.

How to fix this error?

Recalculate the additive costs.
Create the cost estimate with quantity structure again.
&sys_admin&
In Customizing for Product Cost Planning, check the settings for the
costing type and partner version.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message K3062 - Partner version & of additive costs is no longer current ?

  The SAP error message K3062, which states "Partner version & of additive costs is no longer current," typically occurs in the context of controlling (CO) and cost accounting modules. This error indicates that the version of the partner (cost center, internal order, etc.) that is being referenced for additive costs is outdated or has been changed in a way that makes it no longer valid for the current transaction or operation.
  Causes:
  
  Version Changes: The partner version of the additive costs may have been changed or deleted in the system.
  Data Consistency Issues: There may be inconsistencies in the data related to the cost objects or partner versions.
  Configuration Changes: Changes in configuration settings related to cost accounting or controlling may have affected the validity of the partner version.
  Time Period Issues: The transaction may be trying to access a partner version that is not valid for the current fiscal period or has been closed.
  
  Solutions:
  
  Check