General Ledger FAQ for Journal Posting

List of Posting Status Errors and possible Solutions:

Error: Showing batch control total violation

Solution: The batch totals do not match the entered batch control amount. You need to enter the correct amounts in lines or correct the batch control total.

Error: Selected for posting to an unopened period

Solution: The GL period is not open. You need to open the GL periods of the journals and the reversal periods if populated in the journal. You may also want to change the journal period (in the Enter Journals form there is a button for that). Then you should follow steps 5 and 6 above.

Error: Showing no journal entries for this batch

Solution: The batch has no unposted journal headers. You need to review the General Ledger Journal Data Collection Test as advised in step 4 above, and check the status of the batch, journals and lines. If there are no journals or lines then you need to enter journals with lines or delete the batch in the Review Batch window. If the headers or lines are already posted (status='P') but the batch is not, then you may have a data corruption and you should log a Service Request for support.

Error: Showing journal control total violation

Solution: The journal totals do not match the entered journal control amount. You need to enter the correct amounts in lines or correct the journal control total. If you don't want to use the control then you can leave this field blank.

Error: Showing multiple problems preventing posting of batch

Solution: Currently this error should not occur. If it does then you need to review the General Ledger Journal Data Collection Test as advised in step 4 above, and check the status of the batch, journals and lines.

Error: Showing an unbalanced journal entry but suspense not allowed

Solution: The journal is unbalanced (total debits not matching total credits). For a journal to be posted it must be balanced or the suspense posting must be enabled.

a) If you do not want to enable suspense posting then you need to correct the amounts or enter any missing lines.
Remember:

• In functional currency journals: the Entered_Dr should equal the Entered_Cr and the Accounted_Dr should equal the Accounted_Cr
• In foreign currency journals: you will only be able to change the converted columns if the profile 'Journals: Allow Multiple Exchange Rates' is set to Yes, otherwise the amounts are converted using the currency rate.

b) In case the lines are correct but for some reason the totals got incorrect, you can correct them using the Change Currency button to convert to a different currency and then change it back to the original.

c) If the case is with imported journals and is not possible to update them then please see Document 856708.1: R12: Imported Journal getting Error6 Status when Posting.

d) If the journals are cross-currency journals (invoices and payments or receipts in different currencies) then you need to enter the suspense account (even if the suspense accounting is not enabled) because the system segregates the journals by currency and the suspense account is useed to balance each currency journal. In the end the suspense account is balanced.

e) The bugs referred in alert Document 1376579.1 can cause missing imported lines, i.e. incomplete unbalanced journals, or lines flagged as processed in the interface but no corresponding journal.
In this cases you need to log a Service Request for support to provide a datafix.

Error: Showing invalid journal entry lines or no journal entry lines

Solution: The journal have lines with invalid accounts, or does not have unposted lines. You need to review the General Ledger Journal Data Collection Test as advised in step 4 above, and check the headers and  lines of journals and correct them.

The field STATUS in the GL_JE_HEADERS may give important information about the problem:

- : Bad rounding account
> : Reserved for country specific functionality
< : Reserved for country specific functionality
U : Unposted
P : Posted
1 : Invalid currency code
2 : Invalid source
3 : Invalid category
4 : Invalid set of books
5 : Invalid set of books
6 : (Actual) Unopened period
6 : (Budget) Invalid budget version
6 : (Encumbrance) Invalid encumbrance type
7 : Invalid entry
8 : Invalid entry
A : Code combination does not exist
B : Multiple lines have code combination error
C : Code combination: detail posting not allowed
D : Multiple lines have code combination error
E : Multiple lines have code combination error
F : Code combination not enabled
G : Multiple lines have code combination error
H : Multiple lines have code combination error
I : Multiple lines have code combination error
J : Code combination not yet effective (date)
K : Multiple lines have code combination error
L : Multiple lines have code combination error
M : Code combination past effective date
N : Multiple lines have code combination error
O : Multiple lines have code combination error
Q : Multiple lines have code combination error
R : Multiple lines have code combination error
T : Multiple lines have code combination error
V : Multiple lines have code combination error
Z : Multiple lines have code combination error

a) If the journal has no lines you may wish to delete it in the Review Journals window.

b) This is usually due to invalid accounts used in the journal entry. When you try to query the journal it may show "posting is not allowed for this account". You should check if the combination exists and is enabled and valid and the qualifiers allow posting to it. Check also the natural account segment value.
You may need to act on the code combination or else change the journal line account.

Error: Showing unbalanced encumbrance entry without reserve account

Solution: Encumbrance journals can be unbalanced when posting, but the system will generate the required entries to balance it using the Reserve for Encumbrances account defined in the Ledger or Set f Books.
Remember to check this setup in the Reporting Currency ledgers or set of books and also in Secondary ledgers associated.

The reporting Ledger should inherit the account from the primary ledger, so if the value for this account is null in the reporting ledger please log a service request to get a fix. This can happen when the Primary and its Reporting Currency Ledger are created  together from Create Accounting Setup page and the Primary Ledger is Budgetary Control enabled but the Reporting Currency Ledger (at subledger level) is not.
 

Error:  Showing an encumbrance journal entry with no encumbrance type

Solution: Encumbrance journals must have an encumbrance type assigned, which is missing.
Unknown cause, this is a very rare situation, probably due to unsupported updates to the data.
Eventually the log file of the posting process can show some clue for the problem.

Error:  Showing unbalanced journal entry by account category

Solution: This is probably caused by the setup of the profile option GL:Enforce Category Account Balancing, which, if set to Yes will enforce the journals to balanced not only by balancing segment but also by category. If not using Public Sector Financials this is recommended to be set to No.

Error:  Funds reservation failed

Solution: This occurs because budgetary control is enabled and at least one account in this journal was found not having enough funds available. This can happen to a detail account or to a summary account with the budgetary control enabled.
To see in detail what was the account and the problem you need to query the journal, go to the View Results (Budgetary Control Results window).

This error should not occur for journals that have the funds reserved in the subledger (for example POs and Payables Invoices).
If this occurs then confirm the setup of the Profile option Budgetary Control Group is pointing to the correct Control Group and that this has the correct setup.

Error:  Showing invalid period and conversion information for this batch

Solution: Unknown cause. This is a very rare situation. 
It probably is the result of unsupported updates to the data (possibly journal batch or header is using an incorrect period name). You need to review the General Ledger Journal Data Collection Test as advised in step 4 above, and check the period names. Eventually the log file of the posting process can show some clue for the problem.