How To Fix GL332 - CoCode/ledger & uses currency &, but CoCode/ledger & uses &

SAP Error Message - Details

• Message type: E = Error

• Message class: GL - FI-SL Rollup

• Message number: 332

• Message text: CoCode/ledger & uses currency &, but CoCode/ledger & uses &

What causes this issue?

Differences between the receiver and sender ledgers were found in the
second, third or fourth currency.
The receiver combination of company code/ledger &v1& that you defined
in Customizing uses currency &v2&, but the sender combination of
company code/ledger &v3& uses currency &v4&.

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

System Response

Rollup:
During rollup, all amount fields of the relevant currency group (HSL,
KSL, OSL) are in this case set to amount 0 in the rollup ledger unless,
in the rollup definition under "Extras -> Different Currencies" you set
the indicator "Do not initialize currency fields".
Copying planning templates:
Planning data cannot be copied.

How to fix this error?

Rollup:
If you activated the "Do not initialize currency fields" indicator, and
you have different second, third or fourth currencies, you can use a
user exit to enter the correct amount in the corresponding amount
fields (HSL, KSL, OSL). For example, you can use a user exit to have
the system calculate correct group currency amounts from the local
currency amounts.
Copying planning templates:
Change your entries.
&NOTE&
If you do not use a user exit to determine amounts in a third currency,
you can calculate these amounts later using the currency translation
program.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GL332 - CoCode/ledger & uses currency &, but CoCode/ledger & uses & ?

  The SAP error message GL332 typically indicates a mismatch between the currency settings of a company code (CoCode) and the ledger in the context of General Ledger (G/L) accounting. Specifically, it suggests that the company code and the ledger are configured to use different currencies, which can lead to inconsistencies in financial reporting and transactions.
  Cause:
  
  Currency Configuration Mismatch: The company code is set to use a specific currency (e.g., local currency), while the ledger is configured to use a different currency (e.g., group currency or a different local currency).
  Incorrect Master Data: The master data for either the company code or the ledger may have been incorrectly set up, leading to this inconsistency.
  Transaction Posting Issues: If a transaction is being posted that involves both the company code and the ledger, and they are set to different currencies, this error will occur.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the configuration settings for the company code and the ledger in SAP.
  Ensure that both are set to use the same currency. You can check this in the following paths:
  
  For Company Code: SPRO ? Financial Accounting ? General Ledger ? Master Data ? G/L Account ? Prepare G/L Account Creation ? Define Company Code.
  For Ledger: SPRO ? Financial Accounting ? General Ledger ? Master Data ? G/L Account ? Prepare G/L Account Creation ? Define Ledger.
  
  
  
  
  
  Adjust Master Data:
  
  If the configuration is correct but the error persists, check the master data for the G/L accounts involved in the transaction. Ensure that the currency settings are consistent with the company code and ledger.
  
  
  
  Review Transaction:
  
  If the error occurs during a specific transaction, review the details of that transaction to ensure that it aligns with the currency settings of the company code and ledger.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for further guidance on currency settings and configurations.
  
  
  
  Contact SAP Support:
  
  If the issue cannot be resolved through configuration checks, consider reaching out to SAP support for assistance.
  
  
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like OBY6 (to check company code settings) and OB22 (to check ledger settings) to review the configurations.
  Currency Types: Understand the different types of currencies in SAP, such as local currency, group currency, and transaction currency, to ensure proper configuration.
  Impact on Reporting: Be aware that mismatched currencies can affect financial reporting and consolidation processes, so it’s crucial to resolve these issues promptly.
  
  By following these steps, you should be able to identify and resolve the cause of the GL332 error in SAP.