Results for “okl_termnt_interface_all”

28 results




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

Overview

OKL_TERMNT_INTERFACE_ALL is the termination interface table in the Oracle Lease and Finance Management (OKL) module. It serves as the staging and inbound integration surface through which contract or asset termination requests are imported into Oracle E-Business Suite. Rather than terminating contracts directly, external systems, feeder applications, or bulk data loads write termination request records into this table, where they are subsequently validated and processed by the ETRM termination workflow. The table is owned by the OKL schema and is present and valid in both Oracle EBS 12.1.1 and 12.2.2.

The documented physical schema for 12.2.2 defines 48 columns. The primary key OKL_TERMNT_INTERFACE_ALL_PK is defined on TRANSACTION_NUMBER, and a unique index OKL_TERMNT_INTERFACE_ALL_U1 also exists on TRANSACTION_NUMBER, meaning the transaction number acts as the natural business key for each inbound termination request. Based on the foreign key topology — a single parent reference out to OKL_TRX_QUOTES_ALL_B and a dependent child table (OKL_TERMNT_INTF_PTY) referencing back — the heuristic Data Vault classification is satellite-leaning. This suggests treating the table as a descriptive satellite attached to a quote/contract hub, with the transaction number serving as the degenerate business key rather than a true hub.

Key Information Stored

The table captures everything required to describe and track an inbound termination request. The most significant columns are:

Common Use Cases and Queries

Typical scenarios include bulk-loading termination requests via SQL*Loader or an external integration, validating that requests were imported successfully, monitoring processing status, and reconciling interface records against generated terminations. A representative query to find unprocessed requests is:

  • SELECT transaction_number, contract_number, asset_number, status, date_effective_from FROM okl_termnt_interface_all WHERE status IS NULL OR status = 'NEW' ORDER BY creation_date;
  • Joining to the quote table to confirm parent transaction context: SELECT ti.transaction_number, ti.contract_number, q.quote_number FROM okl_termnt_interface_all ti, okl_trx_quotes_all_b q WHERE ti.qte_id = q.id;
  • Auditing inbound source systems: SELECT orig_system, orig_system_reference, COUNT(*) FROM okl_termnt_interface_all GROUP BY orig_system, orig_system_reference;

Reporting commonly focuses on termination volumes by contract, asset, reason code, or effective period, and on the timeliness of processing by comparing DATE_EFFECTIVE_FROM with DATE_PROCESSED.

Related Objects

  • OKL_TRX_QUOTES_ALL_B — Referenced via QTE_ID; the parent quote/transaction record for the termination request.
  • OKL_TERMNT_INTF_PTY — Child table joined on TRANSACTION_NUMBER; holds party information associated with each termination interface record.
  • OKL_TERMNT_INTERFACE_ALL_PK / _U1 — Primary key constraint and unique index on TRANSACTION_NUMBER enforcing record uniqueness.
  • OKL_TERMNT_INTERFACE_ALL columns ATTRIBUTE1–ATTRIBUTE15 and the concurrent program columns (REQUEST_ID, PROGRAM_ID) — integrate with the standard EBS concurrent manager infrastructure.
  • OKL contracts and assets tables (referenced through CONTRACT_ID/ASSET_ID) — provide the operational entities to which each termination request ultimately applies.