How To Fix GC882 - Currencies of the companies are not allowed

SAP Error Message - Details

• Message type: E = Error

• Message class: GC - Error Messages for Consolidation/Extended General Ledger

• Message number: 882

• Message text: Currencies of the companies are not allowed

What causes this issue?

In a local currency group, the currencies of all included
<GL:company>companies</> must be identical to the
<GL:group_currency>group currency.</>
In this case, a <GL:trading_partner>trading partner</> is being posted
whose currency differs from that of the company to be posted to.

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

There are two possible causes:
The <GL:document_type>document type</> posts in
<GL:local_currency>local currency</> instead of group currency
You chose an incorrect <GL:company_pair>company pair</>.

System Response

Error message

How to fix this error?

Please check the currency assignment of the document type or the
companies to be posted to.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GC882 - Currencies of the companies are not allowed ?

  The SAP error message GC882, which states "Currencies of the companies are not allowed," typically occurs in the context of financial transactions involving multiple company codes that have different currencies. This error indicates that the currencies of the involved company codes are incompatible for the transaction being processed.
  Cause:
  
  Different Currencies: The primary cause of this error is that the company codes involved in the transaction are set up with different local currencies. For example, if Company Code A uses USD and Company Code B uses EUR, a transaction attempting to process between these two will trigger this error.
  Transaction Type: Certain transactions may require that the company codes involved share the same currency, especially in intercompany transactions.
  Configuration Issues: There may be configuration settings in the SAP system that restrict transactions between company codes with different currencies.
  
  Solution:
  
  
  Check Company Code Settings: Verify the currency settings for the company codes involved in the transaction. You can do this by navigating to the company code configuration in the SAP system:
  
  Use transaction code OBY6 to check the currency settings for each company code.
  Ensure that the currencies are compatible for the transaction you are trying to execute.
  
  
  
  Use a Common Currency: If the transaction requires a common currency, consider converting the amounts to a common currency before processing the transaction. This may involve using exchange rates to convert the currencies appropriately.
  
  
  Intercompany Transactions: If the transaction is an intercompany transaction, ensure that the intercompany settings are correctly configured. This may involve setting up intercompany pricing and ensuring that both company codes are configured to handle transactions in multiple currencies.
  
  
  Consult Documentation: Review SAP documentation or consult with your SAP support team for specific configuration settings that may need to be adjusted to allow transactions between different currencies.
  
  
  Error Handling: If the error persists after checking the above points, consider implementing error handling procedures in your transaction processing to catch and manage such errors effectively.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBY6 (Company Code Global Settings) and OB22 (Define Company Code Currency) for checking and modifying currency settings.
  Exchange Rate Configuration: Ensure that exchange rates are maintained correctly in the system using transaction code OB08.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message, as there may be specific fixes or recommendations provided by SAP.
  
  By following these steps, you should be able to identify the cause of the GC882 error and implement a solution to resolve it.