Search Results max_ae_line_num

Overview

XLA.XLA_VALIDATION_LINES_GT is a global temporary table (GTT) within the Subledger Accounting (XLA) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as a transient staging area used by the Subledger Accounting validation engine during the creation and validation of accounting entries. Because the table is defined with a data duration of SYS$TRANSACTION, rows inserted by a given session are visible only to that session and are purged automatically at transaction commit or rollback. The table holds candidate journal lines together with the ledger, currency, party, and code combination context required to evaluate Subledger Accounting rules before they are committed to the final accounting tables.

Under the heuristic Data Vault classification supplied in the ETRM metadata, this object is modeled as standalone, meaning it does not participate in a traditional hub-link-satellite dependency chain. This reflects its nature as a work table rather than a persistent master or transactional entity; the classification is a modeling suggestion and should not be interpreted as a formal constraint on its use.

Key Information Stored

The table contains 72 documented columns. The most operationally significant are those that identify the accounting line and describe its validation context.

• AE_HEADER_ID and AE_LINE_NUM — identify the accounting entry header and line being validated; these form the basis of the non-unique index XLA_VALIDATION_LINES_GT_N2.
• EVENT_ID and ENTITY_ID — link the line back to the originating subledger event and entity.
• CODE_COMBINATION_ID — the accounting flexfield combination (CCID) being validated.
• CCID_COA_ID — the chart of accounts identifier associated with the CCID, the column most directly relevant to the user's search for "ccid_coa_id".
• LEDGER_ID, LEDGER_COA_ID, LEDGER_CURRENCY_CODE — ledger-level context against which the code combination must be validated.
• ACCOUNTED_DR, ACCOUNTED_CR, ENTERED_DR, ENTERED_CR — monetary amounts used to evaluate balancing.
• ERROR_FLAG — validation outcome indicator; indexed by XLA_VALIDATION_LINES_GT_N1 together with AE_HEADER_ID.
• CCID_SUMMARY_FLAG, CCID_ENABLED_FLAG, DETAIL_POSTING_ALLOWED_FLAG, BUDGET_CCID_VALID_FLAG, ACCESS_SET_SV_VALID_FLAG, BAL_SEG_VALID_STATUS, MGT_SEG_VALID_STATUS — detailed validation status flags derived from the code combination.
• SUSPENSE_CODE_COMBINATION_ID and SUBSTITUTED_CCID — support suspense and substitution processing.
• ENCUMBRANCE_TYPE_ID — the sole documented foreign key, referencing GL_ENCUMBRANCE_TYPES.

No unique index is documented; the two indexes present (N1 on ERROR_FLAG/AE_HEADER_ID and N2 on AE_HEADER_ID/AE_LINE_NUM) are both non-unique, reinforcing that the table is a transient, non-keyed work area rather than a persistent record store.

Common Use Cases and Queries

The primary use case is diagnostic: when Subledger Accounting validation fails or produces suspense entries, this table holds the intermediate state. A typical query retrieves failing lines for a given header.

• Selecting errored lines: SELECT ae_header_id, ae_line_num, code_combination_id, ccid_coa_id, error_flag FROM xla.xla_validation_lines_gt WHERE error_flag = 'Y';
• Inspecting CCID-to-accounts mapping: SELECT code_combination_id, ccid_coa_id, ledger_coa_id, ccid_enabled_flag FROM xla.xla_validation_lines_gt WHERE code_combination_id = :ccid;
• Reviewing balancing failures by comparing ACCOUNTED_DR and ACCOUNTED_CR grouped by AE_HEADER_ID.
• Auditing suspense or substitution activity via SUSPENSE_CODE_COMBINATION_ID and SUBSTITUTED_CCID.

Because the table is session-scoped and transaction-duration, queries must run within the same database session that populated it; otherwise no rows will be returned. Reporting use is therefore limited to interactive debugging rather than persistent reporting.

Related Objects

• GL_ENCUMBRANCE_TYPES — joined on ENCUMBRANCE_TYPE_ID, the only documented foreign key.
• XLA_AE_HEADERS and XLA_AE_LINES — persistent counterparts keyed by AE_HEADER_ID and AE_LINE_NUM.
• XLA_EVENTS — relates through EVENT_ID to the originating subledger event.
• XLA_TRANSACTION_ENTITIES — relates through ENTITY_ID.
• GL_CODE_COMBINATIONS — joined on CODE_COMBINATION_ID to resolve the CCID and its COA.
• GL_LEDGERS — joined on LEDGER_ID for ledger attributes and chart of accounts.