How To Fix G3221 - Non-matching local currencies in company codes for following companies:

SAP Error Message - Details

• Message type: E = Error

• Message class: G3 - Messages for SAP Consolidation: Integration

• Message number: 221

• Message text: Non-matching local currencies in company codes for following companies:

What causes this issue?

While checking the master records, it was established that for some
company/company code assignments, the company and company code are
using different local currencies.

System Response

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

How to fix this error?

Change the assignment of company codes to the companies in the
Customizing of the enterprise structure or change the local currency of
the corresponding company codes or company.

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 G3221 - Non-matching local currencies in company codes for following companies: ?

  The SAP error message G3221 indicates that there is a mismatch in the local currencies of the company codes involved in a transaction. This typically occurs when you are trying to post a transaction that involves multiple company codes, and those company codes have different local currencies set up in their configurations.
  Cause:
  
  Different Local Currencies: The company codes involved in the transaction have different local currencies defined in their settings. For example, if Company Code A is set to USD and Company Code B is set to EUR, this error will occur when trying to post a transaction that involves both company codes.
  Incorrect Configuration: The company codes may not be configured correctly in terms of currency settings, leading to inconsistencies.
  Transaction Type: Certain transactions may require that all company codes involved use the same local currency.
  
  Solution:
  
  
  Check Company Code Settings:
  
  Go to the transaction code OBY6 (or use the path: SPRO > Financial Accounting > General Ledger > Master Data > G/L Account > Prepare for Migration > Define Company Code).
  Verify the local currency settings for each company code involved in the transaction. Ensure that they are set to the same currency if they need to interact with each other.
  
  
  
  Adjust Transaction:
  
  If the transaction can be adjusted to involve only one company code or to use a different approach that does not require multiple company codes, consider doing so.
  
  
  
  Currency Conversion:
  
  If the business process allows, consider using currency conversion to standardize the currencies involved in the transaction.
  
  
  
  Consult with Finance Team:
  
  Discuss with your finance team or SAP consultant to understand the implications of changing local currencies and to ensure compliance with accounting standards.
  
  
  
  Review Documentation:
  
  Check SAP documentation or help resources for any specific guidelines related to currency settings and transactions involving multiple company codes.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBY6, OB22 (for defining currencies), and OBY1 (for company code settings).
  SAP Notes: Look for SAP Notes related to currency configuration issues, as they may provide additional insights or patches.
  Testing: After making changes, conduct thorough testing to ensure that the issue is resolved and that no new issues arise from the changes made.
  
  By addressing the local currency mismatch, you should be able to resolve the G3221 error and proceed with your transactions.