Search Results cs_cp_audit_u1

Overview

The CS.CS_CP_AUDIT table is an audit trail object within the Oracle E-Business Suite Customer Support (CS) schema, which is part of the Enterprise Territory and Resource Management (ETRM) and Service/TeleService product family. It records changes made to installed base "Customer Products" — the individual instances of inventory items, configurations, and services tracked against a customer's account. Each row represents a discrete audit event that captures the before-and-after state of a customer product, enabling historical traceability of who changed what, when, and from which value to which value.

Because the table stores a complete set of old and new values for a wide range of attributes, it functions as an audit or history satellite. Under a Data Vault modeling heuristic, the table's relationship metadata classifies it as a link object, as indicated by its foreign-key structure connecting to multiple dimension tables such as HZ_CUST_ACCOUNTS, HZ_PARTY_SITES, and HZ_CUST_ACCT_SITES_ALL. This classification should be treated as a design suggestion rather than an authoritative declaration.

Per Oracle's standard notice, this object is marked for Oracle Internal Use Only. Access using custom code, reports, or integrations is not supported by Oracle, and modification should occur only through standard Oracle Applications programs.

Key Information Stored

The table contains 104 documented columns. The surrogate primary key is CP_AUDIT_ID, which is also the business-key candidate, enforced by the unique index CS_CP_AUDIT_U1. This index is the object most commonly sought by the search term cs_cp_audit_u1.

The most significant columns include:

• CUSTOMER_PRODUCT_ID — The identifier of the customer product instance whose change triggered the audit row.
• CUSTOMER_CHANGED_FLAG, OLD_CUSTOMER_ID, CURRENT_CUSTOMER_ID — Indicate whether the owning customer changed, with the prior and subsequent customer identifiers (FKs to HZ_CUST_ACCOUNTS).
• SYSTEM_CHANGED_FLAG, OLD_SYSTEM_ID, CURRENT_SYSTEM_ID — Track changes to the associated system or instance identifier.
• PRODUCT_AGREEMENT_CHANGED_FLAG, OLD_PRODUCT_AGREEMENT_ID, CURRENT_PRODUCT_AGREEMENT_ID — Capture changes to the linked product agreement.
• SERVICE_AGREEMENT_CHANGED_FLAG, OLD_SERVICE_AGREEMENT_ID, CURRENT_SERVICE_AGREEMENT_ID — Capture changes to the linked service agreement.
• CP_STATUS_CHANGED_FLAG, OLD_CP_STATUS_ID, CURRENT_CP_STATUS_ID — Record lifecycle status transitions of the customer product.
• OLD_BILL_TO_SITE_USE_ID, CURRENT_BILL_TO_SITE_USE_ID — Reference HZ_CUST_ACCT_SITES_ALL for billing site changes.
• OLD_SHIP_TO_SITE_USE_ID, CURRENT_SHIP_TO_SITE_USE_ID — Reference HZ_PARTY_SITES for ship-to site changes.
• OLD_INSTALL_SITE_USE_ID, CURRENT_INSTALL_SITE_USE_ID — Reference HZ_PARTY_SITES for installation site changes.
• ATTRIBUTE1 through ATTRIBUTE15, CONTEXT — Descriptive flexfield segments for extensible audit attributes.
• OBJECT_VERSION_NUMBER — Optimistic locking version token used by the EBS framework.
• SECURITY_GROUP_ID — References FND_SECURITY_GROUPS for multi-tenant data partitioning.
• Standard Who columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) — Provide the audit timestamp and user identity for the event itself.

Common Use Cases and Queries

The primary use case is historical reporting on customer product changes for service, warranty, and entitlement analysis. Because the table stores flags alongside old and new values, queries typically filter on a specific change flag to isolate an event type.

• Change history for a single customer product: query by CUSTOMER_PRODUCT_ID and order by CREATION_DATE to reconstruct the life cycle of an instance.
• Customer reassignment reporting: filter on CUSTOMER_CHANGED_FLAG = 'Y' to list products moved between customers, joining OLD_CUSTOMER_ID and CURRENT_CUSTOMER_ID to HZ_CUST_ACCOUNTS.
• Agreement audit: filter on PRODUCT_AGREEMENT_CHANGED_FLAG or SERVICE_AGREEMENT_CHANGED_FLAG to trace agreement linkage changes over time.
• Status transition analysis: filter on CP_STATUS_CHANGED_FLAG = 'Y' to measure movement through the customer product status life cycle.
• Site and installation footprint: join the OLD_*_SITE_USE_ID and CURRENT_*_SITE_USE_ID columns to HZ_PARTY_SITES or HZ_CUST_ACCT_SITES_ALL to compare geographic placement before and after a change.
• Audit attribution: group by LAST_UPDATED_BY and CREATION_DATE to determine which users or concurrent processes initiated the changes.
• Migration tracking: flags such as VALID_FOR_CSI_MIGRATION, MIGRATED_STATUS_FLAG, and UPGRADED_STATUS_FLAG support CSI data migration reconciliation.

Related Objects

The following objects are the most significant referenced by or related to CS_CP_AUDIT, based on the documented foreign-key relationships:

• HZ_CUST_ACCOUNTS — joined via OLD_CUSTOMER_ID and CURRENT_CUSTOMER_ID.
• HZ_PARTY_SITES — joined via OLD_SHIP_TO_SITE_USE_ID, CURRENT_SHIP_TO_SITE_USE_ID, OLD_INSTALL_SITE_USE_ID, and CURRENT_INSTALL_SITE_USE_ID.
• HZ_CUST_ACCT_SITES_ALL — joined via OLD_BILL_TO_SITE_USE_ID and CURRENT_BILL_TO_SITE_USE_ID.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for access control partitioning.
• CS_CP_AUDIT_U1 — the unique index on CP_AUDIT_ID that enforces the primary key.
• Other CS schema customer product tables (such as the base customer product and status reference tables) are referenced indirectly through CUSTOMER_PRODUCT_ID, OLD_CP_STATUS_ID, and CURRENT_CP_STATUS_ID, though these FKs are not enumerated in the documented relationship data.