Search Results okc_k_lines_all_b

Overview

APPS.OKL_LA_PASSTHROUGH_HDR_UV is a supplementary view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 release streams, owned by the APPS schema and registered under the FND Design Data application OKL. It belongs to the Oracle Lease and Finance Management (OLFM/ETRM) module and exposes passthrough payment header information used by the lease and finance contracts subsystem. The view is classified as a "supplementary view used to simplify forms coding," which means it exists primarily to present a denormalized, form-friendly result set to the Oracle Forms user interface rather than to serve as a stable, supported integration or reporting interface. Oracle explicitly warns that querying or altering data through this view is not recommended, and that its structure may change dramatically in subsequent minor or major releases.

Functionally, the view consolidates passthrough payment header attributes — payout basis, passthrough term, effective dates, and stream type references — into a single logical record so the forms layer does not need to join the base transaction tables directly. In this sense it acts as a presentation-layer abstraction rather than a canonical data source.

Underlying Base Objects

Per documented ETRM 12.2.2 metadata, OKL_LA_PASSTHROUGH_HDR_UV references the following base objects:

• OKL_PARTY_PAYMENT_HDR (accessed via synonym) — the primary base table carrying passthrough payment header records.
• OKL_STRM_TYPE_TL (accessed via synonym) — the stream type translation table, supplying the translated stream type NAME.
• FND_LOOKUPS (view) — supplies decoded values such as the payout basis name.
• FND_GLOBAL (package) — supplies session and environment context such as the current user, responsibility, and language, used to filter translated and lookup values.

The view is not referenced by any other database object, confirming its role as a terminal, form-supporting construct. Notably, the CLE_ID column documents a foreign key relationship to table OKC_K_LINES_ALL_B, and DNZ_CHR_ID documents a foreign key to OKC_K_HEADERS_ALL_B — both core Contracts (OKC) tables. This illustrates the cross-module linkage between OLFM passthrough records and the underlying contract line and header structures, while remaining outside the view's direct dependency list.

Key Columns

• ID (NUMBER) — unique identifier for the passthrough payment header.
• CLE_ID (NUMBER) — foreign key to OKC_K_LINES_ALL_B, linking the record to a contract line.
• DNZ_CHR_ID (NUMBER) — foreign key to OKC_K_HEADERS_ALL_B, linking the record to a contract header.
• PASSTHRU_START_DATE (DATE) — passthrough start date.
• PAYOUT_BASIS (VARCHAR2 30) — payout basis code (Billing, Due Date, Partial Receipt, Full Receipt, Formula).
• PAYOUT_BASIS_NAME (VARCHAR2 80) — decoded payout basis name.
• EFFECTIVE_FROM / EFFECTIVE_TO (DATE) — start and end dates for record validity.
• PASSTHRU_TERM (VARCHAR2 10) — passthrough term type (base and evergreen).
• PAYOUT_BASIS_FORMULA (VARCHAR2 150) — formula text when payout basis is "Formula".
• PASSTHRU_STREAM_TYPE_ID (NUMBER) and NAME (VARCHAR2 150) — stream type identifier and translated stream type name.

Common Use Cases and Queries

Typical usage is diagnostic or investigative rather than production reporting. Developers tracing passthrough payment configuration for a given contract line may join CLE_ID to OKC_K_LINES_ALL_B — the object the user searched for — to correlate passthrough headers with contract lines:

• Querying all passthrough headers by payout basis to understand formula-driven versus receipt-driven setups.
• Relating CLE_ID to OKC_K_LINES_ALL_B and DNZ_CHR_ID to OKC_K_HEADERS_ALL_B to reconstruct contract context.
• Checking effective date ranges for overlapping or obsolete passthrough configurations.

Because Oracle does not recommend querying this view directly, custom integrations should target the underlying base table OKL_PARTY_PAYMENT_HDR instead.