Results for “new_contact_type”

8 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CS_CP_PARTIES_AUDIT is an audit history table in the CS (Service) product schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It records the historical state of rows stored in CS_CONTACTS, the table that holds information about parties associated with an entity such as a customer, organization, or service object. Every insert, update, or attribute change against a contact-party relationship produces a corresponding audit row, capturing both the prior ("OLD_") and current ("NEW_") values of the audited attributes alongside standard audit metadata. The table is owned by the CS schema and is documented as VALID in ETRM.

Under the heuristic Data Vault classification mined from its foreign-key structure, this object is satellite-leaning. It is a descriptive, time-stamped history table that hangs off the CS_CONTACTS business key rather than acting as a hub (which would hold a unique business key) or a link (which would resolve many-to-many relationships). Treating it as a satellite is a modeling suggestion: the primary key is a surrogate identifier, and the meaningful business context is supplied by the referenced CP_PARTY_ID in CS_CONTACTS. The physical schema comprises 39 columns.

Key Information Stored

The surrogate primary key is CS_CP_PARTIES_AUDIT_ID, which is backed by the CS_CP_PARTIES_AUDIT_PK constraint. This column uniquely identifies each audit record and is the only documented key; the table does not expose a separate unique business-key index in the supplied metadata, so no column set should be assumed to be a natural or business key. The business-relevant foreign key is CP_PARTY_ID, which joins back to CS_CONTACTS and identifies the party whose changes are being audited.

Common Use Cases and Queries

Audit history tables support compliance, dispute resolution, and reconciliation. Typical patterns include reconstructing the contact history for a party, detecting when a contact was promoted to primary or preferred, and auditing changes to active date ranges.

  • Point-in-time reconstruction: select the row with the greatest AUDIT_DATE less than or equal to a target date for a given CP_PARTY_ID, then read the NEW_ columns to reproduce the state at that instant.
  • Change detection: filter where OLD_PRIMARY_FLAG <> NEW_PRIMARY_FLAG or OLD_PREFERRED_FLAG <> NEW_PREFERRED_FLAG to report promotions and demotions.
  • Contact reassignment: compare OLD_CONTACT_ID and NEW_CONTACT_ID to trace when a party was re-associated with a different contact.
  • Active-window audit: compare OLD_START_DATE_ACTIVE/NEW_START_DATE_ACTIVE and OLD_END_DATE_ACTIVE/NEW_END_DATE_ACTIVE to identify extensions or expirations.
  • Cross-party reporting: join to CS_CONTACTS on CP_PARTY_ID and filter by SECURITY_GROUP_ID to produce security-scoped audit reports for a specific operating unit.

Related Objects

  • CS_CONTACTS — the primary referenced table; joined via CS_CP_PARTIES_AUDIT.CP_PARTY_ID = CS_CONTACTS.CP_PARTY_ID. This is the source of the audited business key.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID, providing the security-group definition used to scope audit queries by operating unit or organization.
  • CS_CP_PARTIES — the base (non-audit) party-relationship entity commonly queried alongside the audit table to contrast current versus historical values.
  • CS_CONTACTS_AUDIT — companion audit history for the parent contact records, useful when reconciling contact-level and party-level change histories.
  • CS_INCIDENTS and related Service objects — downstream consumers that reference contact parties and may rely on the same CP_PARTY_ID lineage.
  • FND_USER — implied join target for LAST_UPDATED_BY and CREATED_BY to resolve user names in audit reporting.

The table should be treated as append-only history and queried with date-bounded predicates for performance, since it can grow rapidly in high-volume Service implementations.