Results for “okl_trx_contracts”

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

Overview

OKL_TRX_CONTRACTS is the lease transactions header table within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It stores the top-level record for every lease contract processed through the OKL transaction lifecycle, functioning as the anchor point that ties together pricing attributes, contractual terms, product definitions, provision details, accounting entries, and downstream billing or invoice activity. In practice, it is the parent header row over which contract lines, AR adjustments, and AP invoices are organized.

The metadata's heuristic Data Vault classification flags this table as satellite-leaning. From a modeling perspective, this is a suggested descriptor rather than a strict rule: the table carries a surrogate primary key (OKL_TRX_CONTRACTS_PK on ID) and a dense set of descriptive and referential attributes that behave like a satellite surrounding a contract business key. A harsher reading is possible — because TCN_ID is referenced by dependent transactions (AR adjustments, AP invoices, contract lines), the table also behaves like a hub for those children. Analysts designing an integration or warehouse model should treat it as the authoritative transaction header while remaining aware that the FK topology is only partially normalized in the source system.

Note that the ETRM metadata records this table as not implemented in the database for the surveyed environment. This generally indicates the module was not installed or the object was absent from that specific instance; the structure and relationships remain valid for environments where OKL is deployed.

Key Information Stored

The table is keyed by the surrogate primary key ID (OKL_TRX_CONTRACTS_PK). The most significant descriptive and relational columns documented in the metadata are:

• ID — surrogate primary key; the sole documented unique identifier for the header row. No separate business-key unique index is documented in the provided metadata, so consumers should treat ID as the join key and rely on foreign keys for classification rather than assuming a natural contract number exists in this object.
• TRY_ID — foreign key to OKL_TRX_TYPES_B; identifies the transaction type (for example, lease origination, renewal, or termination) and drives downstream processing rules.
• PDT_ID — foreign key to OKL_PRODUCTS; the lease product under which the contract was written, carrying associated pricing and accounting configuration.
• QTE_ID — foreign key to OKL_TRX_QUOTES_B; links the contract back to the originating quote when the transaction was converted from quotation.
• PVN_ID — foreign key to OKL_PROVISIONS; associates provisioning rules applied to the contract.
• AES_ID — foreign key to OKL_AE_TMPT_SETS; references the accounting entry template set used to generate journal entries.
• KHR_ID, KHR_ID_NEW, and KHR_ID_OLD — three foreign keys into OKL_K_HEADERS, representing current, replacement, and prior header versions. These support amendment and versioning scenarios where a contract is rebooked or superseded.

Together these columns establish the contract's type, commercial origin, and accounting context, while the three KHR_ID variants provide the version lineage that OKL uses during contract modification.

Common Use Cases and Queries

The most frequent requirement is retrieving contract headers by type, product, or originating quote. A representative pattern joins the header to the transaction type and product base tables:

• Contract population reporting: count or list contracts grouped by TRY_ID to measure origination versus renewal volume.
• Product analysis: aggregate contracts by PDT_ID to compare product mix and pricing performance.
• Quote-to-contract conversion tracking: filter on non-null QTE_ID to trace which quotes closed and which did not.
• Version reconciliation: compare KHR_ID with KHR_ID_NEW and KHR_ID_OLD to detect amended or superseded contracts.
• Child transaction rollup: join to OKL_TXL_CNTRCT_LNS, OKL_TRX_AR_ADJSTS_B, and OKL_TRX_AP_INVOICES_B on TCN_ID to reconcile billed lines against adjustments and invoices.

A typical query shape is SELECT t.ID, t.TRY_ID, t.PDT_ID, t.QTE_ID FROM OKL_TRX_CONTRACTS t WHERE t.TRY_ID = :trx_type_id, extended with joins to OKL_TRX_TYPES_B and OKL_PRODUCTS for descriptive names. Because ID is the only documented unique key, all joins should be driven from that column.

Related Objects

• OKL_TRX_TYPES_B — joined via TRY_ID; transaction type definition.
• OKL_PRODUCTS — joined via PDT_ID; lease product definition.
• OKL_TRX_QUOTES_B — joined via QTE_ID; source quote records.
• OKL_K_HEADERS — joined three ways via KHR_ID, KHR_ID_NEW, and KHR_ID_OLD; contract header versions.
• OKL_PROVISIONS — joined via PVN_ID; provision configuration.
• OKL_AE_TMPT_SETS — joined via AES_ID; accounting entry template sets.
• OKL_TXL_CNTRCT_LNS — references this table via TCN_ID; contract lines.
• OKL_TRX_AR_ADJSTS_B — references this table via TCN_ID; receivable adjustments.
• OKL_TRX_AP_INVOICES_B — references this table via TCN_ID; payable invoices.

These relationships confirm OKL_TRX_CONTRACTS as the central header for lease transaction processing, providing the TCN_ID anchor consumed by lines, adjustments, and invoices across the OKL module.