How To Fix AO_PLANNING103 - App. request &1 variant &2: versions have different currency translation

AO_PLANNING103 - Overview

• Message type: E = Error

• Message class: AO_PLANNING - Message Class for Project WGRS-4B4R6S

• Message number: 103

• Message text: App. request &1 variant &2: versions have different currency translation

What causes this issue?

Variant &V2& of appropriation request &V1& is assigned to more than one
version, in which different exchange rate types have been specified for
currency translation.

System Response

The variant is not translated. The program terminates.

How to fix this error?

Change the assignment of the variant the the versions, or change the
exchange rate types in the versions involved so that they are all the
same.

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 AO_PLANNING103 - App. request &1 variant &2: versions have different currency translation ?

  The SAP error message AO_PLANNING103 indicates that there is a discrepancy in currency translation between different versions of a planning application request. This typically occurs in the context of SAP Analytics Cloud (SAC) or SAP Business Planning and Consolidation (BPC) when trying to execute a planning function or report that involves multiple versions of data that are expected to be in the same currency.
  
  Cause:
  
  Different Currencies: The versions involved in the planning request may be using different currencies. For example, one version might be in local currency while another might be in a reporting currency.
  Currency Translation Settings: The settings for currency translation may not be consistent across the versions. This can happen if different translation methods or rates are applied to different versions.
  Data Source Configuration: The data sources for the versions may be configured differently, leading to inconsistencies in how currency is handled.
  
  
  Solution:
  
  Check Version Settings: Review the settings for each version