Search Results product_agreement




Overview
Explore in AI Chat

Overview

CS_CUST_PROD_MAINT_V is a Service (CS) module view in Oracle EBS 12.1.1 and 12.2.2 that consolidates customer product instance data together with the surrounding order, party, status, system, and configuration context. The ETRM metadata describes it as a "New View for Customer Products – Performance," indicating that it was introduced primarily to support high-volume retrieval of customer product records without requiring callers to join the many base tables that the customer product entity depends upon. Rather than exposing only the columns of the CS_CUSTOMER_PRODUCTS table, the view denormalizes related attributes such as the account number, party name, order header details, order line pricing, product description, configuration identifiers, and the concatenated key flexfield segment.

Because it is a view rather than a table, it carries no independent storage and inherits the read consistency, security, and indexing characteristics of its underlying objects. In 12.1.1 and 12.2.2 it is commonly used in reporting, service workbench extensions, and integration extracts where a flattened, single-row-per-customer-product representation is required. The "config_root_info" search context is directly relevant: the view exposes CONFIG_ROOT_ID, CONFIG_PARENT_ID, CONFIG_ENABLED_FLAG, CONFIG_START_DATE, CONFIG_END_DATE, and CONFIG_TYPE, which are the fields used to reconstruct configuration hierarchy and root information for installed base items.

Underlying Base Objects

The documented metadata reports the view as "Not implemented in this database" and lists no referenced base objects explicitly, so the object definitions below are derived from the SELECT statement embedded in the documentation excerpt:

The joins are outer joins in practice, since a customer product may lack an originating order line or agreement.

Key Columns

The view exposes the complete set of CS_CUSTOMER_PRODUCTS columns together with substantial join context. Principal columns include:

Common Use Cases and Queries

Typical uses include installed base reporting, configuration hierarchy reconstruction, and integration extracts. A representative query to locate root configuration records is:

SELECT customer_product_id, current_serial_number, config_root_id, config_parent_id, config_type, cp_status FROM cs_cust_prod_maint_v WHERE config_root_id IS NOT NULL AND most_recent_flag = 'Y' AND org_id = :p_org_id;

A second scenario retrieves order-to-installation lineage:

SELECT account_number, party_name, order_number, line_number, ordered_date, installation_date, unit_selling_price, product_description FROM cs_cust_prod_maint_v WHERE original_order_line_id = :p_line_id;

A third filters serviceable items for a customer:

SELECT customer_product_id, product_description, system, cp_status, service_order_allowed_flag FROM cs_cust_prod_maint_v WHERE customer_id = :p_cust_id AND terminated_flag = 'N' AND service_order_allowed_flag = 'Y';

Because no base objects are documented and the object is reported as not implemented in the reference database, DBAs should verify the actual view text in each environment before relying on specific column aliases, particularly the unaliased L3.MEANING column.