Results for “accounting_entry_status_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

XLA_AE_HEADERS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite subledger accounting (XLA). It presents the header-level accounting entries generated by the Subledger Accounting engine, enriched with the legal entity identifier resolved from the transaction entity. Accounting event headers created by the Create Accounting process are stored in XLA_AE_HEADERS; the view joins this table to XLA_TRANSACTION_ENTITIES so that each accounting header row is returned together with its owning legal entity. Because legal entity is a critical partitioning attribute for subledger accounting data, the view is the standard interface through which reports, reconciliations, and integration extracts obtain accounting header information without having to perform the join explicitly.

The view retains the APPS owner and VALID status in both 12.1.1 and 12.2.2. Its column list follows the underlying base table almost completely, with LEGAL_ENTITY_ID sourced from the transaction entity table rather than the header.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over two referenced base objects, both exposed as synonyms in the APPS schema:

• XLA_AE_HEADERS — the primary subledger accounting header table, aliased HR in the view text.
• XLA_TRANSACTION_ENTITIES — the transaction entity table, aliased ET, supplying LEGAL_ENTITY_ID.

The view text joins the two on ET.ENTITY_ID = HR.ENTITY_ID. The accounting header carries the entity reference, and the transaction entity resolves it to the legal entity that owns the transaction. No aggregation or filtering is applied, so the view is effectively a one-to-one projection of XLA_AE_HEADERS with the legal entity attribute appended. Because it is a simple view over base tables, DML against it is generally not supported and should be directed to the underlying tables.

Key Columns

The view exposes the full set of accounting header attributes. Notable columns include:

• AE_HEADER_ID — primary key of the accounting header; joins to XLA_AE_LINES.
• APPLICATION_ID, LEDGER_ID, LEGAL_ENTITY_ID — the accounting context: source application, ledger, and legal entity.
• ACCOUNTING_DATE / GL_DATE, PERIOD_NAME — the accounting date and the GL period to which the entry belongs (the view exposes the accounting date under the GL_DATE label).
• JE_CATEGORY_NAME — the journal category used when the entry is transferred to General Ledger.
• GL_TRANSFER_STATUS_CODE, GL_TRANSFER_DATE — whether the header has been transferred to GL and when.
• ACCOUNTING_ENTRY_STATUS_CODE, ACCOUNTING_ENTRY_TYPE_CODE — the status of the accounting entry (for example, final or draft) and whether it is a standard or accrual entry.
• DOC_SEQUENCE_ID, DOC_SEQUENCE_VALUE — document sequencing assignment for the header.
• EVENT_ID, EVENT_TYPE_CODE, ACCOUNTING_BATCH_ID — links back to the accounting event and the batch that produced the entry.
• PRODUCT_RULE_CODE, PRODUCT_RULE_TYPE_CODE, PRODUCT_RULE_VERSION — the accounting rule applied.
• BALANCE_TYPE_CODE, FUNDS_STATUS_CODE — balance type and funds check outcome where applicable.
• PARENT_AE_HEADER_ID, PARENT_AE_LINE_NUM, ACCRUAL_REVERSAL_FLAG — parentage and accrual reversal indicators.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield columns.
• Creation and audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is typically used to reconcile subledger accounting output to GL, to report accounting entries by legal entity or ledger, and to identify entries not yet transferred to GL.

Listing finalized accounting headers for a ledger:

SELECT ae_header_id, je_category_name, gl_date, period_name,
       accounting_entry_status_code, gl_transfer_status_code
FROM   apps.xla_ae_headers_v
WHERE  ledger_id = :ledger_id
AND    accounting_entry_status_code = 'F'
ORDER BY gl_date;

Finding entries pending transfer to General Ledger:

SELECT ae_header_id, application_id, ledger_id, legal_entity_id,
       gl_date, gl_transfer_status_code
FROM   apps.xla_ae_headers_v
WHERE  gl_transfer_status_code = 'N';

Reporting volume by legal entity and event type:

SELECT legal_entity_id, event_type_code, COUNT(*) headers
FROM   apps.xla_ae_headers_v
GROUP BY legal_entity_id, event_type_code;

Because the view already carries LEGAL_ENTITY_ID, these queries avoid an explicit join to XLA_TRANSACTION_ENTITIES and are the recommended access path for subledger accounting header reporting and integration extracts.