Search Results ref_ae_line_num
Overview
XLA.XLA_AE_LINES_GT is a global temporary table (GTT) in the Subledger Accounting (XLA) schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It is the transient staging area used by the Subledger Accounting Engine to assemble, map, and validate accounting entry lines before they are committed to the permanent XLA_AE_LINES table. Unlike a conventional heap table, this object carries a data duration of SYS$TRANSACTION, meaning each session sees only the rows it has inserted and those rows are purged at transaction commit or rollback. This design prevents contention and cross-session leakage during concurrent accounting runs across multiple ledgers and applications.
The table holds 318 documented columns and is registered in FND Design Data as XLA.XLA_AE_LINES_GT. Its heuristic Data Vault classification is standalone, with no foreign keys declared within the database constraint model aside from a documented reference to GL_ENCUMBRANCE_TYPES. In Data Vault terms, it behaves most like a staging satellite: it carries descriptive attributes and measures tied to an accounting event rather than serving as a durable hub or link. That classification should be treated as a modeling suggestion, reflecting the table's temporary and process-scoped nature.
Key Information Stored
The columns below are the most operationally significant within the documented structure. They span identification, account derivation, and monetary measurement.
- AE_HEADER_ID — Surrogate reference to the accounting entry header being staged.
- TEMP_LINE_NUM / AE_LINE_NUM / HEADER_NUM / LINE_HASH_NUM — Temporary and final line identifiers plus the header sequence and hash used for duplicate detection.
- EVENT_ID / REF_EVENT_ID / REF_AE_HEADER_ID / REF_AE_LINE_NUM — Source and cross-referenced accounting event and line pointers.
- CODE_COMBINATION_ID — The derived accounting flexfield combination for the primary account.
- ALT_CODE_COMBINATION_ID — The alternate account combination, populated when a secondary chart-of-accounts mapping applies; this is the column the user searched on.
- SOURCE_COA_ID / CCID_COA_ID / SL_COA_MAPPING_ID / SL_COA_MAPPING_NAME — Chart-of-accounts identifiers and the subledger-to-GL COA mapping that produced the alternate account.
- SEGMENT1–SEGMENT30 / ALT_SEGMENT1–ALT_SEGMENT30 — Denormalized flexfield segment values for the primary and alternate account combinations.
- ENTERED_AMOUNT / ENTERED_DR / ENTERED_CR / ACCOUNTED_DR / ACCOUNTED_CR / LEDGER_AMOUNT — Entered and accounted debit/credit measures.
- LEDGER_ID / BALANCE_TYPE_CODE / ACCOUNTING_CLASS_CODE / ACCOUNTING_LINE_TYPE_CODE — Ledger and balance classification driving line derivation.
- CURRENCY_CODE / CURRENCY_CONVERSION_RATE / CURRENCY_CONVERSION_TYPE / CURRENCY_CONVERSION_DATE — Currency translation context.
- ENCUMBRANCE_TYPE_ID — The sole documented foreign key, referencing
GL_ENCUMBRANCE_TYPES.
The unique index XLA_AE_LINES_GT_U1 spans LEDGER_ID, REF_AE_HEADER_ID, TEMP_LINE_NUM, AE_HEADER_ID, HEADER_NUM, EVENT_ID and functions as the business-key candidate. Four nonunique indexes (N1–N4) support COA mapping lookups, balance-type filtering, and gain/loss aggregation.
Common Use Cases and Queries
Because data is session-scoped, queries are meaningful only within the concurrent program or PL/SQL session that populated the table. Typical diagnostic and reporting scenarios include:
- Inspecting generated lines before posting to confirm account derivation:
SELECT ae_header_id, temp_line_num, code_combination_id, alt_code_combination_id, accounted_dr, accounted_cr FROM xla_ae_lines_gt WHERE ledger_id = :p_ledger ORDER BY temp_line_num; - Auditing alternate COA mapping results: filter on
ALT_CODE_COMBINATION_ID IS NOT NULLand join toSL_COA_MAPPING_IDto verify the mapping name used. - Detecting unbalanced entries by aggregating
ACCOUNTED_DRandACCOUNTED_CRperAE_HEADER_ID. - Reconciling gain/loss calculations via
GAIN_OR_LOSS_FLAG,GAIN_OR_LOSS_REF, andCALCULATE_G_L_AMTS_FLAG, which are indexed onXLA_AE_LINES_GT_N3andN4.
Related Objects
The table participates in the XLA accounting pipeline alongside the following significant objects, joined on the columns indicated.
- XLA_AE_LINES — Permanent target of the staged lines, joined on
AE_HEADER_IDandAE_LINE_NUM. - XLA_AE_HEADERS — Header for both staging and final lines, joined on
AE_HEADER_IDandLEDGER_ID. - XLA_EVENTS — Source accounting events, joined on
EVENT_ID. - GL_CODE_COMBINATIONS — Resolves
CODE_COMBINATION_IDandALT_CODE_COMBINATION_ID. - GL_ENCUMBRANCE_TYPES — Documented FK target via
ENCUMBRANCE_TYPE_ID. - XLA_LEDGERS / GL_LEDGERS — Ledger definition referenced by
LEDGER_ID. - XLA_SUBLEDGER_COA_MAPPINGS — Provides
SL_COA_MAPPING_IDandSL_COA_MAPPING_NAMEfor alternate COA derivation. - XLA_ACCOUNTING_PKG / XLA_AE_PKG — PL/SQL APIs that populate, validate, and commit rows from this GTT.
-
TABLE: XLA.XLA_AE_LINES_GT
12.1.1
owner:XLA, object_type:TABLE, fnd_design_data:XLA.XLA_AE_LINES_GT, object_name:XLA_AE_LINES_GT, status:VALID,
-
TABLE: XLA.XLA_AE_LINES_GT
12.2.2
owner:XLA, object_type:TABLE, fnd_design_data:XLA.XLA_AE_LINES_GT, object_name:XLA_AE_LINES_GT, status:VALID,
-
APPS.XLA_AE_HEADER_PKG SQL Statements
12.1.1
-
APPS.ARP_MRC_XLA_UPGRADE SQL Statements
12.1.1
-
APPS.XLA_AE_HEADER_PKG SQL Statements
12.2.2
-
APPS.ARP_MRC_XLA_UPGRADE SQL Statements
12.2.2
-
APPS.XLA_AE_LINES_PKG SQL Statements
12.1.1
-
APPS.XLA_AE_LINES_PKG SQL Statements
12.2.2
-
PACKAGE BODY: APPS.ARP_MRC_XLA_UPGRADE
12.1.1
-
PACKAGE BODY: APPS.ARP_MRC_XLA_UPGRADE
12.2.2
-
APPS.XLA_THIRD_PARTY_MERGE SQL Statements
12.2.2
-
APPS.XLA_THIRD_PARTY_MERGE SQL Statements
12.1.1
-
PACKAGE BODY: APPS.XLA_AE_LINES_PKG
12.1.1
-
PACKAGE BODY: APPS.XLA_AE_HEADER_PKG
12.1.1
-
PACKAGE BODY: APPS.XLA_AE_LINES_PKG
12.2.2
-
PACKAGE BODY: APPS.XLA_AE_HEADER_PKG
12.2.2
-
PACKAGE BODY: APPS.XLA_THIRD_PARTY_MERGE
12.1.1
-
PACKAGE BODY: APPS.XLA_THIRD_PARTY_MERGE
12.2.2
-
eTRM - XLA Tables and Views
12.2.2
-
eTRM - XLA Tables and Views
12.1.1