Search Results pricing_attribute10

Overview

The view APPS.CSI_CUSTOMER_PRODUCTS_ALL_V is a backward-compatibility wrapper within the CSI (Install Base) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified as a VIEW owned by the APPS schema and is reported with VALID status. Its ETRM description explicitly states "Backward Compatible: Customer Products (Table View)," meaning it exists to preserve the column interface and naming conventions that earlier releases exposed to customizations, reports, and integrations, while the physical storage and canonical model have migrated to the CSI_ITEM_INSTANCES table.

In practical terms, the view presents customer product instances—serialized or non-serialized units that a customer owns and that are tracked in the Install Base. It surfaces instance identity, item and revision information, serial and lot numbers, install location, status, pricing attributes, and originating order-line context. Because it is a compatibility layer rather than a base table, the view is read-oriented and is intended for reporting, extracts, and legacy interfaces that expect the historical "customer products" shape. For the search term returned_quantity, it is important to note that the documented view text does not include a returned quantity column; quantity-related information is exposed through CII.QUANTITY and shipment/original-order columns that can be used to derive return context versus the original sold quantity.

Underlying Base Objects

The documented ETRM metadata lists the following referenced objects, all resolved through APPS synonyms: CSICUMPI_PUB (a package), CSI_II_RELATIONSHIPS, CSI_INSTALL_PARAMETERS, CSI_INSTANCE_STATUSES, CSI_IP_ACCOUNTS, CSI_ITEM_INSTANCES, CSI_I_ORG_ASSIGNMENTS, CSI_I_PARTIES, CSI_I_PRICING_ATTRIBS, OE_ORDER_HEADERS_ALL, and OE_ORDER_LINES_ALL.

The view text is driven primarily by three aliases: CII over CSI_ITEM_INSTANCES, which supplies the core instance rows; OOL over OE_ORDER_LINES_ALL and OOH over OE_ORDER_HEADERS_ALL, which supply the original order context (order number, currency, net amount, and shipment date); and CIPA over CSI_I_PRICING_ATTRIBS, which contributes the 15 pricing attributes and pricing context. Additional joins reach CSI_I_PARTIES and CSI_IP_ACCOUNTS for ship-to and bill-to address data, CSI_INSTANCE_STATUSES for status resolution, and CSI_II_RELATIONSHIPS for instance relationships. The public package CSICUMPI_PUB is referenced as the standard programmatic entry point associated with customer product processing, reinforcing that the view is a queryable projection rather than a transactional object.

Key Columns

• CUSTOMER_PRODUCT_ID — maps from CII.INSTANCE_ID; the primary instance identifier used to relate to Install Base records.
• ROW_ID — maps from CII.ROWID, allowing legacy rowid-based lookups.
• INVENTORY_ITEM_ID, INVENTORY_REVISION, SERIAL_NUMBER, LOT_NUMBER, INSTANCE_NUMBER — item and instance identification attributes.
• QUANTITY, UNIT_OF_MEASURE — the instance quantity; the closest documented column to a returned quantity concept, normally compared against original order quantity.
• ORIGINAL_ORDER_NUMBER, ORIGINAL_ORDER_DATE, ORIGINAL_ORDER_CURRENCY_CODE, ORIGINAL_NET_AMOUNT — originating order context sourced from OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL.
• SHIPPED_FLAG, SHIPPED_DATE, DELIVERED_FLAG — shipment state; SHIPPED_FLAG is decoded from OOL.ACTUAL_SHIPMENT_DATE, while DELIVERED_FLAG is hard-coded NULL.
• INSTALL_DATE, ACTIVE_START_DATE, ACTIVE_END_DATE, INSTANCE_STATUS_ID — lifecycle and status fields.
• PARTY_ACCOUNT_ID, SHIP_TO_ADDRESS, BILL_TO_ADDRESS, INSTALL_LOCATION_ID, OPERATING_UNIT_ID — ownership, address, and organization context.
• MOST_RECENT_FLAG — hard-coded 'Y' in the view text.
• PRICING_ATTRIBUTE1..15, PRICING_CONTEXT — pricing attributes from CSI_I_PRICING_ATTRIBS.
• ATTRIBUTE1..15, CONTEXT — descriptive flexfield segments from the instance.

Common Use Cases and Queries

Typical use cases include Install Base extracts, customer-owned product reporting, order-to-instance reconciliation, and migration of legacy queries that previously targeted customer product tables. The following query illustrates retrieving instances with order and quantity context, which is the standard starting point when a user searches for returned or net quantities:

SELECT customer_product_id,
       serial_number,
       inventory_item_id,
       quantity,
       unit_of_measure,
       original_order_number,
       original_order_date,
       shipped_flag,
       shipped_date,
       party_account_id
  FROM apps.csi_customer_products_all_v
 WHERE inventory_item_id = :p_item_id
   AND NVL(shipped_flag,'N') = 'Y';

Because no dedicated RETURNED_QUANTITY column is documented in the view text, returned quantity must be derived by joining return order lines in OE_ORDER_LINES_ALL (via the originating order) or by comparing the instance QUANTITY against the original sold quantity on the corresponding order line. Practitioners should also filter on ACTIVE_START_DATE and INSTANCE_STATUS_ID to exclude terminated instances, and should treat DELIVERED_FLAG and PARENT_CP_ID as non-functional placeholders, since both are hard-coded NULL.