Search Results split_cp_reference_number




Overview
Explore in AI Chat

Overview

CS_CP_AUDIT_MAINT_V is an APPS-owned database view in the Oracle E-Business Suite CS (Service) product family. It exposes audit trail information for customer products, presenting a denormalized, human-readable projection of the underlying CS_CP_AUDIT base records. Rather than forcing consumers to resolve surrogate identifiers themselves, the view joins audit rows to the descriptive name tables for customers, systems, product agreements, customer product statuses, and lookup meanings, so that each audited change to a customer product can be reported in business terms.

Within Oracle EBS 12.1.1 and 12.2.2 the view is documented as VALID. It functions primarily as a reporting and diagnostic object: it is the target of inquiry screens, concurrent report sources, and ad hoc SQL used by support and implementation teams to answer questions about how a customer product record changed over its lifecycle — for example, what the previous and current customer, system, product agreement, platform version, status, or type were, and who made the change.

Underlying Base Objects

The view is defined principally over CS_CP_AUDIT (exposed as a synonym), which stores the actual before-and-after audit rows for customer products. This is joined to CS_CUSTOMER_PRODUCTS_ALL, referenced to supply the split customer product record and its reference number. Master and transactional descriptive data are resolved through joins to HZ_CUST_ACCOUNTS and HZ_PARTIES (customer accounts and party names), CS_SYSTEMS (old and new systems), OE_AGREEMENTS (old and new product agreements), CS_CUSTOMER_PRODUCT_STATUSES (old and new customer product statuses), and CS_LOOKUPS (view) for the decoded meaning of type codes and the split reason code. FND_USER provides the user name of the person who created the audit row, and FND_GLOBAL is referenced for session context resolution. The package CSICUMPI_PUB is listed among the referenced base objects of the view’s dependency set, reflecting the customer product import/maintenance program that generates the audited activity.

Key Columns

The view exposes paired old/current columns that characterize each audited transition, along with surrogate keys, audit metadata, and descriptive labels:

Common Use Cases and Queries

Typical uses include change-history reporting for a customer product, auditing status transitions, and investigating who moved a product to a new status or customer. A representative query filtered on the current status name follows:

  • SELECT customer_product_id, new_cp_status, old_cp_status, new_customer, old_customer, updated_by, creation_date FROM cs_cp_audit_maint_v WHERE new_cp_status = :p_status ORDER BY creation_date DESC;
  • SELECT customer_product_id, old_type, new_type, cp_split_reason, old_cp_quantity, current_cp_quantity FROM cs_cp_audit_maint_v WHERE customer_product_id = :p_cp_id ORDER BY creation_date;
  • SELECT old_product_agreement, new_product_agreement, old_system, new_system, updated_by FROM cs_cp_audit_maint_v WHERE current_customer_id = :p_cust_id;

Because the view joins numerous descriptive tables, queries benefit from filtering on CUSTOMER_PRODUCT_ID or date ranges. All access should be performed through the APPS schema or a synonym, respecting the standard Oracle EBS security model.