Results for “usage_description”

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

Overview

OKL_UBB_USAGE_ITEMS_UV is a user interface view owned by the APPS schema in Oracle Lease and Finance Management (OKL). Its documented purpose is to present the data required by the usage line definition page, one of the building blocks of usage-based billing (UBB) in Oracle E-Business Suite Release 12.1.1 and 12.2.2. The view consolidates usage item definitions, price list references, rule-driven quantity defaults, and contract line context into a single denormalized row per usage rule, allowing the UBB setup and contract authoring pages to render usage lines without navigating the underlying normalized OKC and OKX tables directly.

Because the object is a view rather than a table, it carries no stored data of its own. It is a query-time projection over lease contract rules, rule groups, contract lines, and the OKX usage/system item and price list views. This makes it equally useful for reporting and integration: extract programs, custom concurrent requests, and downstream interfaces can select from the view to retrieve usage line definitions together with their associated pricing and quantity defaults.

Underlying Base Objects

The documented metadata identifies the following referenced objects, resolved through APPS synonyms and views:

• OKC_RULES_B (synonym) — supplies the usage rule rows, aliased as RUL, including the rule identifiers RGP_ID and ID, plus the rule information attributes that carry minimum and default quantities.
• OKC_RULE_GROUPS_B (synonym) — aliased as RG, links each rule group to a contract line (CLE_ID, DNZ_CHR_ID) and filters on rule group code LAUSBB.
• OKC_K_LINES_B (synonym) — aliased as CLE, provides the contract line context and status, restricted to lines that are not abandoned.
• OKC_LINE_STYLES_B (synonym) — aliased as LSE, restricts the result set to lines whose style code is USAGE.
• OKX_SYSTEM_ITEMS_V (view) — aliased as OKX_USAGE, supplies the usage item name and description, filtered by USAGE_ITEM_FLAG = 'Y'.
• OKX_LIST_HEADERS_V (view) — aliased as OKX_PRICE, supplies the price list name and description, filtered to list type code PRL (price list).

Joins are driven by the rule information category LAUSBB and by object identifier pairs (OBJECT1_ID1/ID2 for the usage item, OBJECT2_ID1/ID2 for the price list), which is the standard OKC rule linking pattern.

Key Columns

• USAGE_NAME / USAGE_DESCRIPTION — name and description of the usage item, sourced from OKX_SYSTEM_ITEMS_V.
• PRICE_NAME / PRICE_DESCRIPTION — name and description of the associated price list. PRICE_DESCRIPTION is the column most commonly targeted when users search for "price_description" in this view, since it exposes the descriptive text of the price list attached to a usage rule.
• MINIMUM_QUANTITY / DEFAULT_QUANTITY — derived from RULE_INFORMATION1 and RULE_INFORMATION2 on the rule, expressing the minimum billable quantity and the default quantity for the usage line.
• CHR_ID / LINE_ID — the contract identifier and contract line identifier that anchor the usage definition.
• USAGE_ORGANIZATION_ID — the organization owning the usage item.
• RGP_ID / RULE_ID — identifiers of the rule group and the usage rule, used as keys for drill-down navigation.

Common Use Cases and Queries

Typical scenarios include verifying which price list is attached to a usage line, auditing minimum and default quantity setup, and feeding usage billing data into custom reports. The following query returns usage lines with their price list descriptions for a given contract:

• SELECT usage_name, usage_description, price_name, price_description, minimum_quantity, default_quantity FROM okl_ubb_usage_items_uv WHERE chr_id = :p_chr_id;
• SELECT line_id, usage_name, price_description FROM okl_ubb_usage_items_uv WHERE price_name = :p_price_list;
• SELECT rule_id, rgp_id, usage_organization_id FROM okl_ubb_usage_items_uv WHERE usage_name LIKE :p_pattern;

Because the view applies filters on rule category, line style, and line status internally, consumers do not need to replicate those predicates; results are limited to active usage lines tied to price lists.