Search Results qp_price_lists_v

Overview

XNC_ORD_IB_PRODUCT_RG_V is a reporting view within the XNC – Sales for Communications product family, a module that is identified as obsolete in Oracle EBS 12.1.1 and 12.2.2. The view is documented as being used to display Install Base details, presenting a denormalized, presentation-ready picture of customer product instances (install base records) joined to their associated order, pricing, item, and party information. Its role is to support reporting and integration scenarios where a flattened view of the install base—together with the ordering and price list context that created or last updated each instance—is required, without the reporting layer needing to assemble the underlying CSI, OE, QP, MTL, and HZ joins directly.

Because the object belongs to a module marked obsolete, it should be treated as a legacy artifact. The ETRM metadata also states "Not implemented in this database," meaning the view is not physically deployed in the database instance from which the documentation was generated. Any reference to this view in a 12.1.1 or 12.2.2 environment should therefore be validated against the actual schema before being relied upon.

Underlying Base Objects

The documented view text exposes the base objects over which the view is defined. They are:

• CSI_ITEM_INSTANCES A — the primary install base instance record, supplying the instance identifier, quantity, unit of measure, inventory item, organization, and active dates.
• CSI_INSTANCE_STATUSES B — provides the instance status description (exposed as CP_STATUS).
• MTL_SYSTEM_ITEMS_VL MSI — the item master, providing concatenated segments, description, BOM item type, service flags, and inventory item identifiers.
• QP_PRICE_LIST_LINES_V QLL and QP_PRICE_LISTS_V QLH — price list line and header information, supplying price list name, currency, and comments.
• OE_ORDER_LINES_ALL OOL — the originating order line, providing price list, unit selling price, line and header identifiers.
• HZ_CUST_ACCOUNTS HCA, CSI_I_PARTIES CIP, and CSI_IP_ACCOUNTS CIPA — party and account relationships linking the instance to the customer account and party.

The joins are largely key-based, with the item-to-organization linkage constrained through CS_STD.GET_ITEM_VALDN_ORGZN_ID. No base objects are separately documented in the 12.2.2 metadata beyond those visible in the view text itself.

Key Columns

• NODE_KEY — a concatenated key of instance, customer account, and party identifiers, useful as a graph or hierarchy node key.
• CUSTOMER_PRODUCT_ID — the install base instance identifier (A.INSTANCE_ID).
• UNIT_OF_MEASURE_CODE — the unit of measure associated with the instance quantity; this is the column most directly relevant to the search term "unit_of_measure_code."
• QUANTITY and EXTENDED_PRICE — quantity and the quantity-extended selling price.
• CONCATENATED_SEGMENTS and DESCRIPTION — item identification and description.
• PRICE_LIST_NAME, PRICE_LIST_ID, CURRENCY_CODE, COMMENTS — pricing context.
• CP_STATUS — instance status description.
• START_DATE_ACTIVE / END_DATE_ACTIVE — active date range for the instance.
• LINE_ID, HEADER_ID, INVENTORY_ITEM_ID, CUSTOMER_ID, ITEM_TYPE_CODE — keys and derived item classification (MDL, OPT, PLN, SRV, SVA, STD).

Common Use Cases and Queries

Typical uses include install base reporting, quantity-on-hand by customer, price list validation, and extract feeds to downstream systems. A representative query retrieving the unit of measure is:

SELECT customer_product_id, inventory_item_id, unit_of_measure_code, quantity, extended_price FROM xnc_ord_ib_product_rg_v WHERE org_id = :org_id;

Other practical patterns filter by price list or status:

• SELECT node_key, price_list_name, currency_code FROM xnc_ord_ib_product_rg_v WHERE price_list_id = :price_list_id;
• SELECT customer_id, description, cp_status FROM xnc_ord_ib_product_rg_v WHERE cp_status = 'Active';

Given the obsolete module designation and non-implementation, these queries should be validated against the live schema, and migration to supported install base views (for example, standard CSI reporting views) is advisable for new development.