Results for “price_list_id1”

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

Overview

The view OKL_BPD_CNTR_PRICE_LIST_UV is an APPS-owned database object within the Oracle E-Business Suite Leasing and Finance Management module (OKL). It is a reporting and integration construct rather than a transactional entity, and its name follows the OKL convention in which the _UV suffix denotes a user view designed for query and display purposes within the Business Process Designer (BPD) and related contingent-rental pricing flows.

The view exposes the relationship between a contract rule, the usage item associated with that rule, and the price list attached to the rule. In practical terms, it answers the question: for a given contract line, which usage (measured item) is linked to which price list, and what minimum and default quantities govern that association? The view is read-only and joins data across the rules engine, the system items definitions, and the price list headers, presenting a flattened, denormalized result set suitable for reporting, validation, and downstream integration. This makes it valuable when users need to audit pricing setup across leasing contracts without navigating the underlying normalization of the OKC rules tables.

Underlying Base Objects

The view is defined over four documented base objects, combined through inner joins:

• OKC_RULES_B (SYNONYM) — Supplies the rule rows, aliased RUL. It contributes RULE_INFORMATION1 (minimum quantity), RULE_INFORMATION2 (default quantity), DNZ_CHR_ID (the contract header identifier), RGP_ID, and the OBJECT1/OBJECT2 identifier pairs used to bridge to usage and price list.
• OKC_RULE_GROUPS_B (SYNONYM) — Aliased RG, it provides rule-group context and the RGD_CODE value. The join requires RGD_CODE = 'LAUSBB' and RULE_INFORMATION_CATEGORY = 'LAUSBB', restricting results to the leasing usage/pricing rule category.
• OKX_SYSTEM_ITEMS_V (VIEW) — Aliased OKX_USAGE, it supplies the usage item, filtered by USAGE_ITEM_FLAG = 'Y'. It provides the usage name, description, and organization identifier.
• OKX_LIST_HEADERS_V (VIEW) — Aliased OKX_PRICE, it supplies the price list, filtered by LIST_TYPE_CODE = 'PRL' (price list).

The joins link OKX_USAGE.ID1 = RUL.OBJECT1_ID1 and TO_CHAR(OKX_USAGE.ID2) = RUL.OBJECT1_ID2, and correspondingly OKX_PRICE.ID1 = RUL.OBJECT2_ID1 and OKX_PRICE.ID2 = RUL.OBJECT2_ID2, with RUL.RGP_ID = RG.ID tying the rule to its group.

Key Columns

• PRICE_LIST_ID1 — Identifier of the price list header (OKX_PRICE.ID1).
• USAGE_NAME — The name of the usage/system item linked to the rule; this is the column most commonly searched, as it identifies the measured usage that drives pricing.
• USAGE_DESCRIPTION — Descriptive text for the usage item.
• PRICE_NAME / PRICE_DESCRIPTION — Name and description of the associated price list.
• MINIMUM_QUANTITY — Derived from RUL.RULE_INFORMATION1; the contractual minimum quantity.
• DEFAULT_QUANTITY — Derived from RUL.RULE_INFORMATION2; the default quantity applied to the rule.
• CHR_ID — Contract header identifier (RUL.DNZ_CHR_ID).
• LINE_ID — Rule group identifier (RG.CLE_ID) representing the line context.
• USAGE_ORGANIZATION_ID — Organization owning the usage item.

Common Use Cases and Queries

Typical scenarios include auditing which price lists are attached to usage items across contracts, validating minimum/default quantity configuration, and feeding pricing data into custom reports or interfaces.

To locate all price lists associated with a specific usage by name:

• SELECT usage_name, price_name, minimum_quantity, default_quantity FROM apps.okl_bpd_cntr_price_list_uv WHERE usage_name = :usage_name;

To retrieve all pricing rules for a given contract header:

• SELECT usage_name, price_name, chr_id, line_id FROM apps.okl_bpd_cntr_price_list_uv WHERE chr_id = :chr_id;

To list distinct usages with their owning organization:

• SELECT DISTINCT usage_name, usage_organization_id FROM apps.okl_bpd_cntr_price_list_uv ORDER BY usage_name;

Because the view joins several public views and rule tables, queries should filter on indexed identifiers such as CHR_ID or PRICE_LIST_ID1 where possible to limit the scan volume in production environments.