Search Results old_cp_status

Overview

CS_CP_AUDIT_MAINTAIN_V is a Service (CS) module view in Oracle E-Business Suite 12.1.1 and 12.2.2 that presents the contents of the Customer Product audit table in a denormalized, human-readable form. The Customer Product entity represents a customer's entitlement to a product, typically tied to a service agreement, warranty, or support contract. Whenever a Customer Product record is created, split, transferred, or otherwise modified, the audit trail records the prior and new values side by side. This view exposes that audit trail together with the resolved descriptive names for the referenced identifiers.

The view is not a physical table and its content is driven entirely by the base audit table. The ETRM metadata notes that it is "Not implemented in this database," meaning it is a seeded dictionary object whose underlying definition is shipped by Oracle but which is only materialized in installations where the Service module is fully configured. The view plays no direct role in transaction processing; its purpose is audit reporting, reconciliation, and troubleshooting of Customer Product life-cycle changes.

Underlying Base Objects

The view is defined over CS_CP_AUDIT (aliased CPA), the Customer Product audit table. It joins that table to several lookup and master tables using outer joins indicated by the (+) syntax:

• RA_CUSTOMERS twice (CUST1, CUST2) to resolve OLD_CUSTOMER_ID and CURRENT_CUSTOMER_ID into customer names.
• CS_SYSTEMS twice (CS1, CS2) to resolve old and current system identifiers.
• SO_AGREEMENTS twice (PAG1, PAG2) to resolve old and current product agreement identifiers.
• CS_CUSTOMER_PRODUCT_STATUSES twice (CPS1, CPS2) to resolve old and current status names.
• FND_USER to resolve CREATED_BY into UPDATED_BY (USER_NAME).
• CS_CUSTOMER_PRODUCTS_ALL (CCP) to resolve SPLIT_CP_ID into SPLIT_CP_REFERENCE_NUMBER.
• CS_LOOKUPS three times (LU1, LU2, LU) to resolve old type code, current type code, and CP_SPLIT_REASON_CODE into their meanings.

Because every join is an outer join, audit rows survive even when the referenced customer, system, agreement, status, or lookup value has since been deleted or end-dated. The metadata lists no documented base objects separately, but the view text confirms CS_CP_AUDIT is the driving table.

Key Columns

The most frequently referenced column in this view, and the reason it surfaces for searches on "current_customer_id," is CPA.CURRENT_CUSTOMER_ID. This is the customer identifier in effect after the audited change, and it joins to RA_CUSTOMERS to produce NEW_CUSTOMER. Its counterpart OLD_CUSTOMER_ID yields OLD_CUSTOMER, allowing direct before/after comparison. Other prominent pairs include OLD_SYSTEM_ID / CURRENT_SYSTEM_ID, OLD_PRODUCT_AGREEMENT_ID / CURRENT_PRODUCT_AGREEMENT_ID, OLD_CP_STATUS_ID / CURRENT_CP_STATUS_ID, and OLD_TYPE_CODE / CURRENT_TYPE_CODE, each with a resolved display column (OLD_SYSTEM / NEW_SYSTEM, OLD_PRODUCT_AGREEMENT / NEW_PRODUCT_AGREEMENT, OLD_CP_STATUS / NEW_CP_STATUS, OLD_TYPE / NEW_TYPE).

Split-related columns include SPLIT_CP_ID, SPLIT_CP_REFERENCE_NUMBER, OLD_CP_QUANTITY, CURRENT_CP_QUANTITY, and CP_SPLIT_REASON_CODE with its meaning column CP_SPLIT_REASON. Standard audit columns (ROW_ID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the descriptive flexfield columns CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 are also exposed, along with COMMENTS.

Common Use Cases and Queries

Typical scenarios include identifying which customer a Customer Product was reassigned to, auditing quantity changes caused by splits, and demonstrating full traceability for service entitlement disputes.

• Locate the current customer for an audited customer product change:

  SELECT customer_product_id, old_customer, new_customer,
         old_cp_quantity, current_cp_quantity, last_update_date
  FROM   cs_cp_audit_maintain_v
  WHERE  current_customer_id = :p_customer_id;

• Review all changes for a specific Customer Product:

  SELECT old_customer, new_customer, old_cp_status, new_cp_status,
         cp_split_reason, updated_by, last_update_date
  FROM   cs_cp_audit_maintain_v
  WHERE  customer_product_id = :p_cp_id
  ORDER BY last_update_date;

• Analyze split activity by reason:

  SELECT cp_split_reason, COUNT(*) audit_count
  FROM   cs_cp_audit_maintain_v
  WHERE  cp_split_reason_code IS NOT NULL
  GROUP BY cp_split_reason;

Because all descriptive lookups are resolved within the view, reports can present readable output without additional joins, making the view suitable for audit workbooks, reconciliation extracts, and integration feeds that require customer product history.