Results for “trx_hdr_id”

50+ results




Overview
Explore in AI Chat

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

Overview

OKL_UPG_TRX_CONTRACTS_T is a table owned by the OKL schema within the Oracle Lease and Finance Management module of Oracle E-Business Suite (available in 12.1.1 and 12.2.2). Its documented purpose is narrowly and explicitly scoped: it supports the upgrade of the identifier column of the OKL_TRX_CONTRACTS table, and it stores the old and new identifiers that result from that conversion. In other words, this is a transitional, upgrade-conversion table rather than a functionally transactional table used in day-to-day lease and finance operations.

From a Data Vault modeling perspective, the heuristic classification for this object is standalone — it holds no foreign key relationship to a parent hub and is not itself modeled as a link. A standalone classification of this kind suggests the table is best treated as a purely technical mapping/staging artifact rather than as a core hub, link, or satellite in a canonical Data Vault model. Because it exists to reconcile identifier changes during a one-time upgrade process, it is generally not part of the steady-state reporting model.

Key Information Stored

The documented physical schema contains two columns, both of which are significant:

  • TCN_ID — the primary key column, defined by the constraint OKL_UPG_TRX_CONTRACTS_T_PK. This is also the unique-index business-key candidate via OKL_UPG_TRX_CONTRACTS_T_U1 (TCN_ID). It identifies each upgrade record and is the join key referenced by downstream tables.
  • TRX_HDR_ID — the second documented column. In the context of upgrading the identifier column of OKL_TRX_CONTRACTS, this column is used to associate the conversion record with the relevant transaction header, allowing the old and new identifiers of the contract to be mapped during the upgrade.

Because the table stores only a two-column mapping, its value lies in the correspondence between the legacy (old) identifier and the current (new) identifier of a transaction contract, keyed through TCN_ID and linked to the transaction header via TRX_HDR_ID. The surrogate primary key (TCN_ID) is documented as distinct from the business-key candidate (the unique index OKL_UPG_TRX_CONTRACTS_T_U1 on the same TCN_ID column), so the two coincide in this object.

Common Use Cases and Queries

Use cases for OKL_UPG_TRX_CONTRACTS_T are typically diagnostic and audit-oriented during or after an upgrade:

  • Verifying upgrade completeness — confirming that every converted transaction contract identifier has a corresponding mapping row. A pattern such as SELECT TCN_ID, TRX_HDR_ID FROM OKL. OKL_UPG_TRX_CONTRACTS_T enumerates the stored mappings for review.
  • Reconciling old-to-new identifiers — joining the mapping rows back to the parent transaction contract to confirm the new identifier is populated correctly after conversion.
  • Cross-referencing dependent conversion tables — because several tables reference TCN_ID (see below), the mapping can be used to trace identifier changes across the accounting and XLA conversion staging tables produced during the same upgrade.
  • Post-upgrade validation and cleanup — after upgrade verification, DBAs may confirm the table can be retained or archived, since it performs no ongoing transactional function.

Related Objects

Several tables reference OKL_UPG_TRX_CONTRACTS_T through the TCN_ID column, indicating that it acts as a reference point for identifier mappings consumed by other upgrade/conversion objects:

  • OKL_XLA_ENT_TCN_MAP_GT — references TCN_ID, tying the mapping into XLA enterprise/accounting conversion staging.
  • OKL_TRX_REQUESTS — references TCN_ID, linking the mapping to transaction request records.
  • OKL_XLA_ACC_DATA_GT — references TCN_ID, used during XLA accounting data conversion.
  • OKL_XLA_EVE_HDR_TRX_MAP_GT — references TCN_ID, associating the mapping with event-header transaction mapping during conversion.

Together with its primary-key constraint (OKL_UPG_TRX_CONTRACTS_T_PK) and unique index (OKL_UPG_TRX_CONTRACTS_T_U1) on TCN_ID, these relationships confirm the table's role as a focused identifier-mapping component of the Oracle Lease and Finance Management upgrade process.