GL-05: Revaluation Diagnostic

Foreign currency revaluation in Oracle EBS GL is a month-end process that adjusts the functional currency balance of monetary accounts denominated in foreign currencies to reflect the current exchange rate. When revaluation is not run, or runs incorrectly, the balance sheet overstates or understates assets and liabilities by the difference between the historical exchange rate and the current rate — a financial reporting error that auditors will identify during year-end review if not caught at month-end.

The most common revaluation failure is a missing or incorrect exchange rate in GL_DAILY_RATES for the revaluation date. When the Revalue Balances concurrent program runs and cannot find a rate for the currency and rate type combination on the period end date, it skips the revaluation for that currency without generating an error that is immediately visible to the accounting team. The revaluation report shows the currency with a zero unrealized gain/loss — which looks correct until the team realizes no adjustment was actually made because the rate was missing, not because the balance was zero.

Revaluation reversal configuration is the second source of issues. Oracle GL supports automatic reversal of revaluation journal entries in the following period — the unrealized gain or loss from FEB-2026 revaluation is automatically reversed in MAR-2026 when the next revaluation runs, producing a clean net position. When this reversal configuration is incorrect — for example, when the reversal period is set to the current period rather than the next period, or when the reversal has been disabled — revaluation entries accumulate without reversing, and the unrealized gain/loss balance grows period over period rather than reflecting only the current period's rate movement.

GL-05 runs a complete revaluation diagnostic — revaluation set configuration analysis per ledger, exchange rate existence in GL_DAILY_RATES for the revaluation date and rate type, foreign currency account balance identification by revaluation set, revaluation journal existence and amount for the current period, reversal configuration status, and comparison of current-period revaluation against the expected amount calculated from the period-end rates.

Revaluation Set Config

Revaluation set accounts per ledger, rate type, and reversal period configuration. Completeness check — all FX monetary accounts included in at least one revaluation set.

Exchange Rate Existence

GL_DAILY_RATES validation for each currency and rate type in the revaluation set on the period-end date. Missing rate identification with expected rate source.

FX Account Balances

Foreign currency account balances by revaluation set. Current period balances compared to prior period to identify new accounts requiring revaluation.

Revaluation Journal Status

Existence, amount, and posting status of revaluation journals for the current period. Currency-level revaluation completeness — identifies which currencies were processed and which were skipped.

Reversal Configuration

Reversal period settings per revaluation set. Prior period revaluation reversal confirmation — ensures no prior-period revaluation entries remain unreversed in the current period.

════════════════════════════════════════════════════════════
  ORACLE EBS R12 — FOREIGN CURRENCY REVALUATION DIAGNOSTIC
════════════════════════════════════════════════════════════
  Ledger             : US Primary Ledger
  Period             : FEB-2026
  Revaluation Set    : US-MONETARY-REVAL
  Case Number        : GL-525840
  Report Date        : 25-FEB-2026 14:20:11
════════════════════════════════════════════════════════════

[ SECTION 1 — REVALUATION SET CONFIG ]        STATUS: ✓ PASS
────────────────────────────────────────────────────────────
  Accounts in Set    : 4 foreign currency monetary accounts
  Rate Type          : Corporate
  Reversal Period    : Next Period (MAR-2026) ✓

[ SECTION 2 — EXCHANGE RATES ]                STATUS: ✗ FAIL
────────────────────────────────────────────────────────────
  EUR Corporate Rate : 28-FEB-2026 — 1.0842 ✓
  GBP Corporate Rate : 28-FEB-2026 — 1.2641 ✓
  CAD Corporate Rate : 28-FEB-2026 — MISSING ✗
  MXN Corporate Rate : 28-FEB-2026 — 0.0512 ✓
  ✗ FAIL: CAD Corporate rate missing for 28-FEB-2026
  CAD Balance        : CAD 842,100 (functional USD equiv: ~$610,000)

[ SECTION 3 — REVALUATION JOURNALS ]          STATUS: ⚠ WARNING
────────────────────────────────────────────────────────────
  ⚠ EUR, GBP, MXN revalued — CAD skipped due to missing rate
  EUR Unrealized G/L : $12,840 gain
  GBP Unrealized G/L : -$4,210 loss
  CAD Unrealized G/L : NOT CALCULATED ✗

════════════════════════════════════════════════════════════
  DIAGNOSTIC SUMMARY
════════════════════════════════════════════════════════════
  CAD revaluation incomplete — rate missing in GL_DAILY_RATES
  FIX: Load CAD Corporate rate for 28-FEB-2026, rerun revaluation
════════════════════════════════════════════════════════════

KB-GL-525840-001 · Script: GL-05

Revaluation Incomplete — CAD Corporate Exchange Rate Missing for Period-End Date

Module: General Ledger
Platform: EBS R12.2.10
Status: RESOLVED

Symptom

FEB-2026 revaluation run completed for EUR, GBP, and MXN but skipped CAD. CAD Corporate rate missing in GL_DAILY_RATES for 28-FEB-2026. CAD monetary balance of CAD 842,100 (approx $610,000 USD equivalent) not revalued. Financial statements understate FX adjustment.

Root Cause

Corporate rate for CAD was not loaded for 28-FEB-2026. Rate feed from the Treasury system failed on 27-FEB-2026 — the feed provider had a connectivity issue. EUR, GBP, and MXN rates from the prior day's feed were available; CAD was not.

Tables Affected

GL_DAILY_RATES — FROM_CURRENCY = CAD, RATE_TYPE = Corporate, CONVERSION_DATE = 28-FEB-2026 (missing record)
GL_JE_HEADERS — JE_CATEGORY = Revaluation (FEB-2026 — CAD not present)

Fix Applied

CAD Corporate rate 1.3618 loaded manually for 28-FEB-2026 with backup. Revalue Balances resubmitted for US-MONETARY-REVAL set. CAD unrealized loss of $8,420 recognized. Reversal entry generated for MAR-2026.

Prevention

Rate feed monitoring alert added for CAD, EUR, GBP, MXN — notify Treasury immediately if rates are not loaded by 17:00 on period-end date. GL-05 should run after revaluation to confirm all currency accounts have been processed.

Exchange Rate Not Loaded for Period End

Treasury system rate feed failure or manual omission leaves one or more currencies without a period-end rate. Revaluation silently skips the currency. GL-05 identifies the missing rate and the correct value to load.

Not Run

Revaluation Not Submitted

Revalue Balances program was not submitted for the period. FX balance sheet accounts carry the prior-month rate, overstating or understating asset and liability balances by the period rate movement.

Reversal

Prior Period Entry Not Reversed

Revaluation reversal configuration incorrect — prior period unrealized gain/loss not reversed at the start of the current period. Cumulative revaluation balance growing rather than reflecting only current-period movement.

Coverage

FX Account Not in Revaluation Set

A monetary account denominated in foreign currency is not included in any revaluation set. New accounts opened during the period are frequently missed. GL-05 identifies unrevaled FX balances.

Table	Module	Purpose
GL_DAILY_RATES	GL	Exchange rates by currency, rate type, and date
GL_JE_HEADERS	GL	Revaluation journal batch headers
GL_JE_LINES	GL	Revaluation journal lines — gain/loss amounts
GL_BALANCES	GL	Period-end account balances in functional currency
GL_REVALUATIONS	GL	Revaluation set definitions
GL_LEDGERS	GL	Ledger configuration — currency, calendar, COA

Decision Framework

How Every Fix Decision Is Made

Before any data is modified in a production Oracle database, AP-01 walks through a four-stage decision process. Every condition identified by the diagnostic maps to exactly one resolution path.

First Option — Always

Can the front end fix this?

Oracle's own forms and concurrent programs are always the first option. If the condition can be corrected through Oracle's standard UI — a form, a concurrent program, a setup screen — that path is taken first. No consultant SQL required, no database risk, and the fix is fully supported by Oracle. The diagnostic identifies these conditions explicitly and states the exact front-end navigation path.

✓ Functional Fix

When Front End Is Not Available

Is a direct data fix safe to apply?

When the front-end path is unavailable or would require an unacceptable volume of manual steps, a direct fix is evaluated against explicit criteria. All of the following must be true before proceeding:

→The fix mirrors exactly what Oracle's own code would have done if the underlying condition were corrected

→All dependent tables have been identified and will be updated in the same transaction

→The fix is fully reversible — a single INSERT from the backup table restores the original state

→The environment patch level has been confirmed against the fix logic version

⚡ Direct Fix

Hard Stops — No Exceptions

Does this require Oracle Support?

Certain table areas are never touched directly, regardless of how well the underlying structure is understood. The diagnostic flags these conditions and generates the Service Request documentation:

✗XLA subledger tables — XLA_EVENTS, XLA_AE_HEADERS — incorrect changes corrupt the subledger audit trail in ways undetectable until period close fails or an auditor requests a reconciliation

✗Workflow engine tables — WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES — ad-hoc DML can corrupt the workflow engine state instance-wide

✗Recurring conditions after a fix — indicates a code defect, not a data error. Documented and submitted as a Service Request with a reproducible test case

⚠ Oracle Support

For All Approved Direct Fixes

Backup → Execute → Verify → Document

A timestamped backup table is created and row-count verified before the first UPDATE fires. Explicit parameter confirmation is required — the script will not self-execute. After execution, a verification query confirms the expected state. A complete change record — rows affected, before and after values, database username, timestamp — is written to the FIX_BACKUP_REGISTRY and becomes the primary artifact in the knowledge base entry for this incident.

📋 Documented

Condition Identified	Resolution Path	Notes
Exchange rate missing for period-end date and rate type	Direct Fix	GL-05 generates the INSERT for the missing rate in GL_DAILY_RATES with full backup. Rate value confirmed with Treasury before insertion. Revalue Balances resubmitted after rate is loaded.
Revaluation not run for the period	Functional First	Submit the Revalue Balances concurrent program for the revaluation set, period, and ledger. GL-05 provides the exact parameters and identifies the accounts in the revaluation set with their current foreign currency balances.
Wrong rate type used for revaluation	Functional First	Update the revaluation set to use the correct rate type via GL > Setup > Revaluation Sets. GL-05 identifies the current rate type and the available rates for the correct type on the period-end date.
Reversal period incorrect — entries not reversing	Functional First	Correct the reversal configuration in the revaluation set via GL > Setup > Revaluation Sets. GL-05 identifies the current reversal setting and the expected next-period reversal behavior.
Revaluation journal not posted	Functional First	Post the revaluation journal batch via GL > Journals > Post. GL-05 identifies the unposted revaluation batch and the total unrealized gain/loss amount pending posting.
Account not in revaluation set — FX account missed	Functional First	Add the account to the revaluation set via GL > Setup > Revaluation Sets. GL-05 identifies foreign currency account balances that are not included in any revaluation set.
Prior period revaluation not reversed	Direct Fix	GL-05 identifies the prior period revaluation journal that should have reversed but did not, calculates the reversal amount, and generates the reversing entry with full backup and Controller authorization.
Cumulative translation adjustment — translation not run	Functional First	Submit the Translate Balances concurrent program for the consolidation ledger. GL-05 identifies translation sets that have not been run for the current period and the accounts requiring translation.

Safeguards

Nothing Executes Without a Safety Net

Before any data fix runs, the script verifies pre-flight conditions and creates a complete verified backup. If any check fails, the script aborts. There is no partial execution path.

Pre-Flight Checks — All Must Pass

✓

POSTED_FLAG = 'N'

Will not modify a posted transaction under any circumstances

✓

ACCOUNTING_EVENT_ID IS NULL

Will not modify rows with an active or pending XLA accounting event

✓

No active database lock

Checks V$LOCK — will not proceed if another session holds a lock on target rows

✓

CONS_BACKUP schema writable

Backup schema must be accessible before any DML is permitted

✓

Explicit confirmation required

Script outputs a confirmation prompt — DML does not execute until consultant enters the case number as the execution parameter

Backup Methodology

Before the first UPDATE fires, the script creates a complete copy of every row to be modified. Tables are named CONS_BACKUP.<TABLE>_<CASE#> and persist permanently after execution.

GL_JE_HEADERS

GL_JE_LINES

GL_DAILY_RATES

GL_BALANCES

Row count verified after backup creation. If backup fails for any reason the script aborts without executing any DML. Rollback is a single INSERT from the backup table. No reconstruction required.

GL-05 — Pre-Flight & Backup Verification

════════════════════════════════════════════════════════════
  PRE-FLIGHT SAFETY CHECK
════════════════════════════════════════════════════════════
  Ledger             : US Primary Ledger
  Revaluation Set    : US-MONETARY-REVAL
  CONS_BACKUP Schema : Accessible ✓
  Session Lock Check : No locks on GL_DAILY_RATES ✓
────────────────────────────────────────────────────────────
  ALL PRE-FLIGHT CHECKS PASSED
════════════════════════════════════════════════════════════
  Creating : CONS_BACKUP.GL_DAILY_RATES_525840
  Rows     : 1 new rate row backed up ✓
  Registry : FIX_BACKUP_REGISTRY — ID 4137 created ✓
────────────────────────────────────────────────────────────
  BACKUP COMPLETE
════════════════════════════════════════════════════════════
  Enter case number to confirm rate insert : 525840
  Confirmed. Loading CAD rate 1.3618...
════════════════════════════════════════════════════════════

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-GL-525840-001

Revaluation Incomplete — CAD Corporate Exchange Rate Missing for Period-End Date

EBS R12.2.10 · General Ledger

● RESOLVED

Symptom

Root Cause

Tables

GL_DAILY_RATES — FROM_CURRENCY = CAD, RATE_TYPE = Corporate, CONVERSION_DATE = 28-FEB-2026 (missing record)
GL_JE_HEADERS — JE_CATEGORY = Revaluation (FEB-2026 — CAD not present)

Fix Applied

Prevention

R12 Guide (PDF)	Title & Chapter	Detail
120glug.pdf	Oracle General Ledger User's Guide — Revaluation	Foreign currency revaluation program, unrealized gain/loss accounts, and reversal entries
120glug.pdf	Oracle General Ledger User's Guide — Reporting	Foreign currency translation reports and revaluation reconciliation
120ceug.pdf	Oracle Cash Management User Guide — Multi-Currency Handling	pp. 1-8 to 1-9: Multi-currency bank reconciliation impacting revaluation balances

Revaluation Diagnostic

Why This Fails — and What It Costs

What This Script Diagnoses

What the Report Looks Like

The Four-Layer Architecture in GL-05

Backup & Rollback for GL-05

Tables Backed Up — GL-05

Pre-Flight Safety Guards

FIX_BACKUP_REGISTRY Entry

Auto-Generated Knowledge Base Article

What This Script Finds

Exchange Rate Not Loaded for Period End

Revaluation Not Submitted

Prior Period Entry Not Reversed

FX Account Not in Revaluation Set

Tables Examined

How Every Fix Decision Is Made

Nothing Executes Without a Safety Net

Every Execution Produces a Record

Oracle Documentation References

Ready to Resolve This in Your Environment?

Why This Fails — and What It Costs

What This Script Diagnoses

What the Report Looks Like

The Four-Layer Architecture in GL-05

Backup & Rollback for GL-05

Tables Backed Up — GL-05

Pre-Flight Safety Guards

FIX_BACKUP_REGISTRY Entry

Auto-Generated Knowledge Base Article

What This Script Finds

Exchange Rate Not Loaded for Period End

Revaluation Not Submitted

Prior Period Entry Not Reversed

FX Account Not in Revaluation Set

Tables Examined

How Every Fix Decision Is Made

Nothing Executes Without a Safety Net

Every Execution Produces a Record

Oracle Documentation References

Related Diagnostic Scripts

GL Period Close Readiness

Consolidation Diagnostic

Ready to Resolve This in Your Environment?