Search Results tcn_type




Overview
Explore in AI Chat

Overview

APPS.OKL_CS_TRX_CONTRACTS_UV is a reporting view within the Oracle E-Business Suite ETRM (Enterprise Contracts and Transactions) module, specifically belonging to the Oracle Lease and Finance Management (OKL) schema family. The view consolidates transaction-level contract data drawn from OKL_TRX_CONTRACTS and enriches it with human-readable lookup descriptions from FND_LOOKUPS. Its purpose is to present a filtered, denormalized list of service-related transactions for reporting, inquiry, and integration consumption.

The defining characteristic of this view is its hard-coded filter on the TCN_TYPE column, restricting output to records where TCN_TYPE equals 'SER'. This filter makes the view purpose-specific: it exposes only those transaction contract rows whose transaction category is classified as service. The view is denoted by the suffix _UV, indicating a "user view" intended primarily for end-user queries, Oracle Reports, and downstream SQL rather than for transactional DML. It surfaces both the header contract identifier and the associated service contract identifier, enabling correlation between a transaction and its parent contract structure.

Underlying Base Objects

The view is defined over the following documented base objects:

  • OKL_TRX_CONTRACTS (referenced via SYNONYM) — the primary source of transaction records. It supplies header contract ID (KHR_ID), transaction date, transaction status code (TSU_CODE), transaction number, service contract ID (CHR_ID), description, transaction ID, and TRY_ID.
  • FND_LOOKUPS (VIEW) — joined to translate the TSU_CODE status value into its descriptive MEANING. The join is qualified by LOOKUP_TYPE = 'OKL_TRANSACTION_STATUS' and TRX.TSU_CODE = LOOKUP.LOOKUP_CODE.
  • FND_GLOBAL (PACKAGE) — referenced in the metadata as an underlying object, typically supplying session context such as application ID, user ID, or responsibility context used in Multi-Org or security predicate evaluation.

An inner join between OKL_TRX_CONTRACTS and FND_LOOKUPS ensures that only transactions with a valid, matching lookup code in the transaction status lookup type are returned. Results are ordered by transaction number in descending sequence.

Key Columns

  • HEADER_CONTRACT_ID — sourced from TRX.KHR_ID; identifies the header-level contract to which the transaction belongs.
  • TRANSACTION_DATE — sourced from TRX.DATE_TRANSACTION_OCCURRED; the date the transaction took effect.
  • TRANSACTION_TYPE_CODE — sourced from TRX.TSU_CODE; the raw status/type code on the transaction record.
  • TRANSACTION_TYPE_DESC — sourced from LOOKUP.MEANING; the decoded description corresponding to the status code.
  • TRANSACTION_NUMBER — sourced from TRX.TRX_NUMBER; the user-facing transaction identifier and the view's sort key.
  • SERVICE_CONTRACT_ID — sourced from TRX.CHR_ID; links the transaction to its service contract.
  • TRX_DESCRIPTION — free-text description of the transaction.
  • TRX_ID — the unique transaction identifier (TRX.ID).
  • TRY_ID — an additional transaction reference identifier carried from the base table.

Common Use Cases and Queries

Typical scenarios include contract service transaction reporting, inquiry screens driven by user search criteria, and integrations extracting service transaction feeds. The column commonly searched as "tcn_type" is not itself projected by this view; rather, it is the filter column used inside the view definition to restrict rows to service transactions. Analysts searching for TCN_TYPE should understand that the value 'SER' is already applied, and that the column is available in the base table OKL_TRX_CONTRACTS when more granular filtering is required.

  • Retrieve all service transactions for a given header contract: SELECT transaction_number, transaction_date, transaction_type_desc FROM apps.okl_cs_trx_contracts_uv WHERE header_contract_id = :p_khr_id;
  • List recent transactions by status description: SELECT transaction_number, service_contract_id, transaction_type_desc FROM apps.okl_cs_trx_contracts_uv WHERE transaction_type_desc = 'Active' ORDER BY transaction_date DESC;
  • Cross-reference a service contract to its transactions: SELECT trx_id, transaction_number, trx_description FROM apps.okl_cs_trx_contracts_uv WHERE service_contract_id = :p_chr_id;

Because the view applies an inner join to FND_LOOKUPS, queries will not return transactions lacking a valid OKL_TRANSACTION_STATUS lookup entry. For full population coverage, developers should query OKL_TRX_CONTRACTS directly.