Analytics Catalog/Oracle Fusion ERP/General Ledger/Pending Transaction Detail Report
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · General Ledger

Pending Transaction Detail Report

General Ledger

Subledger transactions that have been accounted but not yet posted to GL, in detail — source, amount, and account — so the close team can see exactly what is still in flight between the subledgers and the ledger.

Run note · BIP run  High-volume GL extracts can exceed BI Publisher's online output limit and time out. Run it as a scheduled process (ESS) with output bursted to file or email rather than online preview, and bound it by ledger and period.

Sample build of the Pending Transaction Detail Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Pending Transaction Detail Report
Sample build · illustrative
Filters
Bstatus
Validated
From Period
FEB-26
Ledger
US Primary
To Period
FEB-26
Xdo User Name
Globex Holdings
41
Pending batches
$3.20M
Pending value
14
Over 2 days old
LedgerSourceJournal BatchAccountEntered AmountStatusAccounting Date
US PrimarySampleSample1000-2100-000$1,240,500.00Open2026-04-30
EU Primary1000-5400-000$842,150.75Posted2026-03-31
US PrimarySampleSample1000-1410-000$96,400.00Validated2026-02-28
UK Primary2000-2100-000$1,005,233.10Open2026-01-31
US PrimarySampleSample1000-6300-000$58,720.40Paid2025-12-31
US PrimarySampleSample1000-2100-000$1,240,500.00Open2026-04-30
AI Analyst · active
reading

The report reads GL_JE_BATCHES and GL_JE_HEADERS for imported-but-unposted entries, with their subledger source and amount.

flag

14 batches have been pending more than two days — aged pending items usually mean a posting that errored quietly, and they are the gap between subledger and GL balances at close.

root cause & next step

Post or investigate the aged batches; a recurring backlog from one source points to a scheduled posting job that isn't running.

Illustrative data. The live interactive version — drill-through, filters, export, and the AI Analyst — runs on your warehouse. See it live →

This is the report's BI Publisher data model — the SQL data set BI Publisher runs against Oracle tables to produce the output. The same SQL becomes a dbt model in your warehouse, so one definition drives both the formatted report and the analytics layer.

Data sources

How it interconnects: this data set reads the physical tables above. Those same tables surface in OTBI as subject areas and in BICC as PVOs — three lenses on one source. Open any table to trace its subject areas and View Objects.
SQL data set · genericized · parameterized · no hardcoded segments
Show / hide SQL
<![CDATA[/*
Report ID   : RPT-R2R-010
Report Name : Pending Transaction Details Report
Description : Provides the ability to show all the unposted journals, but it is used because it displays all the journal line debits/credits to view the account strings
Date                 Version           Developed by           Description
-----------------------------------------------------------------------------------------------
6/15/2023            1.0               Rajkumar              Initial Development
*/
WITH SECURITY_TBL AS
(
SELECT DISTINCT GL.LEDGER_ID
FROM GL_LEDGERS GL
,(
SELECT DISTINCT GL.LEDGER_ID
FROM 
GL_LEDGERS GL,
GL_ACCESS_SETS GAS,
	FUN_USER_ROLE_DATA_ASGNMNTS FURDA,
	PER_ROLES_DN PRD,
	PER_USER_ROLES PUR,
	PER_USERS PU

WHERE 
UPPER(GL.LEDGER_CATEGORY_CODE) <> 'NONE'
AND GAS.ACCESS_SET_ID=GL.IMPLICIT_ACCESS_SET_ID
	AND (GAS.ACCESS_SET_ID =FURDA.ACCESS_SET_ID OR GL.LEDGER_ID=FURDA.LEDGER_ID)
	AND UPPER(FURDA.role_name) in ('XXC_GL_INQUIRY_JOB','XXC_GENERAL_ACCOUNTANT_JOB','XXC_GENERAL_ACCOUNTING_MANAGER_JOB')
	AND UPPER(FURDA.ACTIVE_FLAG) = 'Y'
	AND UPPER(FURDA.ROLE_NAME) = UPPER(PRD.ROLE_COMMON_NAME)
	AND PRD.ROLE_ID = PUR.ROLE_ID
	AND PUR.USER_ID = PU.USER_ID
	AND  UPPER(PU.USERNAME) = UPPER(:xdo_user_name)
	AND PU.USER_GUID = FURDA.USER_GUID

) ST
WHERE 
1=1

AND ST.LEDGER_ID=GL.LEDGER_ID
)
SELECT 
	GL.name LEDGER_NAME,
	GP.period_name PERIOD,
	GJB.creation_date JOURNAL_BATCH_CREATION_DATE,
	GJB.name JOURNAL_BATCH,
	GJH.name JOURNAL_NAME,
	GJH.currency_code JOURNAL_CURRENCY,
	GJCV.user_je_category_name JOURNAL_CATEGORY,
	GJSV.user_je_source_name JOURNAL_SOURCE,
	FLV.description BATCH_STATUS,
	GJL.je_line_num JOURNAL_LINE_NUMBER,
	FND_FLEX_EXT.GET_SEGS('GL','GL#',GCC.chart_of_accounts_id,gcc.code_combination_id) GL_ACCOUNT_COMBINATION,
	NVL(GJL.entered_dr,0) ENTERED_DR,
	NVL(GJL.entered_cr,0) ENTERED_CR,
	NVL(GJL.accounted_dr,0) ACCOUNTED_DR,
	NVL(GJL.accounted_cr,0) ACCOUNTED_CR,
	GJL.description LINE_DESCRIPTION,
	GJL.created_by JOURNAL_LINE_CREATED_BY,
	GJL.creation_date JOURNAL_LINE_CREATION_DATE,
	GJL.last_updated_by JOURNAL_LINE_LAST_UPDATED_BY,
	GJL.last_update_date JOURNAL_LINE_LAST_UPDATE_DATE
FROM 
	gl_je_batches GJB,
	gl_je_headers GJH,
	gl_je_lines GJL,
	gl_ledgers GL,
	gl_periods GP,
	gl_je_categories_vl GJCV,
	gl_je_sources_vl GJSV,
	gl_code_combinations GCC,
	fnd_lookup_values FLV,
	gl_period_sets GPS,
	SECURITY_TBL ST
WHERE
	1=1
	AND GJB.je_batch_id					= GJH.je_batch_id
	AND GJH.je_header_id				= GJL.je_header_id
	AND GJH.ledger_id					= GL.ledger_id
	AND GJH.period_name 				= GP.period_name
	AND GJH.je_category 				= GJCV.je_category_name
	AND GJH.je_source					= GJSV.je_source_name
	AND GJL.code_combination_id			= GCC.code_combination_id
	AND GJB.status 						not in('P')
	AND GP.PERIOD_SET_NAME				= GPS.PERIOD_SET_NAME
	AND GPS.PERIOD_SET_NAME				= GL.PERIOD_SET_NAME
	AND GJB.status 						= FLV.lookup_code
	AND FLV.lookup_type 				= 'MJE_BATCH_STATUS'
	AND FLV.language					= 'US'
	AND GL.LEDGER_ID					= ST.ledger_id
	AND (GL.name                   		IN (:P_LEDGER)
	OR  'All'                      		IN (:P_LEDGER||'All'))
	AND GP.start_date					>= (select distinct min(start_date) from gl_periods where period_name = :P_FROM_PERIOD)
	AND GP.end_date						<= (select distinct max(end_date) from gl_periods where period_name = :P_TO_PERIOD)  	
	AND (GJB.status                		IN (:P_BSTATUS)
	OR  'All'                      		IN (:P_BSTATUS||'All'))
ORDER BY 1,2,3]]>
:P_BSTATUS :P_FROM_PERIOD :P_LEDGER :P_TO_PERIOD :xdo_user_name

The data-warehouse model — one fact surrounded by conformed dimensions (what you slice by) and measures (what you aggregate), expressed as dbt so it migrates with you. Grain: one row per source transaction.

GL_ACCESS_SETSdimensionFUN_USER_ROLE_DATA_ASGNM…dimensionPER_ROLES_DNdimensionPER_USER_ROLESdimensionGL_LEDGERSfact · one row per source transactionEntered Amount
●— fact → dimension join
ElementTypeDefinition
GL_ACCESS_SETSdimensiondimension
FUN_USER_ROLE_DATA_ASGNMNTSdimensiondimension
PER_ROLES_DNdimensiondimension
PER_USER_ROLESdimensiondimension
Entered Amountmeasuremeasure
Runs on your cloud warehouse — Snowflake, BigQuery, Redshift, or Synapse on AWS, Google Cloud, Azure, or any provider. Reconciled to the source control total — 0% variance by design. You own the code, the model, and the data.
How the data gets here: a BICC bulk extract of the source tables above, on the same pattern for every report. See the extraction pattern & data flow →
See the complete model
How this report's fact and dimensions fit the full picture, via conformed keys.
General Ledger data model →Enterprise model →

Every source object behind this report. Each linked table has its own page with full column descriptions, drawn from the Oracle BICC lineage and articulated for practitioners.

TableReporting columnsSubject areas
GL_LEDGERS10104
GL_ACCESS_SETSSetup / configuration table — joined for reference, not exposed for analytics
FUN_USER_ROLE_DATA_ASGNMNTSSetup / configuration table — joined for reference, not exposed for analytics
PER_ROLES_DNSetup / configuration table — joined for reference, not exposed for analytics
PER_USER_ROLES160
PER_USERS2227
GL_JE_BATCHES142
GL_JE_HEADERS342
GL_JE_LINES262
GL_PERIODSSetup / configuration table — joined for reference, not exposed for analytics
GL_JE_CATEGORIES_VLSetup / configuration table — joined for reference, not exposed for analytics
GL_JE_SOURCES_VLSetup / configuration table — joined for reference, not exposed for analytics
Reporting columns = fields the report selects that are exposed as analytics attributes; subject areas = the OTBI subject areas the table appears in. Setup and configuration tables (master data, ledger and book setup, lookups) are referenced by the report's joins but aren't exposed as analytics columns or subject areas — that's expected, not a gap.