Results for “csi_i_parties”

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

Overview

CSI_I_PARTIES is a table within the CSI (Install Base) schema of Oracle E-Business Suite, documented as valid in both Release 12.1.1 and 12.2.2. Its documented description, "Instance - Party Associations," defines its purpose: it stores the associations between item instances (the tracked units recorded on the Install Base) and the parties who are linked to those instances. Parties are held in the Trading Community Architecture (HZ) model, so this table functions as the associative layer that binds an install base instance to a customer, contact, or other party registration.

Because the table carries relationship semantics rather than descriptive party attributes, it is a reference point for any Install Base inquiry that needs to resolve who is associated with a tracked unit, in what capacity, and for which effective period. The ETRM metadata classifies this object as satellite-leaning under a heuristic Data Vault assessment. As a modeling suggestion, this means it is best treated as a dependent structure whose identity and meaning flow from its parent instance and party references, rather than as an independent hub of business keys.

Key Information Stored

The table is documented with 35 columns. The most operationally significant are:

• INSTANCE_PARTY_ID — the surrogate primary key, enforced by CSI_I_PARTIES_PK and also served by the unique index CSI_I_PARTIES_U01. This is the single-column identifier used by dependent tables.
• INSTANCE_ID — the foreign key to CSI_ITEM_INSTANCES, identifying the item instance being associated.
• PARTY_ID — the foreign key to HZ_PARTIES, identifying the party (customer, contact, or organization) tied to the instance.
• PARTY_SOURCE_TABLE — indicates the source of the party reference, distinguishing origin of the association.
• RELATIONSHIP_TYPE_CODE — the foreign key to CSI_IPA_RELATION_TYPES, defining the nature of the association, such as owner or contact role.
• PREFERRED_FLAG, PRIMARY_FLAG, CONTACT_FLAG — Boolean indicators marking whether the association is the preferred party, the primary party, or a contact-only relationship.
• CONTACT_IP_ID — a self-referencing foreign key to CSI_I_PARTIES, used to associate a contact party row with its governing instance-party row.
• ACTIVE_START_DATE and ACTIVE_END_DATE — the effective dating window for the association.
• SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS supporting multi-organization access control.
• OBJECT_VERSION_NUMBER — the standard EBS optimistic locking column.
• MIGRATED_FLAG and the CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN audit columns, which record data conversion status and row-level change history.

The ATTRIBUTE1 through ATTRIBUTE15 and CONTEXT columns form the standard EBS descriptive flexfield structure, allowing customer-specific extensions without schema modification.

Common Use Cases and Queries

The most common requirement is resolving the parties associated with a given instance. A typical pattern joins this table to HZ_PARTIES through PARTY_ID, filtered by INSTANCE_ID, and ordered by the flag columns to surface the primary or preferred party first. Reporting on Install Base ownership frequently filters RELATIONSHIP_TYPE_CODE against CSI_IPA_RELATION_TYPES to isolate a specific role, and applies ACTIVE_START_DATE and ACTIVE_END_DATE to return only currently effective associations.

Contact hierarchies are traversed through the self-referencing CONTACT_IP_ID column, allowing a parent association to be resolved to its dependent contacts. Security-aware queries must join to FND_SECURITY_GROUPS using SECURITY_GROUP_ID to enforce organizational isolation. Because the table evolves through updates rather than deletes, the CSI_I_PARTIES_H history table supports as-of-date reporting and audit reconstruction of prior party associations.

Related Objects

• CSI_ITEM_INSTANCES — joined on INSTANCE_ID; the parent instance record for each association.
• HZ_PARTIES — joined on PARTY_ID; supplies party name and TCA attributes.
• CSI_IPA_RELATION_TYPES — joined on RELATIONSHIP_TYPE_CODE; supplies the relationship type meaning.
• CSI_IP_ACCOUNTS — references this table through INSTANCE_PARTY_ID, linking associations to account data.
• CSI_I_PARTIES_H — the history table keyed by INSTANCE_PARTY_ID for audit and as-of reporting.
• CSI_T_PARTY_DETAILS — references INSTANCE_PARTY_ID and holds extended party detail attributes.
• CSI_I_PARTY_INTERFACE — the interface table for loading or updating instance-party associations.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID to enforce access control.