Search Results cs_customer_products_all




Overview

The CS_CUSTOMER_PRODUCTS_ALL table is the central repository for Customer Installed Base (CIB) information within Oracle E-Business Suite Service (CS) modules. It stores the master record of products and assets that have been sold, installed, or are otherwise under service at a customer's location. This table is fundamental to service management, enabling the tracking of service history, warranties, contracts, and repairs against specific customer-owned assets. Its role is critical for linking service activities, such as service requests and field service dispatches, to the physical product instances they pertain to. The "_ALL" suffix indicates it is a multi-organization enabled table, storing data partitioned by operating unit.

Key Information Stored

The table's structure captures comprehensive details about the installed product instance. The primary key is CUSTOMER_PRODUCT_ID, which uniquely identifies each asset record. Key foreign key relationships define the asset's context: CUSTOMER_ID links to HZ_CUST_ACCOUNTS (TCA), while INSTALL_SITE_USE_ID, SHIP_TO_SITE_USE_ID, and BILL_TO_SITE_USE_ID link to HZ_PARTY_SITES and HZ_CUST_ACCT_SITES_ALL for location data. The table manages product configuration through PARENT_CP_ID, CONFIG_ROOT_ID, and CONFIG_PARENT_ID, allowing representation of complex, multi-component assets. Status is tracked via CUSTOMER_PRODUCT_STATUS_ID linked to CS_CUSTOMER_PRODUCT_STATUSES. Critical inventory details are stored via MIB_INVENTORY_ITEM_ID, MIB_ORGANIZATION_ID, and MIB_REVISION_ID, linking to the Inventory master (MTL_ITEM_REVISIONS_B). The SYSTEM_ID links the asset to a broader CS_SYSTEMS_ALL_B record, and CURRENT_CP_REVISION_ID points to the active revision in CS_CP_REVISIONS.

Common Use Cases and Queries

This table is queried extensively for service delivery and asset reporting. Common scenarios include generating a customer's installed base report, validating warranty coverage during service request creation, and identifying assets eligible for a service contract renewal. A typical query retrieves product details for a specific customer, joining related TCA and Inventory tables:

  • SELECT ccp.CUSTOMER_PRODUCT_ID, ccp.SERIAL_NUMBER, hca.account_number, msib.segment1 item_code FROM CS_CUSTOMER_PRODUCTS_ALL ccp, HZ_CUST_ACCOUNTS hca, MTL_SYSTEM_ITEMS_B msib WHERE ccp.CUSTOMER_ID = hca.cust_account_id AND ccp.MIB_INVENTORY_ITEM_ID = msib.inventory_item_id AND ccp.MIB_ORGANIZATION_ID = msib.organization_id AND hca.account_number = 'CUST123';
  • Identifying the configuration hierarchy of an asset: SELECT CONNECT_BY_ROOT SERIAL_NUMBER AS Root_Asset, LEVEL, SERIAL_NUMBER FROM CS_CUSTOMER_PRODUCTS_ALL START WITH CUSTOMER_PRODUCT_ID = :p_root_cp_id CONNECT BY PRIOR CUSTOMER_PRODUCT_ID = PARENT_CP_ID;
  • Joining to service requests (CS_INCIDENTS_ALL) via the CS_INCIDENTS_ALL.CUSTOMER_PRODUCT_ID column is a fundamental pattern for service history analysis.

Related Objects

CS_CUSTOMER_PRODUCTS_ALL has extensive relationships across the EBS suite. Key dependent service tables include CSD_REPAIRS, which logs repair orders against an asset, and CS_CONTACTS, which can list contacts associated with the product instance. Child tables CS_CP_LANGUAGES and CS_CP_PARAMETERS store translated descriptions and extended attributes, respectively. It is the parent table for revisions stored in CS_CP_REVISIONS. For transactional lineage, ORIGINAL_LINE_SERV_DETAIL_ID can link back to the original service line detail in CS_LINE_INST_DETAILS. Crucially, it is referenced by the core service request entity, CS_INCIDENTS_ALL, forming the primary link between reported problems and the affected asset.