Search Results customer_product_type




Overview
Explore in AI Chat

Overview

The APPS.CS_CP_AUDIT_MAINT_V view provides a denormalized, human-readable presentation of the CS_CP_AUDIT table, which stores audit trail records for customer product (CP) maintenance activity within Oracle E-Business Suite's TeleService/Service (CS) module. Each row represents a single captured change to a customer product record, exposing both the prior ("OLD") and resulting ("CURRENT") values side by side. Because raw audit tables store numeric foreign keys, this view resolves those identifiers into descriptive names from customer, system, agreement, status, and lookup sources, making it directly usable for reporting, reconciliation, and integration without additional joins. It is documented as a standard APPS-owned view in ETRM for both 12.1.1 and 12.2.2, and it is commonly surfaced in customer product audit inquiries and historical change reports where end users need to see what changed on a customer product instance and who changed it.

Underlying Base Objects

The view is defined primarily over the CS_CP_AUDIT synonym and joins outward to twelve additional objects. Customer references are resolved through CS_CUSTOMER_PRODUCTS_ALL, HZ_CUST_ACCOUNTS, and HZ_PARTIES (via the party_name attribute). System references join to CS_SYSTEMS for both old and current system names. Product agreement references join to OE_AGREEMENTS. Status descriptions are resolved through CS_CUSTOMER_PRODUCT_STATUSES, while type codes and split reason codes map to meanings via CS_LOOKUPS (the view is joined twice for OLD/CURRENT type codes plus once for split reason). FND_USER supplies the updating user's name, and FND_GLOBAL supports session context. CSICUMPI_PUB is the concurrent program package associated with the customer product import/maintenance process that writes audit rows. Note that the documented dependency list confirms these base objects; the join predicates in the view text link each audit foreign key to its parent with outer joins.

Key Columns

Common Use Cases and Queries

Typical uses include auditing status or ownership changes on a customer product, reporting quantity splits, and tracing historical customer/system/agreement reassignments. Example:

SELECT customer_product_id, old_customer, new_customer,
       old_cp_status, new_cp_status, old_type, new_type,
       updated_by, last_update_date
FROM   apps.cs_cp_audit_maint_v
WHERE  customer_product_id = :cp_id
ORDER  BY last_update_date DESC;

To find split activity:

SELECT customer_product_id, old_cp_quantity, current_cp_quantity,
       split_cp_reference_number, cp_split_reason
FROM   apps.cs_cp_audit_maint_v
WHERE  split_cp_id IS NOT NULL;