Search Results okx_licprod

Overview

APPS.OKX_PRODUCT_LINES_V is a reporting view in the Oracle E-Business Suite Order Management and Oracle Contracts (OKC/OKX) schema. It exposes the product, license, and item line information associated with contract and service line records. In EBS 12.1.1 and 12.2.2 the view serves as a denormalized read-only projection that joins contract line headers, multilingual line translations, line styles, contract item associations, and the system items view. Its principal role is to support reporting and integration scenarios in which product lines tied to a licensing or service contract must be presented with descriptive text and item attributes rather than raw identifier keys.

Underlying Base Objects

The ETRM metadata documents the view as owned by APPS and defined over five referenced objects: OKC_K_ITEMS, OKC_K_LINES_B, OKC_K_LINES_TL, OKC_LINE_STYLES_B (all synonyms), and OKX_SYSTEM_ITEMS_V (a view). OKC_K_LINES_B supplies the contract line header row (ID, LINE_NUMBER, CHR_ID, DNZ_CHR_ID, LSE_ID, dates, and termination). OKC_K_LINES_TL supplies the translatable line attributes (NAME, ITEM_DESCRIPTION, COMMENTS) filtered to the session language using USERENV('LANG'). OKC_LINE_STYLES_B provides the line style classification through LTY_CODE, LSE_TYPE, and LSE_PARENT_ID. OKC_K_ITEMS links the contract line to a licensed product or item via the JTOT_OBJECT1_CODE value of 'OKX_LICPROD'. OKX_SYSTEM_ITEMS_V resolves the inventory item identifiers and item name.

Key Columns

• ID1 / ID2 — Surrogate identifiers for the line; ID2 is emitted as the literal '#'.
• NAME — Resolved as NVL(TL.NAME, SI.NAME), falling back to the system item name when no translated line name exists.
• DESCRIPTION / ITEM_DESCRIPTION / COMMENTS — Descriptive and free-text fields carried from the line and its translation.
• CHR_ID / DNZ_CHR_ID — Contract header and denormalized contract header references.
• LTY_CODE / LSE_TYPE / LSE_PARENT_ID — Line style code, style type, and parent style identifier driving line classification and hierarchy.
• DATE_TERMINATED / START_DATE_ACTIVE / END_DATE_ACTIVE — Effective dating for the line.
• STATUS — Derived as 'A' (active) or 'I' (inactive) by comparing SYSDATE against the start and end dates using nested DECODE(SIGN(...)) logic.
• INVENTORY_ITEM_ID / ORGANIZATION_ID — Item and organization keys; ORGANIZATION_ID is coerced to -99 when the source value is '#'.
• QUANTITY / UNIT_OF_MEASURE_CODE / ITEM_NAME / PRIMARY_UOM_CODE — Quantity and unit attributes from OKC_K_ITEMS and the resolved item name; PRIMARY_UOM_CODE is always NULL.

Common Use Cases and Queries

Typical usage retrieves active product lines for a given contract header, or lists items associated with a licensing contract for downstream integration. Because no sample queries were included in the excerpt, the following illustrative forms are consistent with the documented structure.

• List active lines for a contract: SELECT name, item_name, quantity, unit_of_measure_code FROM apps.okx_product_lines_v WHERE chr_id = :p_chr_id AND status = 'A';
• Report all licensed product lines with item detail: SELECT inventory_item_id, organization_id, item_name, quantity FROM apps.okx_product_lines_v ORDER BY item_name;
• Filter by line style classification: SELECT name, lty_code FROM apps.okx_product_lines_v WHERE lse_type = :p_type;
• Join to contract headers for a full contract-to-item report using the CHR_ID column.

Note that the STATUS column is computed at query time, so results reflect the current system date rather than a stored value.