Script Library › General Ledger › GL-07
GL-07 Oracle Fusion Cloud General Ledger Guided Actions

GL Period Close Readiness (Oracle Fusion)

Fusion GL close readiness via OTBI, BIP, REST, and ESS — unposted journals, clearing account balances, journal batch status, intercompany imbalances, and Close Ledger job history.

Get Full Script → ← Back to Library
PlatformOracle Fusion Cloud
Input RequiredPeriod Name and Ledger Name
Diagnostic ChecksOTBI + BIP + REST
Data SourcesOTBI / REST / BIP
Fix OptionsGuided UI Actions
The Problem

Why This Fails — and What It Costs

Oracle Fusion Cloud GL period close diagnostics operate in a fundamentally different environment than EBS R12 — the subledger transfer, journal posting, and period close processes are managed through Enterprise Scheduler Service (ESS) jobs, the Fusion Manage Accounting Periods screen, and OTBI reporting rather than through direct database queries. The Fusion GL close sequence — complete subledger accounting, post all journals, run revaluation, run translation, close the period — is the same as EBS R12, but each step is monitored through different tooling.

The most common Fusion GL close blocker is an ESS Create Accounting job that completed with errors in one of the subledger applications. The error details appear in the Create Accounting Execution Report — a BIP report that shows the specific journal entry, the error type (typically an invalid account combination or a missing accounting rule), and the transaction reference. Unlike EBS R12 where XLA events can be queried directly, Fusion requires navigating to the BIP report to understand the error and then correcting the source transaction or the accounting rule configuration.

The Fusion Close Ledger process is more automated than the EBS R12 process — Oracle Fusion has a Close Monitor feature that shows the real-time status of each close step across all subledgers. However, the Close Monitor requires that each step be explicitly submitted, and a step that is stuck in Pending or In Progress status can block subsequent steps from starting. GL-07 provides a systematic approach to reading the Close Monitor status, identifying stuck ESS jobs, and determining the correct resolution path for each blocking condition.

GL-07 provides a structured Fusion GL period-close diagnostic using OTBI GL Journal Entries subject area for unposted journal analysis, the ESS job history for Create Accounting status, the Fusion Close Monitor for step-by-step close status, BIP Create Accounting Execution Report for error detail, and the Manage Accounting Periods screen for period status. It produces a close readiness checklist with the exact ESS program names for each blocking condition.

Diagnostic Coverage

What This Script Diagnoses

GL-07 systematically investigates every major condition that can cause the issue this diagnostic targets. Below is the complete coverage breakdown.

Close Monitor Status
Fusion Close Monitor step-by-step status for each subledger and GL close step. Identifies which steps are Pending, In Progress, Completed with Errors, or Complete.
Create Accounting ESS Analysis
ESS job history for Create Accounting across all subledger applications. BIP Create Accounting Execution Report interpretation for error-level detail.
OTBI Unposted Journals
GL Journal Entries subject area query for unposted journal batches — count, amount, source, approver, and age. Identifies batches blocking the Post Journals close step.
Period Status in Fusion
Manage Accounting Periods status for GL and all subledger applications. Confirms all subledgers are in the correct status before GL close can proceed.
Sample Diagnostic Output

Example Completed Worksheet

Completed diagnostic worksheet showing what the full diagnostic picture looks like after all steps have been worked through. Your worksheet will reflect your environment's specific data — the steps, tool sequence, and REST API calls to assemble it are documented in the Audit Trail section below.

GL-07 — GL-07 Diagnostic Report 
════════════════════════════════════════════════════════════
  ORACLE FUSION — GL PERIOD CLOSE READINESS DIAGNOSTIC
════════════════════════════════════════════════════════════
  Period             : FEB-2026
  Ledger             : Fusion US Primary Ledger
  Case Number        : FC-GL-2026-0204
  Report Date        : 25-FEB-2026 17:30:22
════════════════════════════════════════════════════════════

[ STEP 1 — MANAGE ACCOUNTING PERIODS ]        STATUS: ✓ OPEN
────────────────────────────────────────────────────────────
  FEB-2026 — Open in all subledgers ✓

[ STEP 2 — CLOSE MONITOR STATUS ]
────────────────────────────────────────────────────────────
  AP Subledger       : Create Accounting — Completed with errors ✗
  AR Subledger       : Complete ✓
  FA Subledger       : Complete ✓
  INV Subledger      : Complete ✓
  Post Journals      : Pending — blocked by AP errors ⚠

[ STEP 3 — BIP: CREATE ACCOUNTING EXECUTION REPORT ]
────────────────────────────────────────────────────────────
  AP Errors          : 3 invoices — INVALID_ACCOUNT_CODE_COMBINATION ✗
  Invoice IDs        : 1998210, 1998445, 1998881
  Account            : 01.500.7810.0000 — disabled 01-JAN-2026

[ STEP 4 — UNPOSTED JOURNALS ]                STATUS: ✗ FAIL
────────────────────────────────────────────────────────────
  Unposted Journals  : 4 manual journal batches — $284,100 ✗
  Awaiting Approval  : Controller approval required

════════════════════════════════════════════════════════════
  CLOSE READINESS SUMMARY
════════════════════════════════════════════════════════════
  PERIOD CANNOT CLOSE — 2 blocking conditions
  1. Resolve AP Create Accounting errors — re-enable account or remap invoices
  2. Post 4 manual journal batches
════════════════════════════════════════════════════════════
How the Diagnostic Works

The Four-Layer Architecture in GL-07

1
Diagnostic Steps
Fusion GL close diagnostic using the Close Monitor status screen, OTBI GL Journal Entries subject area for unposted journals, ESS job history for Create Accounting across all subledgers, BIP Create Accounting Execution Report for error detail, and Manage Accounting Periods for period status.
2
Backup Created
Fusion Cloud does not permit direct database modification. OTBI and BIP report outputs are exported before any corrective actions. FBDI exports are used when bulk journal data needs to be documented.
3
Guided Data Fix
All close blockers resolved through Fusion UI or ESS resubmission — Manage Chart of Accounts for account corrections, Create Accounting ESS resubmission, Manage Journals for posting. GL-07 provides exact ESS program names and navigation paths.
4
KB Article Generated
Complete KB article generated — period, ESS job IDs, Close Monitor status per subledger, error types, correction path, close completion confirmation. Upload directly to your knowledge base.
Audit Trail

Documentation Before Every Action — GL-07

Fusion Cloud does not permit direct database access. Every corrective action goes through a supported Oracle interface. Before any action is taken, the current state is exported and documented.

Pre-Action Documentation — GL-07

Fusion Close Monitor — step status export before action
ESS: Create Accounting — job output log downloaded per subledger
BIP: Create Accounting Execution Report — error detail saved
OTBI: GL Journal Entries — unposted journal export

Exported before any UI action, ESS resubmission, or FBDI reimport. Provides a point-in-time record of the error state for the KB article and SR documentation if needed.

Pre-Action Verification

Fusion tenant accessibleConfirmed ✓
Close Monitor status retrievedExported ✓
ESS Create Accounting job history downloadedSaved ✓
BIP Execution Report run and savedSaved ✓
No Create Accounting job currently runningConfirmed ✓

Audit Trail Record

CASE_NUMBER<consultant case#>
DIAGNOSTIC_TOOL<OTBI / REST API / BIP / ESS>
ERROR_SNAPSHOT<exported before action>
ACTION_TAKEN<UI path / ESS program / FBDI>
RESULT_VERIFIEDYES ✓

No Direct DB Access — By Design

Oracle Fusion Cloud is a SaaS environment. There is no consultant-accessible Oracle schema, no SQL*Plus connection, and no CONS_BACKUP tablespace. All diagnostic and corrective activity goes through OTBI, REST APIs, BIP reports, ESS programs, and the Fusion UI — the same supported tools Oracle Support uses.

REST API Reference — Endpoints Used in This Diagnostic

All API calls use OAuth 2.0 authentication. The base URL is your Fusion Cloud instance URL. Replace {instanceName} with your tenant name. Obtain the OAuth token via the /oauth/token endpoint using client credentials.

GETJournal Entry Batches (Unposted)
/fscmRestApi/resources/11.13.18.05/journalBatches
Key Query Parameters
q filter — Status=Unposted;PeriodName=FEB-26;LedgerId={ledgerId}
limit integer — default 25
fields BatchName,BatchId,Status,PeriodName,TotalEnteredCr,TotalEnteredDr,CreatedBy
Response Fields Read
BatchId, BatchName — journal batch identifier
Status — Unposted, Posted, Error
PeriodName — the accounting period
TotalEnteredDr, TotalEnteredCr — batch debit/credit totals for balance check
CreatedBy, CreationDate — who created the batch and when
GETAccounting Period Status
/fscmRestApi/resources/11.13.18.05/accountingPeriods
Key Query Parameters
q LedgerId={ledgerId};PeriodName=FEB-26
fields PeriodName,Status,LedgerId — minimal field set for period status check
Response Fields Read
Status — Open, Closed, Never Opened, Future Enterable, Permanently Closed
PeriodName, LedgerId, LedgerName
Layer 4 Output

Auto-Generated Knowledge Base Article

This article is produced automatically at the end of every GL-07 execution — written from actual run output. No manual documentation required.

KB-FC-GL-0204-001 · Script: GL-07
Fusion GL Period FEB-2026 Close — AP Create Accounting Errors and 4 Unposted Manual Journals
Module: General Ledger
Platform: Oracle Fusion Cloud
Status: RESOLVED
Symptom
Fusion GL FEB-2026 cannot close. Close Monitor shows AP Create Accounting completed with errors — 3 invoices with INVALID_ACCOUNT_CODE_COMBINATION. 4 manual journal batches unposted totalling $284,100. Post Journals step blocked.
Root Cause
AP invoices 1998210, 1998445, 1998881 reference account 01.500.7810.0000 disabled in Fusion COA on 01-JAN-2026. Identified via BIP Create Accounting Execution Report. Manual journals: 4 adjustment batches entered by regional accountants awaiting Controller approval — approval SLA exceeded.
Tables Affected
Fusion GL Close Monitor — AP Create Accounting step status: Completed with errors
BIP Create Accounting Execution Report — Journal Entry line: account 01.500.7810.0000, error: INVALID_ACCOUNT_CODE_COMBINATION
OTBI GL Journal Entries — journalStatus: Unposted (4 batches)
Fix Applied
Account 01.500.7810.0000 re-enabled in Fusion Chart of Accounts by GL Controller. AP Create Accounting resubmitted — 3 invoices accounted. Controller posted 4 manual journal batches. Close Monitor all steps Complete. FEB-2026 period closed.
Prevention
Fusion COA account disablement process updated to require BIP impact report before disablement. Manual journal posting SLA set to 48 hours with escalation to Controller. GL-07 should run at period day-minus-3.
Tags
Fusion GLPeriod CloseCreate AccountingClose MonitorINVALID_ACCOUNT_CODE_COMBINATIONESS JobOracle Fusion Cloud
Common Issues

What This Script Finds

Critical

Create Accounting Completed with Errors

One or more subledger Create Accounting ESS jobs show errors. BIP Execution Report identifies the specific account, transaction, and error type. GL-07 provides the navigation path to correct the source account or transaction.

Critical

Unposted Manual Journals

Manual adjustment batches awaiting approval are blocking the Post Journals close step. GL-07 identifies each batch from OTBI with the approver and escalation path.

Warning

Close Monitor Step Stuck

A Close Monitor step shows Pending or In Progress for more than 2 hours. GL-07 identifies the underlying ESS job and determines whether it is actively running or has stalled.

Warning

Revaluation or Translation Not Run

FX accounts not revalued, or consolidation translation not run, before attempting GL close. GL-07 identifies the missing step from OTBI and provides the ESS program parameters.

Data Layer

Tables Examined

Data SourceTypePurpose
Close MonitorFusion UIStep-by-step close status per subledger and GL
ESS Job HistoryESSCreate Accounting and Post Journals job status
BIP: Create Accounting Execution ReportBIPError-level detail for accounting failures
OTBI: GL Journal EntriesOTBIUnposted journal count and amount
Manage Accounting PeriodsFusion UIPeriod status for GL and all subledgers
Decision Framework

How Every Resolution Decision Is Made

Every condition identified by the diagnostic maps to exactly one resolution path. In Fusion Cloud, all paths go through supported Oracle interfaces — UI, REST API, FBDI, or ESS. Direct database access does not exist in this environment.

1
First Option — Always
Can the Fusion UI resolve this?

Oracle's own Fusion screens, Scheduled Processes (ESS), and workflow tools are always the first resolution path. Manage Invoices, Manage Suppliers, Manage Accounting Periods, BPM Worklist, Scheduled Processes — the diagnostic identifies the exact navigation path and screen sequence for every condition that can be resolved this way. No third-party tools, no API calls, no risk beyond what Oracle's own UI carries.

✓ Functional First
2
When the UI Path Is Insufficient
Can a REST API PATCH or FBDI reimport resolve this?

For bulk corrections or conditions not surfaced in the standard UI, Oracle Fusion's public REST APIs and FBDI import templates are the supported programmatic path. A REST API PATCH call to correct an invoice distribution account, an FBDI resubmission with corrected records after an import failure, or a Mass Update via the REST API — these are supported, documented, and reversible through normal Oracle mechanisms. The current state is exported before any API call is made.

→The API endpoint is an Oracle-published, versioned REST resource
→The FBDI template matches the current Fusion release version
→The pre-action state is exported (OTBI report / GET response) before the PATCH or import runs
→The result is verified via a follow-up GET or OTBI query before the case is closed
⚡ API / FBDI
3
Hard Stops — No Exceptions
Does this require Oracle Support?

Certain conditions in Fusion Cloud cannot be resolved through any customer-accessible interface. The diagnostic flags these and generates the Service Request documentation:

✗ESS job infrastructure failures — job status Error (not Completed with Warnings) indicating an engine-level issue not caused by data
✗Subledger accounting engine errors — Create Accounting failures where the error is in the Oracle accounting engine, not in the source transaction data
✗Recurring failures after correct setup — a condition that returns after a confirmed correct resolution indicates a code defect, submitted as an SR with a reproducible test case
✗Fusion data corruption — records in an inconsistent internal state not reachable through any published API or UI action
⚠ Oracle Support
4
For All Actions Taken
Export → Act → Verify → Document

Before any UI action, ESS resubmission, REST API call, or FBDI reimport — the current error state is exported via OTBI report, BIP report output, or REST API GET response. After the action, a verification step confirms the expected outcome. The complete sequence — tool used, pre-action state, action taken, result verified — is written into the KB article as the primary record of what was done and why.

📋 Documented
Condition Identified Resolution Path Notes
Create Accounting ESS errors — invalid account in Fusion COA Functional First Correct the account via Manage Chart of Accounts, then resubmit Create Accounting ESS for the subledger. GL-07 identifies the account and the BIP Execution Report reference.
Unposted manual journals in Fusion GL Functional First Post via Manage Journals > Actions > Post, or submit the Post Journals ESS program. GL-07 identifies unposted batches from OTBI GL Journal Entries with approver and amount.
Close Monitor step stuck in Pending Functional First Identify the blocking ESS job from the Close Monitor step detail. Resubmit or cancel via Manage Scheduled Processes. GL-07 identifies the job ID and the prerequisite step.
Subledger period not closed before GL close Functional First Close the subledger period via Manage Accounting Periods for the specific subledger application. GL-07 identifies which subledgers have open periods blocking the GL close.
Revaluation not run for Fusion FX accounts Functional First Submit the Revalue Balances ESS program for the Fusion revaluation definition and period. GL-07 identifies FX accounts from OTBI not yet revalued.
Translation not run — consolidation ledger Functional First Submit the Translate Balances ESS program. GL-07 identifies translation definitions not run for the current period from OTBI.
Manual journal approval pending Functional First Escalate via Fusion Worklist or configure a delegate approver. GL-07 identifies pending journal batches with approver and submission age from OTBI.
ESS Create Accounting job status Error — full failure Oracle Support SR Full ESS Create Accounting failures (status Error) may indicate an accounting engine or profile configuration issue. GL-07 documents the job ID and error for the Oracle Support SR.
Safeguards

Nothing Acts Without a Documented State

Fusion Cloud's SaaS architecture eliminates direct database access — which means every action is a supported Oracle API call, UI operation, or ESS submission. Before any action runs, the current error state is captured. After any action, the result is verified.

Pre-Action Documentation — All Completed First
✓
Fusion Close Monitor — step status export before action
Exported before any corrective action is taken
✓
ESS: Create Accounting — job output log downloaded per subledger
Exported before any corrective action is taken
✓
BIP: Create Accounting Execution Report — error detail saved
Exported before any corrective action is taken
✓
OTBI: GL Journal Entries — unposted journal export
Exported before any corrective action is taken
✓
Post-action verification
Follow-up OTBI query or REST GET confirms the expected state before the case is closed
Fusion Audit Trail — What Replaces CONS_BACKUP

In EBS R12, a CONS_BACKUP table provides the rollback point. In Fusion Cloud, the equivalent audit trail is built from three sources that together give a complete before-and-after record:

BEFORE STATE
OTBI report export or REST API GET response saved as the pre-action snapshot
ACTION RECORD
Fusion audit trail (Setup and Maintenance > Audit Reports) captures every UI and API change with user, timestamp, old value, and new value
AFTER STATE
Post-action OTBI query or REST GET confirms the fix — this output becomes the KB article verification artifact
GL-07 — Fusion Diagnostic Framework 
════════════════════════════════════════════════════════════
  ORACLE FUSION — GL PERIOD CLOSE DIAGNOSTIC
════════════════════════════════════════════════════════════
  Platform           : Oracle Fusion Cloud (no direct DB access)
  Tools Available    : Close Monitor, OTBI, ESS History, BIP Reports, Manage Periods
  Pre-Action Export  : Close Monitor status and OTBI journals exported before action
────────────────────────────────────────────────────────────
  Step 1 — Close Monitor: AP Create Accounting — Completed with errors identified ✓
  Step 2 — BIP Report   : Create Accounting Execution Report — 3 account errors ✓
  Step 3 — OTBI Journals: 4 unposted batches identified — approver and amount ✓
────────────────────────────────────────────────────────────
  DIAGNOSTIC COMPLETE — 2 blocking conditions identified
════════════════════════════════════════════════════════════
  Documentation      : KB article generated from Close Monitor and BIP output
  Fusion Audit Trail : COA and journal changes logged in Fusion audit trail
  SR Reference       : N/A — resolved via Fusion COA correction
════════════════════════════════════════════════════════════
Knowledge Base

Every Execution Produces a Record

The knowledge base article is generated automatically from the script's execution output. No manual documentation required. It becomes the institutional record — for the team, for auditors, and for every future engagement in the same environment.

Zero Manual Effort
Every field — environment, tables, before/after values, backup reference, root cause, prevention — is generated from actual execution output. Nothing is written by hand.
Patterns Surface Over Time
The first engagement produces findings. The third produces patterns. Recurring conditions that are invisible as individual incidents become obvious as knowledge base trends.
Survives Staff Turnover
The knowledge base is an institutional record of the Oracle environment. A new manager, a new DBA, or an external auditor can read exactly what happened, what was done, and what prevents recurrence.
KB-FC-GL-0204-001
Fusion GL Period FEB-2026 Close — AP Create Accounting Errors and 4 Unposted Manual Journals
Oracle Fusion Cloud · General Ledger
● RESOLVED
Symptom
Fusion GL FEB-2026 cannot close. Close Monitor shows AP Create Accounting completed with errors — 3 invoices with INVALID_ACCOUNT_CODE_COMBINATION. 4 manual journal batches unposted totalling $284,100. Post Journals step blocked.
Root Cause
AP invoices 1998210, 1998445, 1998881 reference account 01.500.7810.0000 disabled in Fusion COA on 01-JAN-2026. Identified via BIP Create Accounting Execution Report. Manual journals: 4 adjustment batches entered by regional accountants awaiting Controller approval — approval SLA exceeded.
Tables
Fusion GL Close Monitor — AP Create Accounting step status: Completed with errors
BIP Create Accounting Execution Report — Journal Entry line: account 01.500.7810.0000, error: INVALID_ACCOUNT_CODE_COMBINATION
OTBI GL Journal Entries — journalStatus: Unposted (4 batches)
Fix Applied
Account 01.500.7810.0000 re-enabled in Fusion Chart of Accounts by GL Controller. AP Create Accounting resubmitted — 3 invoices accounted. Controller posted 4 manual journal batches. Close Monitor all steps Complete. FEB-2026 period closed.
Prevention
Fusion COA account disablement process updated to require BIP impact report before disablement. Manual journal posting SLA set to 48 hours with escalation to Controller. GL-07 should run at period day-minus-3.
Tags
Fusion GLPeriod CloseCreate AccountingClose MonitorINVALID_ACCOUNT_CODE_COMBINATIONESS JobOracle Fusion Cloud
Oracle References

Oracle Documentation References

References the Oracle public documentation for this diagnostic area. These links open directly on docs.oracle.com.

Documentation PageTitleScenario
Period ClosePeriod Close — Close MonitorFusion Close Monitor for all subledger and GL period status
Using General Ledger.PdfUsing General Ledger — Fusion 25DFusion journal import, posting, and close sequence
Oracle Fusion General LedgerUsing Analytics and Reports for FinancialsClearing account balance verification reports for Fusion close
Continue Your Diagnosis

Related Diagnostic Scripts

AP-07

AP Invoice Validation (Fusion)

View the full diagnostic for this related script.

 AR-08

AR Period Close (Fusion)

View the full diagnostic for this related script.

 GL-08

GL Journal Import (Fusion)

View the full diagnostic for this related script.

Engage William A. Green

Ready to Resolve This in Your Environment?

GL-07 is one of 65 diagnostic scripts covering every major Oracle EBS and Fusion module. William A. Green Consulting runs the script in your environment, applies guided data fixes, and builds the knowledge base that prevents the same issues from recurring.

Schedule a Discovery Call → ← View All 65 Scripts

See this script run autonomously — Oracle AI Platform →