Do you have any question about this error?
Message type: E = Error
Message class: GL - FI-SL Rollup
Message number: 339
Message text: Receiver ledger & stores &, but company code/ledger & do not
Receiver ledger &v1& stores &v2&, but the company code/ledger
combination &v3& does not. It is also possible that ledger &V4& does
not store &V2&.
This means that only initial values will be transferred to the data
fields of this field group.
If you therefore store the field group in the receiver ledger because
it is filled from other ledgers, an evaluation will give incorrect
results. You should therefore consider whether you can transfer the
field group with consistent data using a user exit.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
If the field group will never be evaluated, you should set it to
inactive for the receiver ledger in configuration.
Note
You can define whether &v2& is to be stored both in the ledger
definition and in the company code -> ledger assignment or the global
company -> ledger assignment (&v2& is stored if one of the two
indicators is set).
Error message extract from SAP system. Copyright SAP SE.
GL339
- Receiver ledger & stores &, but company code/ledger & do not ?The SAP error message GL339 typically indicates a mismatch between the company code and the ledger in the context of a financial transaction. This error occurs when the system is unable to find a valid combination of company code and ledger in the configuration settings.
Cause:
- Configuration Issues: The company code and ledger may not be properly configured in the system. This can happen if the ledger is not assigned to the company code in the configuration settings.
- Missing Assignments: The specific ledger you are trying to use may not be assigned to the company code in the General Ledger (G/L) settings.
- Data Entry Errors: There may be a typo or incorrect entry in the transaction data, leading to the mismatch.
- Inactive Ledger: The ledger you are trying to use might be inactive or not available for the specified company code.
Solution:
Check Configuration:
- Go to the SAP Customizing Implementation Guide (SPRO).
- Navigate to Financial Accounting (New) > General Ledger Accounting (New) > Master Data > G/L Accounts > Preparation > Define Company Code and Ledger Assignment.
- Ensure that the ledger is assigned to the correct company code.
Verify Ledger Settings:
- Check if the ledger is active and properly configured for the company code.
- Ensure that the ledger is set up for the correct fiscal year and is not restricted.
Review Transaction Data:
- Double-check the transaction data for any typos or incorrect entries.
- Ensure that the correct company code and ledger are being used in the transaction.
Consult Documentation:
- Review SAP documentation or help files related to General Ledger configuration for any additional insights.
Testing:
- After making the necessary changes, try to reprocess the transaction to see if the error persists.
Related Information:
OB22
to check the ledger assignments or FS00
to view G/L account details.If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in Financial Accounting.
Get instant SAP help. Start your 7-day free trial now.
GL338
You can only roll up data from local to global ledgers with fixed company
What causes this issue? You are trying to roll up data from a local to a global ledger. However, you can only do so if you roll up the data to a fixe...
GL337
Global company/ledger & uses currency &, but comp.code/ledger & uses &
What causes this issue? Differences between the receiver and sender ledgers were found in the second, third or fourth currency. The receiver combinat...
GL340
Receiver ledger & stores &, but global company/ledger & do not
What causes this issue? Receiver ledger &v1& stores &v2&, but the global company/ledger combination &v3& does not. It is als...
GL341
Special periods only allowed with a sender fiscal year variant
What causes this issue? You have set the 'Special periods' indicator. However, different fiscal year variants (see Customizing) are used i...
Click on this link to search all SAP messages.