Search Results csi_i_parties

Overview

The table CSI_I_PARTIES is a core data object within the Install Base module (CSI) of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as the central repository for managing all party associations for tracked assets, known as item instances. This table is fundamental to establishing and maintaining relationships between physical or logical assets and the various entities—such as customers, suppliers, employees, or internal organizations—that have a defined role concerning those assets. Its role is to enable comprehensive service, support, and asset lifecycle management by documenting who is related to an asset and the nature of that relationship.

Key Information Stored

The primary data stored in CSI_I_PARTIES defines the association between an item instance and a party. The key columns include INSTANCE_PARTY_ID, which is the unique primary key identifier for each party association record. The INSTANCE_ID column is a foreign key linking to the CSI_ITEM_INSTANCES table, identifying the specific asset. The PARTY_ID column is a foreign key linking to the HZ_PARTIES table in the Trading Community Architecture (TCA) model, identifying the associated entity. The RELATIONSHIP_TYPE_CODE column defines the nature of the association (e.g., Owner, Installer, Bill-To Contact) by referencing the CSI_IPA_RELATION_TYPES table. Additional columns, such as CONTACT_IP_ID, allow for hierarchical relationships between party records, enabling the designation of primary contacts within a party organization.

Common Use Cases and Queries

A primary use case is generating reports to understand asset ownership and responsibility. For example, to list all item instances with their current owners, a query would join CSI_I_PARTIES to CSI_ITEM_INSTANCES and HZ_PARTIES, filtered by the appropriate relationship type. Support and service teams frequently query this table to identify the correct contacts for a specific asset when logging service requests. Another critical operational use is during the installation or transfer of an asset, where applications like Field Service or Depot Repair create or update records in this table to reflect new party assignments. A sample query pattern is:

• SELECT cii.instance_number, hp.party_name, cip.relationship_type_code
• FROM csi_i_parties cip, csi_item_instances cii, hz_parties hp
• WHERE cip.instance_id = cii.instance_id
• AND cip.party_id = hp.party_id
• AND cip.relationship_type_code = 'OWNER';

Related Objects

CSI_I_PARTIES is a central hub with numerous relationships to other key Install Base and TCA objects. Its primary foreign key dependencies, as documented, are to CSI_ITEM_INSTANCES (the asset), HZ_PARTIES (the party entity), and CSI_IPA_RELATION_TYPES (the relationship definition). It has a recursive relationship to itself via the CONTACT_IP_ID column to model contact hierarchies. Furthermore, it is the parent table for transactional and historical data. The table CSI_IP_ACCOUNTS links party associations to specific accounting contexts, while CSI_T_PARTY_DETAILS stores additional descriptive information for the association. The CSI_I_PARTIES_H table maintains an audit history of changes to the party association records, which is crucial for compliance and tracking asset history.