Results for “tcn_status_code”

14 results




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

Overview

OKL_IA_EXTRACT_HDR_V is an APPS-owned reporting view in the Oracle Leasing and Finance Management (OKL) module. It serves as the header extract object for the Investor Agreement event class, functioning as the inbound data feed for Oracle Subledger Accounting (SLA) and the ETRM Investor Agreement accounting program. In Oracle EBS 12.1.1 and 12.2.2, the view presents one row per accounting event generated against a transaction contract, combining the transaction record, its optional Investor Agreement extension attributes, and the corresponding SLA event header.

The view is not a transactional entry point. It is a read-only, denormalized projection used by the accounting extraction engine to build the header portion of the Investor Agreement extract file that is consumed by downstream GL and reporting processes. Its status is VALID in both releases, and the object name follows the standard OKL naming convention for extract views (OKL_IA_*_V).

The user's search term tcn_id maps to the TCN_ID column, which is the primary join key linking the view back to OKL_TRX_CONTRACTS_ALL. Because TCN_ID identifies the source transaction contract, it is the most frequently filtered and joined column when diagnosing extract failures or tracing a specific lease or loan transaction through the accounting pipeline.

Underlying Base Objects

The view is defined over three referenced base objects, all resolved through APPS synonyms:

  • OKL_TRX_CONTRACTS_ALL (alias TCN) — the transaction contract table holding the contract number, amount, currency, status, and organization. Restricted by ORG_ID through multi-org views.
  • OKL_TRX_EXTENSION_B (alias TEH) — the Investor Agreement extension table storing agreement number, effective date, currency, syndication code, pool number, and agreement status carried on the transaction contract.
  • XLA_EVENTS_GT (alias XE) — the SLA events global temporary table populated by the subledger accounting program for the current run.

The join conditions are: TCN.ID = TEH.SOURCE_ID(+) with TEH.SOURCE_TABLE(+) = 'OKL_TRX_CONTRACTS', and XE.APPLICATION_ID = 540 (the OKL application identifier) with XE.SOURCE_ID_INT_1 = TCN.ID. The outer join on the extension table means a transaction contract without Investor Agreement attributes still appears in the extract, with null TEH_* columns.

Key Columns

Common Use Cases and Queries

Typical uses include reconciling Investor Agreement events to SLA, isolating transactions missing agreement attributes, and auditing currency conversion on extracted headers. A query filtering on the searched term:

  • SELECT tcn_id, event_id, tcn_trx_number, tcn_type, gl_date FROM okl_ia_extract_hdr_v WHERE tcn_id = :p_tcn_id;
  • SELECT event_id, tcn_id, teh_inv_agrmnt_number, tcn_ia_amount, gl_date FROM okl_ia_extract_hdr_v WHERE org_id = :p_org_id AND gl_date BETWEEN :p_start AND :p_end ORDER BY tcn_id;
  • SELECT tcn_id, tcn_trx_number FROM okl_ia_extract_hdr_v WHERE teh_inv_agrmnt_number IS NULL AND tcn_accounting_reversal_flag = 'N';

Note that XLA_EVENTS_GT is a global temporary table, so rows are visible only within the session that populated them. Queries outside the accounting program session may return the contract rows but exclude event-based columns.