Results for “tsu_code”

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

Overview

The OKL_REVISIONS_UV view is an APPS-owned, VALID database object registered in the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment under the OKL — Lease and Finance Management product family. It is a user interface view (indicated by the _UV suffix) used by the rebook summary page within the Lease Management rebook flow. Its purpose is to expose the relationship between an original lease contract and the newly created (rebooked) contract, together with the revision processing status and the rebook reason.

Rebooking in Lease and Finance Management allows a contract to be revised and a new contract version to be generated while preserving an audit link to the prior version. The OKL_REVISIONS_UV view supplies the transactional context that drives that summary screen and supports downstream reporting on rebook activity. As a view rather than a table, no data is stored within it; all content is derived at runtime from its underlying lease header and transaction objects.

Underlying Base Objects

The documented metadata identifies three referenced base objects:

• OKL_K_HEADERS_FULL_V (VIEW) — Aliased twice within the view definition, once as OLDK (the original contract) and once as NEWK (the rebooked contract). This is the source of contract identifiers, contract numbers, and descriptive attributes.
• OKL_TRX_CONTRACTS_ALL (SYNONYM) — Aliased as TRX, this is the transactional linkage table that joins the old and new header records and carries the rebook reason code, the transaction status code, and the operating unit identifier.
• OKC_UTIL (PACKAGE) — A shared utility package referenced by the dependent objects; it supplies common contract-handling logic for the underlying header view rather than for OKL_REVISIONS_UV directly.

The join logic links each transaction record to its original contract via OLDK.ID = TRX.KHR_ID and to its rebooked successor via NEWK.ID = TRX.KHR_ID_NEW, producing a one-row-per-rebook pairing.

Key Columns

• NEW_CONTRACT_NUMBER — Contract number of the newly generated (rebooked) lease.
• OLD_CONTRACT_NUMBER — Contract number of the pre-revision lease.
• OLD_CONTRACT_DESC — Short description of the original contract, sourced from OLDK.SHORT_DESCRIPTION.
• NEW_CONTRACT_ID / OLD_CONTRACT_ID — Internal header identifiers for the new and original contracts respectively, useful for programmatic joins.
• RBR_CODE — The rebook reason code recorded on the transaction, indicating why the revision was performed.
• TSU_CODE — Transaction status code. Because the view filters on TRX.TSU_CODE <> 'PROCESSED', only revisions that are not yet fully processed are returned. This column is the field most frequently referenced in support searches.
• ORG_ID — Operating unit identifier, enforcing multi-org data segregation.

Common Use Cases and Queries

The view is used to populate the rebook summary page and to reconcile outstanding revisions. Because it excludes processed transactions and abandoned new contracts (NEWK.STS_CODE <> 'ABANDONED'), it returns only pending or in-flight rebook activity. A typical query is:

• SELECT new_contract_number, old_contract_number, rbr_code, tsu_code FROM okl_revisions_uv WHERE org_id = :p_org_id ORDER BY old_contract_number;
• Filtering by tsu_code to identify revisions awaiting processing, or by rbr_code to analyse rebook reasons across a portfolio.
• Joining on new_contract_id or old_contract_id to retrieve additional contract detail from the lease header tables.

All queries should be executed with the APPS schema context or an equivalent synonym-owning responsibility to resolve the underlying base objects correctly.