Results for “tcn_id”

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

Overview

OKL_XLA_ENT_TCN_MAP_GT is an APPS-owned table within the Oracle Lease and Finance Management (OKL) product family. It functions as a global temporary-style mapping table that associates an Oracle Subledger Accounting (XLA) entity identifier with a Transaction Contract Number (TCN) identifier, providing the join bridge between lease contract upgrade transactions and the SLA entity assignments used during accounting event generation. In Oracle EBS 12.1.1 and 12.2.2, tables of this naming pattern (suffix _GT) are typically populated at runtime by concurrent processes and consumed within the same session for subledger accounting and upgrade processing logic in OKL.

The ETRM metadata classifies this object heuristically as standalone under the Data Vault model. Following that modeling suggestion, the table behaves as a lightweight link-style mapping rather than a true hub or satellite: it carries no descriptive attributes of its own beyond the two identifier columns, and its purpose is purely associative. It holds exactly two documented columns, confirming its role as a transient correlation structure rather than a master or transactional entity store.

Key Information Stored

The documented physical schema for 12.2.2 lists only two columns, both of which are identifier fields:

• TCN_ID — The transaction contract number identifier. The metadata confirms a foreign key from OKL_XLA_ENT_TCN_MAP_GT.TCN_ID to OKL_UPG_TRX_CONTRACTS_T, establishing this column as the business-key linkage to the contract upgrade transaction record.
• ENTITY_ID — The Subledger Accounting entity identifier. This value corresponds to the XLA entity used when creating accounting events and entries, allowing the lease transaction to be mapped to the correct accounting entity context.

Because only two columns are documented, no separate surrogate primary key column is exposed in the metadata; the (TCN_ID, ENTITY_ID) pair functions as the effective composite business key for the mapping. No unique index columns beyond this pair are documented in the supplied metadata. The absence of audit columns (creation date, created by, last updated by) reinforces the conclusion that the table is a transient working structure populated and purged by process logic rather than a persisted transactional table.

Common Use Cases and Queries

The primary use case is diagnostic: tracing how a lease contract upgrade transaction was assigned to an SLA entity during accounting generation. A typical query joins the mapping table to the upgrade contracts table:

• SELECT m.tcn_id, m.entity_id, c.* FROM okl_xla_ent_tcn_map_gt m, okl_upg_trx_contracts_t c WHERE m.tcn_id = c.tcn_id;
• Filtering by a specific entity to enumerate all upgrade transactions routed to that SLA entity: SELECT tcn_id FROM okl_xla_ent_tcn_map_gt WHERE entity_id = :entity_id;
• Reverse lookup to confirm the entity mapped to a known upgrade transaction: SELECT entity_id FROM okl_xla_ent_tcn_map_gt WHERE tcn_id = :tcn_id;

Reporting scenarios include reconciliation of lease upgrade transactions against generated subledger accounting events, and troubleshooting cases where an upgrade transaction failed to produce expected accounting because no entity mapping row was present. Because the table is transient in nature, queries are generally most meaningful while the originating concurrent program session is active or immediately following population.

Related Objects

• OKL_UPG_TRX_CONTRACTS_T — Referenced by the foreign key on TCN_ID; the primary source of contract upgrade transaction data.
• OKL_UPG_TRX_CONTRACTS — The non-temporary upgrade transaction table frequently joined for persisted staging data.
• XLA_EVENTS / XLA_AE_HEADERS — Subledger Accounting event and entry tables keyed by entity, used together with ENTITY_ID for accounting reconciliation.
• OKL_CONTRACTS_ALL / OKL_K_HEADERS — Lease master and header objects providing contract context for the transactions mapped here.
• OKL_UPG_* concurrent programs — The upgrade and SLA generation processes that populate and consume this table at runtime.