Search Results txn_party_detail_id

Overview

The CSI_T_PARTY_DETAILS table is a core transaction table within the Oracle E-Business Suite Install Base (CSI) module for versions 12.1.1 and 12.2.2. It functions as a transactional staging table that temporarily holds new or updated party associations for item instances during business processes like service requests, asset transfers, or instance updates. Its primary role is to record proposed changes to the relationships between an Install Base instance and various parties (e.g., owners, users, contacts, service providers) before these changes are permanently applied to the master instance-party relationship table (CSI_I_PARTIES). This transactional model ensures data integrity and supports complex business flows where multiple related updates are processed as a single unit.

Key Information Stored

The table stores the details of party associations linked to a specific transaction line. Its primary key is the system-generated TXN_PARTY_DETAIL_ID. Critical foreign key columns define its relationships: TXN_LINE_DETAIL_ID links it to the parent transaction line in CSI_T_TXN_LINE_DETAILS. INSTANCE_PARTY_ID can reference an existing party record in CSI_I_PARTIES for updates, or be null for new associations. PARTY_SOURCE_ID links to the master party definition in HZ_PARTIES. RELATIONSHIP_TYPE_CODE, referencing CSI_IPA_RELATION_TYPES, defines the nature of the association (e.g., OWNER, USER, SERVICE_PROVIDER). CONTACT_PARTY_ID, which is a self-referencing foreign key to the same table, is used to link a primary party record to a specific contact person record within the same transaction.

Common Use Cases and Queries

A primary use case is auditing and troubleshooting pending transactions that modify instance ownership or service assignments. A developer might query all pending party changes for a specific instance to understand the full scope of a transaction. For example:

• SELECT tpd.relationship_type_code, hp.party_name, tpd.instance_party_id FROM csi_t_party_details tpd, hz_parties hp WHERE tpd.party_source_id = hp.party_id AND tpd.txn_line_detail_id IN (SELECT txn_line_detail_id FROM csi_t_txn_line_details WHERE instance_id = <INSTANCE_ID>);

Another common scenario involves validating data before transaction submission by checking for required contacts associated with a primary party record within the same transaction, leveraging the CONTACT_PARTY_ID self-reference. Reporting on the volume and types of pending party changes by relationship type is also a frequent operational need.

Related Objects

CSI_T_PARTY_DETAILS is centrally connected to several key Install Base objects. It is a direct child of CSI_T_TXN_LINE_DETAILS and serves as the parent table for CSI_T_PARTY_ACCOUNTS, which holds transactional account details for parties. Its structure is defined by master data tables: HZ_PARTIES for the party entity, CSI_I_PARTIES for existing instance-party relationships, and CSI_IPA_RELATION_TYPES for valid relationship codes. The transactional data in this table is ultimately processed by concurrent programs or APIs that merge it into the permanent Install Base tables, such as CSI_I_PARTIES.