Analytics Catalog/Oracle Fusion ERP/Fusion Accounting Hub/AHCS Create Accounting Errors Report
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · Fusion Accounting Hub

AHCS Create Accounting Errors Report

Fusion Accounting Hub

The errors raised when the Accounting Hub's Create Accounting process tries to account externally-sourced transactions — the source transaction, the rule that failed, and the error — so the team can fix mapping gaps and get the entries posted.

Related  Companion to the Subledger Period Close Exceptions Report, for Accounting Hub source systems.

Run note · Performance  The subledger (XLA) join — especially Projects-to-XLA — is a known BI Publisher performance trap on large ledgers. Pre-join it in the warehouse, or apply tight ledger, period, and source filters before running online.

Sample build of the AHCS Create Accounting Errors Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

AHCS Create Accounting Errors Report
Sample build · illustrative
Filters
Accounting Period
FEB-26
Event Type
Standard
From Accounting Date
2026-02-28
Ledger
US Primary
Request Id
1003
Subledger Application
US Primary
18,200
Transactions processed
98.6%
Accounted
255
In error
Source SystemTransactionEvent TypeErrorAccounting DateLedger
SampleSampleStandardSample2026-04-30US Primary
Corporate2026-03-31EU Primary
SampleSampleStandardSample2026-02-28US Primary
Default2026-01-31UK Primary
SampleSampleStandardSample2025-12-31US Primary
SampleSampleStandardSample2026-04-30US Primary
AI Analyst · active
reading

The report reads the XLA transaction and event tables for entries Create Accounting could not account, grouping them by source system and error.

flag

255 transactions failed, and 200 share one error — a missing account-rule mapping for a single event type from one source system, not 255 unique problems.

root cause & next step

Add the missing mapping for that event type in the Accounting Hub rules, then re-run Create Accounting; the 200 should clear in one pass.

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
WITH SECURITY_TBL AS
(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_AHCS_MANAGER_JOB', '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
	
)

SELECT  /*+parallel(24) */ 
 GLL.NAME LEDGER_NAME
, XAH.PERIOD_NAME AS ACCOUNTING_PERIOD
,XAH.ACCOUNTING_DATE
, XEC.NAME AS EVENT_CLASS
, XET.NAME AS EVENT_TYPE
,XE.EVENT_DATE
, GJST.USER_JE_SOURCE_NAME AS JOURNAL_SOURCE 
, GJCT.USER_JE_CATEGORY_NAME AS JOURNAL_CATEGORY
, XTE.TRANSACTION_NUMBER
, XAL.AE_LINE_NUM LINE_NUMBER
,XAL.CURRENCY_CODE ENTERED_CURRENCY
,XAL.ENTERED_DR ENTERED_DR
,XAL.ENTERED_CR ENTERED_CR
,GLL.CURRENCY_CODE LEDGER_CURRENCY
,XAL.ACCOUNTED_DR ACCOUNTED_DR
,XAL.ACCOUNTED_CR ACCOUNTED_CR
, CASE WHEN NVL(GCC.SEGMENT4,'-1')!='-1' THEN GCC.SEGMENT1 || '.' || GCC.SEGMENT2 || '.' || GCC.SEGMENT3 || '.' || GCC.SEGMENT4 || '.' || GCC.SEGMENT5
 || '.' || GCC.SEGMENT6 || '.' || GCC.SEGMENT7 || '.' || GCC.SEGMENT8 || '.' || GCC.SEGMENT9 END AS ACCOUNT_CODE_COMBINATION
 , FLV3.MEANING AS ACCOUNTING_CLASS
,FLV.MEANING ACCOUNTING_ENTRY_STATUS
, 'Unposted' POSTING_STATUS
, XAH.CREATION_DATE JOURNAL_CREATION_DATE
,XAH.DESCRIPTION HEADER_DESCRIPTION
,XAL.DESCRIPTION LINE_DESCRIPTION
,XAE.encoded_msg Error_Message
,XTH.REQUEST_ID
,XAE.REQUEST_ID ERROR_REQUEST_ID
FROM
XLA_TRANSACTION_ENTITIES XTE,
XLA_TRANSACTION_HEADERS XTH,
XLA_AE_HEADERS XAH,
GL_LEDGERS GLL,
XLA_SUBLEDGERS XSL,
XLA_AE_LINES XAL,
GL_CODE_COMBINATIONS GCC,
XLA_SUBLEDGERS_TL XST
,XLA_EVENT_TYPES_TL XET
, GL_JE_SOURCES_TL GJST
, GL_JE_CATEGORIES_TL GJCT
--,gl_je_batches GJB
--, FND_LOOKUP_VALUES_VL FLV2
, FND_LOOKUP_VALUES_VL FLV
,FND_LOOKUP_VALUES_VL FLV3
--,GL_IMPORT_REFERENCES GIR

,XLA_EVENT_CLASSES_TL XEC
,XLA_EVENTS XE

,XLA_ACCOUNTING_ERRORS XAE
 --,XLA_FSN_EVENTS_INT EVTINT 
,SECURITY_TBL ST

--,XLA_AE_LINES XAL1

WHERE 1=1
AND ST.LEDGER_ID=GLL.LEDGER_ID
--AND XAH.AE_HEADER_ID = XAL.AE_HEADER_ID
AND XAH.APPLICATION_ID=XTH.APPLICATION_ID(+)
AND XAH.EVENT_ID=XTH.EVENT_ID(+)
--AND XAH.APPLICATION_ID = XAL.APPLICATION_ID
AND XAH.ENTITY_ID = XTE.ENTITY_ID 
AND XAH.APPLICATION_ID = XTE.APPLICATION_ID  
AND XAH.APPLICATION_ID = XSL.APPLICATION_ID 
AND XSL.APPLICATION_ID=XST.APPLICATION_ID
AND xsT.LANGUAGE  = userenv('LANG')
and xah.application_id = xet.application_id
and xah.event_type_code = xet.event_type_code
AND xET.LANGUAGE  = userenv('LANG')
AND XSL.IMPLEMENTATION_MODE_CODE = 'SIMPLIFIED'
AND XAH.LEDGER_ID = GLL.LEDGER_ID
--AND XST.APPLICATION_NAME ='DOM INVENTORY'
--AND NVL(XAL.SR31,'-1')!='-1'
AND XAL.CODE_COMBINATION_ID  = GCC.CODE_COMBINATION_ID(+)
AND GJST.JE_SOURCE_NAME=XSL.JE_SOURCE_NAME
AND GJCT.JE_CATEGORY_NAME(+)=XAH.JE_CATEGORY_NAME
AND GJCT.LANGUAGE (+) = userenv('LANG')
AND GJST.LANGUAGE  = userenv('LANG')
AND FLV3.LOOKUP_TYPE(+)='XLA_ACCOUNTING_CLASS'
AND FLV3.LOOKUP_CODE(+)= XAL.ACCOUNTING_CLASS_CODE
AND FLV.LOOKUP_TYPE(+)='XLA_ACCOUNTING_ENTRY_STATUS'
AND FLV.LOOKUP_CODE(+)=XAH.ACCOUNTING_ENTRY_STATUS_CODE
/*AND GJB.GROUP_ID(+)=XAH.GROUP_ID
   AND FLV2.LOOKUP_TYPE(+)='MJE_BATCH_STATUS'
   AND FLV2.LOOKUP_CODE(+)=GJB.STATUS
   AND GIR.GL_SL_LINK_ID(+)=XAL.GL_SL_LINK_ID	
   AND GIR.GL_SL_LINK_TABLE(+)	=XAL.GL_SL_LINK_TABLE	
   AND GIR.JE_BATCH_ID=GJB.JE_BATCH_ID(+)
   AND XAL.ACCOUNTING_CLASS_CODE =(SELECT  XAL2.ACCOUNTING_CLASS_CODE
                                   FROM XLA_AE_LINES XAL2
								   WHERE XAL2.AE_HEADER_ID=XAL.AE_HEADER_ID
								   AND XAL2.AE_LINE_NUM=XAL.AE_LINE_NUM
								   AND XAL2.APPLICATION_ID=XAL.APPLICATION_ID
								   AND (XAL2.ACCOUNTING_CLASS_CODE!='EXCHANGE_GAIN_LOSS'
								   OR (XAL2.ACCOUNTED_DR!=0 OR XAL2.ACCOUNTED_CR!=0))
								   )*/
								   
								   
	AND XEC.APPLICATION_ID=XET.APPLICATION_ID
	AND XEC.ENTITY_CODE=XET.ENTITY_CODE
	AND XEC.EVENT_CLASS_CODE=XET.EVENT_CLASS_CODE
	AND XEC.LANGUAGE=userenv('LANG')
	AND XAH.APPLICATION_ID=XEC.APPLICATION_ID
	AND XAH.APPLICATION_ID=XE.APPLICATION_ID
	AND XAH.EVENT_ID=XE.EVENT_ID
	AND XAH.ENTITY_ID=XE.ENTITY_ID
	
	AND XAH.APPLICATION_ID(+)=XAE.APPLICATION_ID
	AND XAH.LEDGER_ID(+)=XAE.LEDGER_ID
	AND XAH.EVENT_ID(+)=XAE.EVENT_ID
	AND XAH.ENTITY_ID(+)=XAE.ENTITY_ID
	AND XAH.AE_HEADER_ID(+)=XAE.AE_HEADER_ID
	AND XAL.APPLICATION_ID(+)=XAE.APPLICATION_ID
	and XAL.AE_HEADER_ID(+)=XAE.AE_HEADER_ID
	AND XAL.ae_line_num(+)=XAE.ae_line_num
	and XAE.EVENT_ID=XE.EVENT_ID
	
	 /*AND  XAE.EVENT_ID 	= EVTINT.EVENT_ID
	 AND XE.EVENT_ID                 = EVTINT.EVENT_ID
	 AND  XET.EVENT_TYPE_CODE         = EVTINT.EVENT_TYPE_CODE
	 AND  XEC.APPLICATION_ID          = EVTINT.APPLICATION_ID
       AND  XEC.EVENT_CLASS_CODE        = EVTINT.EVENT_CLASS_CODE
	  -- AND  EVTINT.REPORT_REQUEST_ID    = XAE.REQUEST_ID */
	   AND  (XE.PROCESS_STATUS_CODE    IN ('I')
            OR NVL(XE.HAS_WARNINGS_FLAG,'N')    = 'Y')
	
	AND UPPER(FLV.MEANING) NOT IN ('FINAL')

	
--Parameters
AND (XST.APPLICATION_NAME IN (:P_SUBLEDGER_APPLICATION) OR 'All' IN ('All'||:P_SUBLEDGER_APPLICATION))
AND XAH.ACCOUNTING_DATE BETWEEN :P_FROM_ACCOUNTING_DATE AND :P_TO_ACCOUNTING_DATE
AND (XAH.PERIOD_NAME IN (:P_ACCOUNTING_PERIOD) OR 'All' IN ('All'||:P_ACCOUNTING_PERIOD))
AND (GLL.NAME IN (:P_Ledger) OR 'All' IN ('All'||:P_Ledger))
AND (XTH.REQUEST_ID  IN (:P_REQUEST_ID) OR 'All' IN ('All'||:P_REQUEST_ID))
AND (XET.NAME  IN (:P_EVENT_TYPE) OR 'All' IN ('All'||:P_EVENT_TYPE))

ORDER BY GLL.NAME, XAH.PERIOD_NAME, XTE.TRANSACTION_NUMBER, XAL.AE_LINE_NUM, XET.NAME/*,  GCC.SEGMENT1 || '.' || GCC.SEGMENT2 || '.' || GCC.SEGMENT3 || '.' || GCC.SEGMENT4 || '.' || GCC.SEGMENT5
 || '.' || GCC.SEGMENT6 || '.' || GCC.SEGMENT7 || '.' || GCC.SEGMENT8 || '.' || GCC.SEGMENT9*/
:P_ACCOUNTING_PERIOD :P_EVENT_TYPE :P_FROM_ACCOUNTING_DATE :P_Ledger :P_REQUEST_ID :P_SUBLEDGER_APPLICATION :P_TO_ACCOUNTING_DATE :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 transactionAmount
●— fact → dimension join
ElementTypeDefinition
GL_ACCESS_SETSdimensiondimension
FUN_USER_ROLE_DATA_ASGNMNTSdimensiondimension
PER_ROLES_DNdimensiondimension
PER_USER_ROLESdimensiondimension
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.
Fusion Accounting Hub 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
XLA_TRANSACTION_ENTITIES23
XLA_TRANSACTION_HEADERSSetup / configuration table — joined for reference, not exposed for analytics
XLA_AE_HEADERS1619
XLA_SUBLEDGERSSetup / configuration table — joined for reference, not exposed for analytics
XLA_AE_LINES2317
GL_CODE_COMBINATIONS761
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.