Search Results posting_entity

Overview

AR.AR_XLA_LINES_EXTRACT is a global temporary table in the Oracle E-Business Suite Receivables (AR) schema. It is registered in FND Design Data as AR.AR_XLA_LINES_EXTRACT and holds status VALID in both 12.1.1 and 12.2.2. The table functions as a staging and extraction structure used by the Subledger Accounting (XLA) engine when assembling accounting event data for Receivables transactions before that data is transformed into journal entry lines and transferred to the general ledger interface. It is the mechanism by which the Create Accounting process materializes the transactional, customer, tax, and distribution attributes required to derive accounting rules and produce final subledger journal entries.

Because it is defined as a global temporary table with a data duration of SYS$TRANSACTION, rows are visible only to the session that inserted them and are purged on transaction commit or rollback. Multiple concurrent accounting runs therefore do not collide on this object. Physical storage uses PCT Free 10 and PCT Used 40. From a Data Vault modeling perspective the table is best characterized as a satellite-style structure attached to accounting events, since it carries descriptive and derived attributes keyed to event identifiers rather than serving as a standalone hub; the metadata classifies it heuristically as standalone, so this should be treated as a modeling suggestion only.

Key Information Stored

The table contains 110 documented columns; the most operationally significant are listed below.

• EVENT_ID (NUMBER 15) — the subledger accounting event that owns the extracted line set. It forms the leading column of indexes AR_XLA_LINES_EXTRACT_N1 and AR_XLA_LINES_EXTRACT_N3.
• LINE_NUMBER (NUMBER 15) — the sequence of the line within the event; combined with EVENT_ID it identifies a row within an extraction run.
• LINE_ID (NUMBER 15) — the source transaction line identifier, indexed by AR_XLA_LINES_EXTRACT_N2.
• LEVEL_FLAG — indicates the accounting level at which the line is being extracted (for example header versus line versus distribution level). It appears in index N1 and in N3, confirming that it is a frequently filtered attribute in extraction and reporting queries.
• FROM_TO_FLAG — distinguishes the "from" side from the "to" side of reversing or transfer entries; also indexed in N1 and N3.
• POSTING_ENTITY (VARCHAR2 20) — defines the balance type context for the accounting, such as Receivables or Revenue.
• EVENT_CLASS_CODE — classifies the accounting event, indexed in N1.
• ACCTD_AMOUNT and TAXABLE_ACCTD_AMOUNT — the accounted amounts used to build journal lines.
• CUSTOMER_TRX_ID, CUSTOMER_TRX_LINE_ID, CASH_RECEIPT_ID — transaction and receipt context columns; CUSTOMER_TRX_ID is indexed in N3.
• MFAR_ADDITIONAL_ENTRY — multi-funding additional entry indicator, indexed in N3.
• SELECT_FLAG and ORIGIN_EXTRACT_TABLE — control columns indicating row selection and the source of extraction.

No single-column unique index is documented; uniqueness is enforced through the natural combination of EVENT_ID, LINE_NUMBER, LEVEL_FLAG, and related qualifiers rather than a surrogate primary key. The documented foreign keys provide business-key linkage to CUST_TRX_LINE_SALESREPS_ALL, AR_RECEIPT_METHODS, AR_RECEIVABLES_TRX_ALL, and ZX_LINES.

Common Use Cases and Queries

The primary use case is diagnostic: when Create Accounting produces unexpected entries, developers query this table mid-run to inspect the staged data. Because of the SYS$TRANSACTION duration, such queries must execute in the same session that populated the table.

• Inspecting extraction output for a specific event: SELECT event_id, line_number, level_flag, from_to_flag, posting_entity, acctd_amount FROM ar.ar_xla_lines_extract WHERE event_id = :event_id ORDER BY line_number;
• Confirming how many header-level versus line-level rows were extracted: aggregate by LEVEL_FLAG and EVENT_CLASS_CODE.
• Reconciling tax amounts against ZX_LINES by joining on TAX_LINE_ID.
• Tracing a transaction's accounting by joining CUSTOMER_TRX_ID to RA_CUSTOMER_TRX_ALL and GROUPing by POSTING_ENTITY.
• Investigating receipt-related entries through CASH_RECEIPT_ID, RECEIVABLE_APPLICATION_ID, and RECEIPT_METHOD_ID.

The composite indexes N1 and N3 make level_flag-based filtering efficient, which is why this column is frequently the user's search term in troubleshooting scenarios.

Related Objects

• ZX_LINES — joined via TAX_LINE_ID for tax line detail.
• AR_RECEIVABLES_TRX_ALL — referenced through RECEIVABLES_TRX_ID for receivables transaction types.
• AR_RECEIPT_METHODS — referenced through RECEIPT_METHOD_ID for receipt method attributes.
• RA_CUST_TRX_LINE_SALESREPS_ALL — referenced through CUST_TRX_LINE_SALESREP_ID for salesperson credit.
• RA_CUSTOMER_TRX_ALL / RA_CUSTOMER_TRX_LINES_ALL — transaction header and line context via CUSTOMER_TRX_ID and CUSTOMER_TRX_LINE_ID.
• AR_CASH_RECEIPTS_ALL — receipt context via CASH_RECEIPT_ID.
• XLA_EVENTS / XLA_AE_LINES — upstream event definition and downstream journal lines that consume this extracted data.
• AR_XLA_LINES_EXTRACT_N1 / N2 / N3 — supporting nonunique indexes on EVENT_ID, LINE_NUMBER, LINE_ID, LEVEL_FLAG, FROM_TO_FLAG, EVENT_CLASS_CODE, and related columns.