Results for “customer_category”

50+ results




Overview
Explore in AI Chat

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

Overview

QP_CUSTOMER_ITEMS_V is a PL/SQL view owned by the APPS schema within the QP (Advanced Pricing) module of Oracle E-Business Suite. It exposes customer item details and is referenced by the Pricing Agreements form, where it provides the cross-reference between a customer's own item numbering and the internal Oracle inventory item definition. In ETRM 12.1.1 and 12.2.2 the object carries a VALID status, confirming it remains an active, supported dictionary artifact in both releases.

From a reporting and integration standpoint, the view presents a denormalized, human-readable join between customer item cross-references, the inventory item master, and customer master data. Because it flattens these relationships into a single queryable structure, it is well suited to ad-hoc reporting, custom concurrent programs, and inbound/outbound interface logic where an external system must reconcile a customer-facing part number to an internal inventory item. The view is constrained by the QP_ORGANIZATION_ID profile option, so it is inherently single-organization in scope, returning only items belonging to the organization currently set in that profile.

Underlying Base Objects

The documented base objects underlying the view are:

  • MTL_CUSTOMER_ITEM_XREFS (referenced via a SYNONYM) — the cross-reference table linking a customer item to an internal inventory item. It supplies the join key between customer item and inventory item.
  • MTL_CUSTOMER_ITEMS_ALL_V (VIEW) — customer item header and address information, providing the customer item number, description, customer identifier, category, and address details.
  • MTL_SYSTEM_ITEMS_VL (VIEW) — the inventory item master view, supplying the inventory item identifier, concatenated segments, description, and organization identifier.
  • ARP_ADDR_PKG (PACKAGE) and QP_UTIL (PACKAGE) — supporting packages referenced in the definition (for example, address handling and pricing utilities).

The join logic links CITEMSV.CUSTOMER_ITEM_ID to CXREF.CUSTOMER_ITEM_ID and CXREF.INVENTORY_ITEM_ID to SITEMS.INVENTORY_ITEM_ID, restricting SITEMS.ORGANIZATION_ID to the value returned by FND_PROFILE.VALUE('QP_ORGANIZATION_ID').

Key Columns

  • CUSTOMER_ITEM_NUMBER / CUSTOMER_ITEM_ID — the customer's own item number and its surrogate identifier.
  • ITEM_DESCRIPTION — derived via NVL of the customer item description and the internal inventory item description.
  • INVENTORY_ITEM_ID / INVENTORY_ITEM — the internal inventory item identifier and its concatenated segment representation.
  • SOLD_TO_ORG_ID — the customer identifier associated with the cross-reference.
  • ORGANIZATION_ID — the inventory organization of the internal item.
  • CUSTOMER_CATEGORY — the customer category assigned to the item relationship.
  • ADDRESS_ID / ADDRESS — the customer address identifier and a SUBSTR-limited (400 character) concatenated address.

Common Use Cases and Queries

Typical scenarios include reconciling customer part numbers against the internal item master, populating pricing agreement line defaults, and validating cross-reference data during order import. A representative query follows:

SELECT customer_item, inventory_item, item_description, sold_to_org_id FROM apps.qp_customer_items_v WHERE inventory_item = :item_number;

Because the view is organization-scoped through QP_ORGANIZATION_ID, callers should confirm the profile is initialized for the current session before relying on results.