Results for “cs_customer_product_statuses”

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

Overview

CS_CUSTOMER_PRODUCT_STATUSES is a Service (CS) module reference table in Oracle E-Business Suite 12.1.1 and 12.2.2 that defines the discrete lifecycle statuses assignable to products recorded in the installed base. Installed base records — the customer-facing inventory of items, systems, and configurations a customer owns — carry a status that indicates whether a product is active, terminated, or in some other administrative state. This table provides the controlled vocabulary for those states, ensuring that every installed base product references a valid, predefined status rather than free-form text.

From a dimensional modeling perspective, the metadata classifies this object as hub-leaning. That classification suggests CS_CUSTOMER_PRODUCT_STATUSES functions primarily as a hub: a table whose surrogate key is referenced by multiple dependent tables, providing a stable, reusable identity for each status value independent of how it is described or consumed. Treating it as a hub is a modeling suggestion only; in the EBS schema it functions as a standard lookup/reference table. Note that the implementation metadata records "Not implemented in this database" for this specific extraction, meaning the table may be absent or empty in the surveyed instance, but it remains the canonical definition for statuses in the installed base.

Key Information Stored

The table is anchored by a single-column surrogate primary key, CUSTOMER_PRODUCT_STATUS_ID, enforced through the CS_CUSTOMER_PRODUCT_STATUS_PK constraint. This identifier is the value propagated into all dependent tables and should be treated as the authoritative business/technical key for a status row.

• CUSTOMER_PRODUCT_STATUS_ID — surrogate primary key and the foreign key target for every referencing table.
• Status name / description — the user-visible label presented in the Service responsibility when assigning a status to an installed base product.
• Status code — the internal, language-independent identifier used by application logic and concurrent programs.
• Enabled/active flag — governs whether the status remains selectable for new assignments.
• Seeded indicator — distinguishes Oracle-supplied statuses from user-defined ones.
• Audit columns — creation and last-update who/date columns common to EBS base tables.

Because the documented metadata does not enumerate descriptive or business-key columns, the surrogate key CUSTOMER_PRODUCT_STATUS_ID is the only column with a confirmed unique constraint; any additional uniqueness (for example on a name or code) should be confirmed against the live ALL_CONS_COLUMNS and ALL_INDEXES views in the target instance.

Common Use Cases and Queries

Typical reporting resolves the status of installed base products by joining CS_CUSTOMER_PRODUCTS_ALL to this reference table. A representative pattern:

• Listing active installed base products: SELECT cpi.serial_number, cps.customer_product_status_id FROM cs_customer_products_all cpi JOIN cs_customer_product_statuses cps ON cps.customer_product_status_id = cpi.customer_product_status_id WHERE cpi.customer_product_status_id = :status_id;
• Identifying which transaction types move a product into or out of a given status by joining CS_TRANSACTION_TYPES_B on INSTALLED_CP_STATUS_ID and NEW_CP_STATUS_ID.
• Populating status LOVs in custom Service extensions and in the Service Workbench.
• Reconciliation reporting: confirming that no CS_CUSTOMER_PRODUCTS_ALL row references an orphaned or disabled status.

Related Objects

The foreign-key metadata establishes two direct dependents, with the third relationship an outbound-external pattern to the same table evidenced through CS_TRANSACTION_TYPES_B:

• CS_CUSTOMER_PRODUCTS_ALL — the installed base product table; joins via CS_CUSTOMER_PRODUCTS_ALL.CUSTOMER_PRODUCT_STATUS_ID = CS_CUSTOMER_PRODUCT_STATUSES.CUSTOMER_PRODUCT_STATUS_ID. This is the primary transactional consumer.
• CS_TRANSACTION_TYPES_B — joins on two columns, INSTALLED_CP_STATUS_ID and NEW_CP_STATUS_ID, defining the status transitions triggered by a transaction type.

These relationships confirm CS_CUSTOMER_PRODUCT_STATUSES as a reference hub feeding both the installed base record and the transaction-type configuration that governs lifecycle movement.