Results for “okl_contract_status”

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

Overview

OKL_AR_CASH_RECEIPTS_H_V is a public and self-service view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Lease and Finance Management (OKL) component of the Receivables (AR) product family. The view is documented in the E-Business Tax and Lease Management (ETRM) reference data with a status of VALID. Its stated purpose is to supply the data required by public and self-service views within the lease management module, which is reflected in its role as a lightweight projection that surfaces receipt-level identifiers, ledger context, language, and contract status for downstream reporting and integration consumers.

Rather than duplicating the full richness of the underlying cash receipts data model, this view exposes a narrow, purpose-built column set. It acts as a security and abstraction layer: public and self-service responsibilities can query a controlled set of columns without direct access to the base transaction tables, and joins between lease-specific receipt references and standard Receivables cash receipt headers are resolved within the view definition itself.

Underlying Base Objects

The view is defined over two referenced objects, both of which are themselves views in the APPS schema. The first is AR_CASH_RECEIPTS_H_V, the standard Receivables cash receipt header view, which provides the core receipt identity through RCT_CASH_RECEIPT_ID. The second is OKL_AR_RECEIPT_REF_VL, the lease-specific receipt reference view, which supplies the OKL_AR_RECEIPT_ID and the lease-oriented attributes.

The join condition is an equijoin on the receipt identifier: ACRH.RCT_CASH_RECEIPT_ID = OARR.OKL_AR_RECEIPT_ID. This correlates a standard Receivables receipt with its Lease Management reference record. Because both sides are views, the view ultimately resolves to the underlying AR_CASH_RECEIPTS and OKL receipt reference base tables, but the documented metadata lists only the two intermediate views as referenced base objects.

Key Columns

• EVENT_ID — Identifier for the receipt-related event carried through from the lease receipt reference; the primary linkage column in the exposed output.
• LEDGER_ID — The ledger associated with the receipt, establishing the accounting and reporting context for the transaction.
• LANGUAGE — Exposed under the alias OKL_LANGUAGE, providing the language context used for multilingual (VL) resolution of descriptive lease data.
• OKL_CONTRACT_STATUS — The status of the associated lease contract, enabling consumers to filter or report on receipts by contract state without joining to lease tables directly.

Common Use Cases and Queries

Typical usage centers on reporting and integration scenarios where only receipt identity, ledger, language, and contract status are needed. A minimal projection is:

• SELECT EVENT_ID, LEDGER_ID, LANGUAGE, OKL_CONTRACT_STATUS FROM APPS.OKL_AR_CASH_RECEIPTS_H_V;
• Filtering by ledger for a specific reporting entity: SELECT EVENT_ID, OKL_CONTRACT_STATUS FROM APPS.OKL_AR_CASH_RECEIPTS_H_V WHERE LEDGER_ID = :p_ledger_id;
• Isolating receipts tied to contracts in a given status: SELECT EVENT_ID FROM APPS.OKL_AR_CASH_RECEIPTS_H_V WHERE OKL_CONTRACT_STATUS = :p_status;

Because the view is intended for public and self-service access, it is commonly referenced from custom concurrent programs, BI Publisher data templates, and OAF-based self-service pages within the lease management flow. Queries should generally be constrained by LEDGER_ID or EVENT_ID to limit the joined row set, since the view performs an implicit join across the entire receipt and lease reference data sets on each access.