How To Fix K8138 - The price for resource &1 has been defined using different currencies

K8138 - Overview

• Message type: E = Error

• Message class: K8 - CO Planning: Messages for Function Group KAPP

• Message number: 138

• Message text: The price for resource &1 has been defined using different currencies

What causes this issue?

The price for resource &V1& has been defined using different
currencies. However, in CO Planning, you are only allowed to use one
currency per fiscal year.

System Response

In planning, the R/3 System takes a resource price of zero for the
valuation.

How to fix this error?

Maintain valid prices for resource &V1& for WBS element &V2&, fiscal
year &V3&, version &V4&, so that the price determination strategy finds
the price in only one currency.
You can analyze the price determination if you activate condition
analysis for the valuation variants used for version &V4& in fiscal
year &V3&.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message K8138 - The price for resource &1 has been defined using different currencies ?

  The SAP error message K8138 indicates that there is a discrepancy in the currency settings for a resource in the system. Specifically, it means that the price for a resource has been defined in different currencies, which can lead to inconsistencies and issues in cost calculations and reporting.
  
  Cause:
  
  Multiple Currency Definitions: The resource in question has been assigned prices in different currencies, which is not allowed in the context of the specific transaction or configuration you are working with.
  
  Configuration Issues: There may be a configuration issue in the controlling area or the master data settings for the resource.
  Data Entry Errors: Manual entry errors during the creation or maintenance of the resource master data could lead to this issue.
  
  
  Solution:
  
  
  Check Resource Master Data:
  
  Go to the resource master data (transaction code CR01 or CR02) and check the pricing information for the resource identified by &1 in the error message.
  Ensure that all price entries for