Search Results termination_quote_number




Overview

APPS.OKL_SLA_TRX_INFO_V is a reporting view within the Oracle E-Business Suite (EBS) Lease and Finance Management (formerly Oracle Lease Management / OKL) module. It presents Sub-Ledger Accounting (SLA) related transaction information by joining lease transaction records with their originating contracts, products, lessee party details, customer accounts, and termination quote attributes. Its principal role is to provide a denormalized, human-readable projection of lease transaction data that combines accounting-relevant transaction identifiers with the descriptive context required for financial reporting, reconciliation, and downstream integration into the SLA engine.

The view is documented in ETRM for EBS 12.1.1 and 12.2.2 and is owned by the APPS schema, making it accessible to reporting tools, concurrent programs, and custom integrations running in the EBS environment. Because it exposes the lessee's party name and customer account alongside contract and transaction information, it is frequently used when the reported output must be attributable to a specific customer or party.

Underlying Base Objects

The view is defined over a set of base tables and supporting objects, joined to associate each transaction with its contract, product, lessee, and termination quote. The documented base objects are:

  • OKL_TRX_CONTRACTS_ALL (TCN) — the driving lease transaction table, supplying transaction number, currency, transaction date, and cancellation date.
  • OKC_K_HEADERS_ALL_B (CHR) — the contract header, supplying contract number and the SCS code that determines whether the record is treated as a lease or an investor contract.
  • OKL_K_HEADERS (KHR) — lease header extension, supplying securitization type and related attributes.
  • OKL_PRODUCTS (PDT) — the lease product definition, supplying the product name.
  • OKC_K_PARTY_ROLES_B (CUST_PARTY_ROLES) — party roles on the contract, restricting the join to the LESSEE role.
  • HZ_PARTIES (CUST_PARTY) — the trading community party record, supplying the party name where party type is PERSON or ORGANIZATION.
  • HZ_CUST_ACCOUNTS (CUST_ACCOUNTS) — the customer account, supplying the account number.
  • OKL_TRX_QUOTES_ALL_B (TERM) — the termination quote, supplying quote number and quote type code.
  • FND_LOOKUPS (SECLKUP, TQLKUP) — lookup views that translate securitization and quote type codes into their descriptive meaning.
  • FND_GLOBAL (PACKAGE) — referenced by the application's session context for security and environment values.

Key Columns

Note that the view text also includes a second DECODE on CHR.SCS_CODE for 'INVESTOR'; the full expression is truncated in the supplied metadata, but the pattern mirrors the CONTRACT_NUMBER column, returning the contract number only for investor contracts.

Common Use Cases and Queries

Because the view surfaces the lessee's party name and account, a common pattern is to filter or report by customer. A typical query joining this view to locate transactions for a specific customer is:

  • SELECT id, contract_number, customer_name, customer_account, transaction_number, transaction_date FROM apps.okl_sla_trx_info_v WHERE customer_account = :customer_account;
  • SELECT customer_name, transaction_number, termination_quote_number FROM apps.okl_sla_trx_info_v WHERE termination_quote_number IS NOT NULL;
  • SELECT investor_agreement_type, COUNT(*) FROM apps.okl_sla_trx_info_v GROUP BY investor_agreement_type;

The view supports reconciliation of lease transactions to accounting events, aggregation of transaction volumes by product or investor agreement type, and extraction feeds into external reporting or accounting sub-ledger processes. Filtering on CUSTOMER_NAME or CUSTOMER_ACCOUNT addresses the frequent requirement to isolate transactions belonging to a specific lessee.