Search Results hz_party_sites




Overview
Explore in AI Chat

Overview

CS_CP_AUDIT is an audit table in the CS (Service) product schema of Oracle E-Business Suite, documented as VALID in both 12.1.1 and 12.2.2. Its stated purpose is to record audit information about products in the installed base — that is, changes made to customer product instances tracked by Service/Depot Repair and the Install Base (CSI) modules. Each row captures a before-and-after image of a single attribute group on a customer product record, together with change flags that indicate which attributes were altered.

Under the heuristic Data Vault classification supplied in the metadata, CS_CP_AUDIT is modelled as a link. This reflects its structure: the table is dominated by foreign key references to parties, sites, accounts, and related transactional entities, and it connects a customer product to the sites and accounts that applied at two points in time (the "OLD" and "CURRENT" states). It is not a pure hub, since it carries no single durable business key of its own beyond CP_AUDIT_ID, and it is not a pure satellite, since it references multiple external entities directly rather than depending on a single parent hub.

Key Information Stored

The table holds 104 documented columns. The surrogate primary key, enforced by the unique index CS_CP_AUDIT_U1, is CP_AUDIT_ID. The remaining significant columns fall into the following groups:

Common Use Cases and Queries

The most common reporting need is a change history for a given installed-base product. Because each row carries OLD and CURRENT values of the same attribute, a simple query reconstructs the timeline:

SELECT cp_audit_id, customer_product_id, cp_status_changed_flag, old_cp_status_id, current_cp_status_id, last_update_date FROM cs.cs_cp_audit WHERE customer_product_id = :cp_id ORDER BY last_update_date;

A site-change report joins both site columns back to HZ_PARTY_SITES to resolve the party site and location:

SELECT a.customer_product_id, a.old_install_site_use_id, a.current_install_site_use_id, s.party_site_id, s.location_id FROM cs.cs_cp_audit a, hz.hz_party_sites s WHERE a.current_install_site_use_id = s.party_site_id;

Typical scenarios include reconciliation after customer reorganisation or account merges, investigation of incorrectly installed locations, migration validation (using VALID_FOR_CSI_MIGRATION and MIGRATED_STATUS_FLAG), and audit evidence for split or transferred product instances.

Related Objects

  • HZ_PARTY_SITES — referenced four times through CURRENT_INSTALL_SITE_USE_ID, OLD_INSTALL_SITE_USE_ID, CURRENT_SHIP_TO_SITE_USE_ID, and OLD_SHIP_TO_SITE_USE_ID.
  • HZ_CUST_ACCT_SITES_ALL — referenced by CURRENT_BILL_TO_SITE_USE_ID and OLD_BILL_TO_SITE_USE_ID.
  • HZ_CUST_ACCOUNTS — referenced by CURRENT_CUSTOMER_ID and OLD_CUSTOMER_ID.
  • FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID.
  • Service / Install Base product tables (CS_*, CSI_*) — the CUSTOMER_PRODUCT_ID and SPLIT_CP_ID columns logically depend on the customer product instance and its split lineage.