Results for “okl_bpd_inv_formats_uv”

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

Overview

The view OKL_BPD_INV_FORMATS_UV is a user-facing (UV) database view within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, appearing in releases 12.1.1 and 12.2.2. It exposes configuration metadata for invoice formats used by the leasing and financing engine, allowing reporting tools, concurrent programs, and integration interfaces to retrieve the definition of each invoice format without querying the underlying base object directly. The view is defined as a projection over OKL_INVOICE_FORMATS_V, meaning it acts as a thin repackaging layer that presents a curated set of columns for external consumption. As documented in the ETRM metadata, the object is identified as "Not implemented in this database," indicating that in the documented environment the view was not deployed; nevertheless its definition is catalogued as part of the OKL schema reference.

Underlying Base Objects

The documented view text is:

• SELECT ID, NAME, DESCRIPTION, CONTRACT_LEVEL_YN, START_DATE, END_DATE, ILT_ID FROM OKL_INVOICE_FORMATS_V

Accordingly, the single referenced base object is OKL_INVOICE_FORMATS_V, itself a view over the invoice format table (typically OKL_INVOICE_FORMATS_B / OKL_INVOICE_FORMATS_TL for translation-enabled name and description columns). The ETRM metadata lists no additional referenced base objects for OKL_BPD_INV_FORMATS_UV, and the owner is not documented. Because the "_UV" suffix conventionally denotes a user view, the object is expected to be exposed through grants to application users or reporting schemas. The absence of a documented WHERE clause in the extracted view text implies no filtering is applied at this level; date-effectivity logic is handled within the underlying OKL_INVOICE_FORMATS_V.

Key Columns

• ID — Primary identifier of the invoice format record; used as a foreign key by lease and invoice transaction tables.
• NAME — The invoice format name presented to users, sourced from the translation layer.
• DESCRIPTION — Free-text description of the format's purpose or layout.
• CONTRACT_LEVEL_YN — A flag indicating whether the invoice format operates at the contract level (Y) or at a lower grouping such as the line or asset level (N). This is the column most commonly targeted by ad hoc searches.
• START_DATE and END_DATE — Effective dating that determines the period during which the format is valid.
• ILT_ID — Identifier linking the format to the associated invoice line type or related leasing configuration entity.

Common Use Cases and Queries

Typical usage includes validating which invoice formats are active, driving conditional logic during invoice generation, and joining format definitions to lease contracts for reporting. A frequent scenario is identifying all contract-level formats currently in effect:

• SELECT id, name, contract_level_yn, start_date, end_date FROM okl_bpd_inv_formats_uv WHERE contract_level_yn = 'Y' AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1);
• SELECT id, name, ilt_id FROM okl_bpd_inv_formats_uv ORDER BY name;

Because CONTRACT_LEVEL_YN is exposed directly, the view is well suited to filters that separate contract-level billing logic from line-level logic. Before deploying dependent reports, administrators should confirm the view exists in the target instance, as the ETRM metadata records it as not implemented in the documented database.