Fusion General Ledger problems are usually sequence problems. Journal Import fails on validation against the ledger, calendar or chart of accounts. A period will not close while subledgers still hold unaccounted transactions or journals remain unposted. Both are resolved by working the dependency chain in order rather than by attacking the visible symptom.
What problem does this solve?
Journal Import failures are validation failures: an invalid account combination, a closed or unopened period, a currency without a rate, or a source and category the ledger does not accept.
Periods that will not close are almost never a GL fault. A subledger still holds unaccounted transactions, or journals sit unposted, and GL is correctly refusing to close over them.
Unposted journals accumulate quietly because posting is often assumed to be automatic. Where posting runs on a schedule, a failed run leaves journals in limbo with no alert to anyone.
How the solution works
We work the close as a dependency chain — subledger exceptions, then posting, then reconciliation, then close — so the blocking item is identified on the first pass rather than the fourth.
Journal Import errors are read from the error table rather than inferred; the rejection identifies the line and the validation that failed.
- 1Identify the rejected lines and the specific validation that failed for each.
- 2Confirm the combination exists, is enabled, and is not disabled for posting.
- 3Confirm the accounting period is open and a rate exists for every foreign currency line.
- 4Resolve unaccounted transactions in each subledger before attempting to close.
- 5Confirm no journals remain unposted, including those created by scheduled processes.
- 6Prove subledger to GL agreement, then close the period.
Limitations & prerequisites
- GL will not close over subledger exceptions by design; forcing a close is not available and would be wrong if it were.
- Dynamic account combination creation depends on flexfield configuration; where it is disabled, valid-looking combinations will reject until created.
- Reopening a closed period is possible but has reporting and audit implications that should be agreed rather than assumed.
- Scheduled posting failures are silent unless monitored, so absence of errors in the user interface does not mean everything posted.
- Currency rate loads are a recurring dependency; a missing rate fails at period end rather than at transaction entry.
FAQ
A validation rejected the line: an invalid or disabled account combination, a period that is not open, a missing currency rate, or a source and category the ledger does not accept. The import error table names the failing line and reason — read it before changing any data.
Something upstream is not finished. Typically a subledger still holds unaccounted transactions, or journals remain unposted. Close subledgers in dependency order and confirm posting completed before attempting the GL close.
Yes, but agree the consequences first. Reporting already issued from the closed position becomes inconsistent, and auditors will ask what changed and why. It should be an exception with a documented reason, not part of the monthly routine.
Usually a scheduled posting process failed and nobody was notified. Monitor the posting job as an interface rather than assuming it ran, and check for unposted journals as an explicit close step.
The combination does not exist, is disabled, or violates a cross-validation rule. Where dynamic insertion is turned off, the combination must be created before the journal will import.
Move exception detection earlier. Most close time is spent finding problems, not fixing them, so running unaccounted and unposted checks from day one of the close typically saves more than any automation of the posting steps themselves.
Tell us the module, the release and the exact symptom.
Send the module in scope, your Fusion release or EBS version, and the exact error text or symptom with a screenshot where you have one. We reply with a written assessment: the likely cause, what we would check first, and whether it is a configuration fix, a data fix, or a defect that needs an Oracle service request. When Swedish Technology can help, we scope the remediation with effort and sequence before you commit to anything.
Request an Oracle AssessmentSources & evidence
- Oracle Help Center — Cloud Applications documentation — module setup, subledger accounting and period-close reference
- Oracle Help Center — all product documentation — database, middleware and infrastructure reference used for error diagnosis
- My Oracle Support — patches, known-issue notes and service requests; Oracle account required
Vendor and product names are trademarks of their respective owners; references are for technical context and do not imply partnership, certification or endorsement unless stated on the vendor's official pages.