Do you have any question about this error?
Message type: E = Error
Message class: G3 - Messages for SAP Consolidation: Integration
Message number: 222
Message text: Company &1 (LC = &2), company code &3 (LC = &4)
While checking the master records, it was established that the company
&V1& and the company code &V3& are using different local currencies.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
In the Customizing of the enterprise structure, assign company code
&V3& a different company with the corresponding local currency or
change the local currency of company code &V3& or the company &V1&.
Error message extract from SAP system. Copyright SAP SE.
G3222
- Company &1 (LC = &2), company code &3 (LC = &4) ?The SAP error message G3222 typically indicates an issue related to the company code and local currency settings in the system. This error can arise in various scenarios, such as during document posting, financial reporting, or when executing certain transactions that involve company codes and their respective local currencies.
Cause:
The error message G3222 is generally caused by one of the following issues:
- Mismatch in Local Currency Settings: The local currency (LC) for the company code does not match the expected local currency for the transaction or document being processed.
- Configuration Issues: There may be a configuration issue in the Financial Accounting (FI) module where the local currency settings for the company code are not properly defined.
- Missing or Incorrect Master Data: The master data for the company code or related entities (like vendors, customers, or materials) may not be set up correctly, leading to inconsistencies in currency settings.
Solution:
To resolve the G3222 error, you can take the following steps:
Check Company Code Configuration:
- Go to the transaction code
OBY6
(or navigate through the menu: SPRO > Financial Accounting > Financial Accounting Global Settings > Company Code > Edit, Copy, Delete, Check Company Code).- Verify that the local currency for the company code is correctly defined and matches the expected currency for the transaction.
Review Transaction Currency:
- Ensure that the currency used in the transaction matches the local currency defined for the company code. If you are trying to post a document in a different currency, ensure that the necessary exchange rates are maintained.
Check Master Data:
- Review the master data for the relevant entities (vendors, customers, etc.) to ensure that their currency settings are consistent with the company code's local currency.
Consult with Configuration Team:
- If you are unable to resolve the issue, consult with your SAP configuration team or a functional consultant who specializes in Financial Accounting to review the settings and make necessary adjustments.
Testing:
- After making changes, perform a test transaction to ensure that the error no longer occurs.
Related Information:
OBY6
, OB22
(for currency settings), and OB08
(for maintaining exchange rates).By following these steps, you should be able to identify and resolve the underlying cause of the G3222 error message in SAP.
Get instant SAP help. Start your 7-day free trial now.
G3221
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...
G3220
Data was already saved
What causes this issue? The Programm has determined that no data has been changed since the last time you saved. It is not necessary to save the data...
G3223
Company &1 and company code &2 have different local currencies
What causes this issue? While checking the master records, it was established that the company &V1& and the company code &V2& are usi...
G3224
Unable to print the settings for the SAP Cons. System
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.