Script Library › Accounts Receivable › AR-08
AR-08 Oracle Fusion Cloud Accounts Receivable Guided Actions

AR Period Close Readiness (Oracle Fusion)

Fusion AR close readiness via OTBI, REST API, and ESS job history — unposted receipts, unaccounted transactions, revenue recognition completeness, and Transfer to GL status.

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

Why This Fails — and What It Costs

Oracle Fusion Cloud AR period close diagnostics present a different challenge from EBS R12 — not because the blocking conditions are fundamentally different, but because the tools available to identify them are different. In EBS R12, a consultant can query the database directly for unaccounted transactions, pending adjustments, and revenue recognition status. In Fusion, the same analysis goes through OTBI reports against the Receivables Transactions and Receivables Accounting subject areas, ESS job history for Create Accounting and Transfer to General Ledger, and the Fusion AR Manage Accounting Periods screen.

The Fusion AR period close sequence has a specific order that must be followed: all transactions must be accounted (ESS Create Accounting must complete without errors), the Transfer to General Ledger ESS job must complete, and revenue recognition schedules must be current. If the Create Accounting ESS job completes with errors, the error details appear in the job output log and the Subledger Accounting Create Accounting Execution Report — a BIP report that shows each accounting error with the transaction reference, the error type, and the correction path.

The Transfer to General Ledger step in Fusion introduces a synchronization consideration that does not exist in EBS R12. In Fusion, the Transfer to GL process transfers subledger accounting journals to the General Ledger module. If the GL period is already closed when Transfer to GL runs, the journals are automatically routed to the next open GL period — but the AR period can still be closed to the current period. This differs from EBS R12 behavior where a closed GL period would block the AR close entirely. AR-08 clarifies this Fusion-specific behavior and identifies whether the GL period routing is appropriate.

AR-08 provides a structured Fusion AR period-close diagnostic using OTBI analysis of unaccounted transactions, ESS job history review for Create Accounting and Transfer to GL, the Fusion Manage Accounting Periods screen for period status, revenue recognition completeness via OTBI, and BIP Create Accounting Execution Report interpretation. It produces a close readiness checklist with the ESS program names and submission parameters for each blocking condition.

Diagnostic Coverage

What This Script Diagnoses

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

Period Status in Fusion
Receivables period status via REST. Subledger accounting period via OTBI. Ledger period status. Close status across all legal entities.
Unaccounted Transactions
OTBI: Transactions with accounting status INCOMPLETE or NONE. ESS job history for Create Accounting — AR module. Error count and type from Create Accounting log.
Transfer to GL Status
ESS job history for Transfer to General Ledger — AR. Unjournal entries not yet transferred. Transfer batch status and error records via OTBI.
Revenue Recognition
OTBI: Deferred revenue balances by period. Revenue recognition schedule completion. Contingency release events pending.
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.

AR-08 — AR-08 Diagnostic Report 
════════════════════════════════════════════════════════════
  ORACLE FUSION — AR PERIOD CLOSE READINESS DIAGNOSTIC
════════════════════════════════════════════════════════════
  Period             : FEB-2026
  Business Unit      : US Primary BU
  Case Number        : FC-AR-2026-0168
  Report Date        : 25-FEB-2026 14:20:30
════════════════════════════════════════════════════════════

[ STEP 1 — FUSION PERIOD STATUS ]            STATUS: ✓ PASS
────────────────────────────────────────────────────────────
  AR Period          : FEB-2026 — Open ✓
  GL Period          : FEB-2026 — Open ✓

[ STEP 2 — CREATE ACCOUNTING ESS ]           STATUS: ✗ ERRORS
────────────────────────────────────────────────────────────
  Last ESS Job ID    : ESS-2026-04820
  Job Status         : Completed with errors
  Errors             : 3 transactions — INVALID_ACCOUNT_CODE_COMBINATION
  Transaction IDs    : 1998210, 1998445, 1998881
  BIP Report         : Create Accounting Execution Report — see Error Details section

[ STEP 3 — TRANSFER TO GL ]                  STATUS: ⚠ BLOCKED
────────────────────────────────────────────────────────────
  ⚠ Transfer to GL blocked — Create Accounting must complete first

[ STEP 4 — REVENUE RECOGNITION ]             STATUS: ✓ PASS
────────────────────────────────────────────────────────────
  All FEB-2026 revenue schedules recognized ✓

════════════════════════════════════════════════════════════
  CLOSE READINESS SUMMARY
════════════════════════════════════════════════════════════
  PERIOD CANNOT CLOSE — 1 blocking condition
  1. Resolve 3 INVALID_ACCOUNT_CODE_COMBINATION errors in Create Accounting
  2. Resubmit Create Accounting ESS job
  3. Run Transfer to GL
  4. Close FEB-2026 via Manage Accounting Periods
════════════════════════════════════════════════════════════
How the Diagnostic Works

The Four-Layer Architecture in AR-08

1
Diagnostic Steps
Fusion AR period-close diagnostic using OTBI Receivables Transactions and Accounting subject areas, ESS job history for Create Accounting and Transfer to GL, Manage Accounting Periods status, revenue recognition completeness via OTBI, and BIP Create Accounting Execution Report analysis.
2
Backup Created
Fusion Cloud does not permit direct database modification. OTBI report output and BIP report results are exported before any corrective actions are taken.
3
Guided Data Fix
All close blockers resolved through Fusion UI or ESS program resubmission — Manage Chart of Accounts for account corrections, ESS Create Accounting resubmission, and Transfer to GL. AR-08 provides exact ESS program names and parameters.
4
KB Article Generated
Complete KB article generated — period, ESS job IDs, error types, correction path, close completion confirmation. Upload directly to your knowledge base.
Audit Trail

Documentation Before Every Action — AR-08

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 — AR-08

OTBI: Receivables Transactions — unaccounted export before action
ESS: Create Accounting — job output log downloaded
BIP: Create Accounting Execution Report — error detail saved
Manage Accounting Periods — period status screenshot

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 ✓
OTBI unaccounted count retrievedExported ✓
Create Accounting ESS job history retrievedDownloaded ✓
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.

GETUnaccounted Receivables Transactions
/fscmRestApi/resources/11.13.18.05/receivablesInvoices
Key Query Parameters
q filter — AccountingStatus=NOT ACCOUNTED;GlDate>={period_start};GlDate<={period_end}
limit integer — set to 500 for period-close review
fields TransactionId,TransactionNumber,TransactionDate,GlDate,Amount,AccountingStatus
Response Fields Read
TransactionId, TransactionNumber
AccountingStatus — NOT ACCOUNTED for unaccounted transactions
GlDate — the accounting date that determines period assignment
Amount — transaction amount for reconciliation
GETAccounting Period Status
/fscmRestApi/resources/11.13.18.05/accountingPeriods
Key Query Parameters
q filter — e.g. LedgerId={ledgerId};PeriodName=FEB-26 to check a specific period
fields PeriodName,Status,LedgerId,LedgerName — restrict to period and status fields
Response Fields Read
PeriodName — e.g. FEB-26
Status — Open, Closed, Never Opened, Future Enterable, Permanently Closed
LedgerId, LedgerName — the GL ledger this period belongs to
Layer 4 Output

Auto-Generated Knowledge Base Article

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

KB-FC-AR-0168-001 · Script: AR-08
Fusion AR Period FEB-2026 Close — Create Accounting Errors Blocking Transfer to GL
Module: Accounts Receivable
Platform: Oracle Fusion Cloud
Status: RESOLVED
Symptom
Fusion AR FEB-2026 period cannot be closed. Create Accounting ESS job ESS-2026-04820 completed with errors. 3 transactions failing with INVALID_ACCOUNT_CODE_COMBINATION. Transfer to GL blocked pending Create Accounting completion.
Root Cause
Three AR transactions reference an account code combination that was inactivated in Fusion Chart of Accounts on 01-FEB-2026. The account was used in the default AutoAccounting rules for the transaction type — not caught at entry time because the account was active when the transactions were entered in late January.
Tables Affected
Fusion AR Transactions — transactionId: 1998210, 1998445, 1998881 (Create Accounting error: INVALID_ACCOUNT_CODE_COMBINATION)
ESS Job ID: ESS-2026-04820, status: Completed with errors
Fix Applied
Account 01.500.7810.0000 re-enabled in Fusion Chart of Accounts by GL Controller. Create Accounting resubmitted — all 3 transactions accounted. Transfer to GL completed. FEB-2026 AR period closed 25-FEB-2026 15:45.
Prevention
Before disabling accounts in Fusion Chart of Accounts, run OTBI: AR Transaction Distributions with account filter to identify open AR transactions referencing the account. AR-08 period-close check should run at period day-minus-3.
Tags
Fusion ARPeriod CloseCreate AccountingTransfer to GLINVALID_ACCOUNT_CODE_COMBINATIONESS JobOracle Fusion Cloud
What It Finds

Most Common Issues Detected by AR-08

Critical

Create Accounting Errors in Fusion AR

Create Accounting ESS job completed with errors for AR module. AR-08 navigates to ESS log, identifies error type, and provides the Review Accounting Exceptions path.

Critical

Transfer to GL Not Complete

AR journals not yet transferred to GL. AR-08 identifies the Transfer to GL ESS job status and outstanding transfer amounts by accounting class.

Warning

Revenue Recognition Not Run

Deferred revenue schedules unprocessed for the current period. AR-08 identifies the ESS job for Revenue Recognition and the outstanding amounts.

Data Sources

Tables & Views Examined

Table / ViewSchemaPurpose in Diagnostic
OTBI: Receivables Transactions OTBI Accounting status and unaccounted items
ESS: Create Accounting ESS Accounting job run history
ESS: Transfer to GL ESS GL transfer job history
OTBI: Revenue Recognition OTBI Deferred revenue and recognition schedules
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 combination Functional First Correct the account via Manage Chart of Accounts, then resubmit Create Accounting ESS for the AR application. AR-08 identifies the specific account from the BIP Execution Report.
Transfer to GL not complete Functional First Submit the Transfer to General Ledger ESS program. AR-08 provides the ESS program name and required parameters for the AR application and period.
Revenue recognition incomplete Functional First Submit the Generate Revenue ESS program for the period. AR-08 identifies transactions with incomplete schedules from the OTBI Revenue Recognition subject area.
Unaccounted receipts Functional First Submit Create Accounting for the Receivables application. AR-08 identifies the unaccounted receipt count from OTBI Receivables Accounting subject area.
Period status mismatch — AR open, GL closed Functional First AR-08 explains the Fusion behavior: Transfer to GL routes journals to the next open GL period automatically. Confirms whether this routing is intentional for the current close.
Pending adjustments in Fusion approval workflow Functional First Escalate via Fusion Worklist or configure a delegate approver via Manage Receivables System Options. AR-08 identifies pending adjustments from OTBI with approver and age.
Incomplete transaction batches Functional First Close open batches via Billing > Manage Transaction Batches. AR-08 identifies batches in incomplete status from OTBI.
Create Accounting ESS job status Error — full failure Oracle Support SR Full Create Accounting failures (status Error) may indicate an accounting engine or configuration issue. AR-08 documents the job ID and error detail 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
✓
OTBI: Receivables Transactions — unaccounted export before action
Exported before any corrective action is taken
✓
ESS: Create Accounting — job output log downloaded
Exported before any corrective action is taken
✓
BIP: Create Accounting Execution Report — error detail saved
Exported before any corrective action is taken
✓
Manage Accounting Periods — period status screenshot
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
AR-08 — Fusion Diagnostic Framework 
════════════════════════════════════════════════════════════
  ORACLE FUSION — AR PERIOD CLOSE DIAGNOSTIC
════════════════════════════════════════════════════════════
  Platform           : Oracle Fusion Cloud (no direct DB access)
  Tools Available    : OTBI, ESS History, BIP Execution Report, Manage Periods
  Pre-Action Export  : OTBI unaccounted report saved before any action
────────────────────────────────────────────────────────────
  Step 1 — OTBI      : Receivables Transactions — 3 unaccounted identified ✓
  Step 2 — ESS       : Create Accounting job history retrieved — errors logged ✓
  Step 3 — BIP       : Create Accounting Execution Report — 3 errors categorized ✓
────────────────────────────────────────────────────────────
  DIAGNOSTIC COMPLETE — 1 blocking condition identified
════════════════════════════════════════════════════════════
  Documentation      : KB article generated from ESS and BIP output
  Fusion Audit Trail : COA and period 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-AR-0168-001
Fusion AR Period FEB-2026 Close — Create Accounting Errors Blocking Transfer to GL
Oracle Fusion Cloud · Accounts Receivable
● RESOLVED
Symptom
Fusion AR FEB-2026 period cannot be closed. Create Accounting ESS job ESS-2026-04820 completed with errors. 3 transactions failing with INVALID_ACCOUNT_CODE_COMBINATION. Transfer to GL blocked pending Create Accounting completion.
Root Cause
Three AR transactions reference an account code combination that was inactivated in Fusion Chart of Accounts on 01-FEB-2026. The account was used in the default AutoAccounting rules for the transaction type — not caught at entry time because the account was active when the transactions were entered in late January.
Tables
Fusion AR Transactions — transactionId: 1998210, 1998445, 1998881 (Create Accounting error: INVALID_ACCOUNT_CODE_COMBINATION)
ESS Job ID: ESS-2026-04820, status: Completed with errors
Fix Applied
Account 01.500.7810.0000 re-enabled in Fusion Chart of Accounts by GL Controller. Create Accounting resubmitted — all 3 transactions accounted. Transfer to GL completed. FEB-2026 AR period closed 25-FEB-2026 15:45.
Prevention
Before disabling accounts in Fusion Chart of Accounts, run OTBI: AR Transaction Distributions with account filter to identify open AR transactions referencing the account. AR-08 period-close check should run at period day-minus-3.
Tags
Fusion ARPeriod CloseCreate AccountingTransfer to GLINVALID_ACCOUNT_CODE_COMBINATIONESS JobOracle Fusion Cloud
Oracle References

Oracle Documentation References

Documentation PageTitleScenario
Period ClosePeriod Close — Close MonitorFusion AR subledger status in Close Monitor
Manage Accounts Receivable BalancesManage Accounts Receivable BalancesTransfer to GL reconciliation for Fusion AR close
Continue Your Diagnosis

Related Diagnostic Scripts

AR-07

AutoInvoice Diagnostic (Fusion)

View the full diagnostic for this related script.

 GL-07

GL Period Close (Fusion)

View the full diagnostic for this related script.

 AP-07

AP Invoice Validation (Fusion)

View the full diagnostic for this related script.

Engage William A. Green

Ready to Resolve This in Your Environment?

AR-08 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 →