Results for “installation_date”

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

Overview

CS_CUSTOMER_PRODUCTS is an APPS-owned, VALID database view within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, delivered as part of the CS (Service) product family. The view presents customer product information organized by operating unit. In the Service module architecture, a "customer product" (often abbreviated as CP) represents an instance of an inventory item owned or installed at a customer site — the installed base record that drives service contracts, depot repair, field service, and tele-service activities. The view is primarily intended for multi-organization reporting, where consumers require customer product rows scoped to a given organization context, and for integration programs that must resolve customer product data without directly accessing the underlying _ALL table. Its presence in the Applications schema allows it to be referenced by concurrent programs, BI Publisher reports, OAF pages, and inbound/outbound interfaces that operate as the APPS database user.

Underlying Base Objects

According to the documented ETRM metadata for 12.2.2, CS_CUSTOMER_PRODUCTS is defined over two referenced base objects:

• CS_CUSTOMER_PRODUCTS_ALL (SYNONYM) — the multi-organization base entity that stores customer product records across all operating units. The _ALL suffix confirms that the object holds data for every ORG_ID, and the view exists to expose this data (in the standard 12.1.1/12.2.2 pattern, typically through a MO: Operating Unit or MO: Security Profile VPD policy applied at the synonym level) with the organization context resolved.
• CSICUMPI_PUB (PACKAGE) — the Customer Products public API package. The view references this package (commonly through an inline packaged function call such as to filter, translate, or derive attribute values consistently with the API-layer logic), which means view performance can depend on the PL/SQL function's runtime behavior and that direct SELECTs incur context-switch overhead per row.

Because the view is defined over a synonym rather than a table directly, any change to the CS_CUSTOMER_PRODUCTS_ALL synonym target or its VPD policy directly affects the rows returned.

Key Columns

The SELECT list exposes the full column set of the underlying entity. Important columns include:

• CUSTOMER_PRODUCT_ID — primary key of the customer product instance.
• CUSTOMER_ID, INVENTORY_ITEM_ID, LOT_NUMBER, CURRENT_SERIAL_NUMBER — identify the owning customer and the installed item, including lot and serial tracking.
• ORG_ID — operating unit; the principal organization-scoping column.
• TYPE_CODE, CUSTOMER_PRODUCT_STATUS_ID, MOST_RECENT_FLAG, CREATED_MANUALLY_FLAG — classify the record (e.g., item instance, recovery) and its lifecycle state.
• SHIP_TO_SITE_USE_ID, BILL_TO_SITE_USE_ID, INSTALL_SITE_USE_ID — site-use references for shipping, billing, and installation locations.
• QUANTITY, UNIT_OF_MEASURE_CODE, SHIPPED_FLAG, DELIVERED_FLAG, SHIPPED_DATE, INSTALLATION_DATE — fulfillment and installation tracking.
• ORIGINAL_ORDER_LINE_ID, ORIGINAL_NET_AMOUNT, ORIGINAL_ORDER_CURRENCY_CODE, RMA_LINE_ID, RETURN_BY_DATE, ACTUAL_RETURNED_DATE — originating order and return (RMA) context.
• CONFIG_ENABLED_FLAG, CONFIG_ROOT_ID, CONFIG_PARENT_ID, CONFIG_TYPE, CONFIG_START_DATE, CONFIG_END_DATE — configuration structure for assembled products.
• CURRENT_CP_REVISION_ID, PRODUCT_AGREEMENT_ID, SYSTEM_ID, PARENT_CP_ID, PROJECT_ID, TASK_ID — revision, agreement, system, hierarchy, and project associations.
• START_DATE_ACTIVE, END_DATE_ACTIVE, OBJECT_VERSION_NUMBER — effective dating and optimistic locking.
• ATTRIBUTE1–15, CONTEXT, PRICING_ATTRIBUTE1–28 — descriptive flexfield and pricing flexfield storage.

Common Use Cases and Queries

Typical scenarios include: extracting the installed base for a specific operating unit; listing serialized products shipped but not yet installed; reconciling customer products against order lines and RMAs; and feeding service contract entitlement checks or field service dispatch.

Because the view applies organization context, queries should be executed from an environment where the correct MO profile option is set for the session.

• Installed base by customer and item:

  SELECT customer_product_id, customer_id, inventory_item_id,
         current_serial_number, installation_date, org_id
  FROM   cs_customer_products
  WHERE  customer_id = :customer_id
  AND    most_recent_flag = 'Y';

• Returnable customer products:

  SELECT cp.customer_product_id, cp.reference_number, cp.return_by_date
  FROM   cs_customer_products cp
  WHERE  cp.rma_line_id IS NOT NULL
  AND    cp.actual_returned_date IS NULL
  AND    cp.org_id = :org_id;

• Configuration hierarchies:

  SELECT config_root_id, config_parent_id, customer_product_id, config_type
  FROM   cs_customer_products
  WHERE  config_enabled_flag = 'Y'
  AND    config_root_id = :root_id
  ORDER BY config_parent_id;

When large volumes are involved, note that the packaged function reference to CSICUMPI_PUB may prevent certain predicate pushdowns; filtering by CUSTOMER_ID, ORG_ID, or CUSTOMER_PRODUCT_ID is recommended to limit row processing.