Search Results csi_t_party_accounts




Overview
Explore in AI Chat

Overview

The CSI_T_PARTY_ACCOUNTS table is a core transactional table within the Oracle E-Business Suite Install Base (CSI) module. It functions as a junction table that manages the real-time associations between serviceable product instances and their related customer accounts, specifically during transaction processing. Its primary role is to capture and maintain the detailed relationships between a serviceable item (instance) and the various parties (accounts) involved with it, such as the owner, bill-to, or ship-to contacts, as those relationships are created or updated through business flows like service requests, asset transfers, or installations. This table is essential for maintaining accurate and auditable account-party relationships for installed products throughout their lifecycle.

Key Information Stored

The table's structure is designed to link transactional detail records to specific account relationships. The primary key, TXN_ACCOUNT_DETAIL_ID, uniquely identifies each association record. The foreign key column TXN_PARTY_DETAIL_ID links to the CSI_T_PARTY_DETAILS table, anchoring the account association to a specific transaction line for a party. The ACCOUNT_ID column references HZ_CUST_ACCOUNTS, storing the identifier for the Trading Community Architecture (TCA) customer account. For relationships governed by predefined Install Base rules, the IP_ACCOUNT_ID links to the CSI_IP_ACCOUNTS table, and the RELATIONSHIP_TYPE_CODE defines the nature of the association (e.g., OWNER, BILL_TO) by referencing the CSI_IPA_RELATION_TYPES table.

Common Use Cases and Queries

A primary use case is auditing the history of account assignments for a specific installed product instance. Support or asset management personnel often query this table to determine who was the billed owner of an item at a given point in time. Another critical use is during transaction processing, where the Install Base engine queries and inserts into this table to establish new party-account links. A common reporting query involves joining to instance and party details to list all current account relationships for active instances.

  • Sample Query Pattern: SELECT cpa.relationship_type_code, hca.account_number, hca.account_name FROM csi_t_party_accounts cpa, hz_cust_accounts hca, csi_t_party_details cpd WHERE cpa.account_id = hca.cust_account_id AND cpa.txn_party_detail_id = cpd.txn_party_detail_id AND cpd.instance_id = :p_instance_id ORDER BY cpd.transaction_date DESC;

Related Objects

The CSI_T_PARTY_ACCOUNTS table is centrally connected to several key Install Base and TCA entities through documented foreign key constraints. These relationships are fundamental for data integrity and application logic.

  • CSI_T_PARTY_DETAILS: Linked via CSI_T_PARTY_ACCOUNTS.TXN_PARTY_DETAIL_ID. This is the primary parent table, providing the transactional context for the party.
  • HZ_CUST_ACCOUNTS: Linked via CSI_T_PARTY_ACCOUNTS.ACCOUNT_ID. This connects the association to the definitive Trading Community customer account record.
  • CSI_IP_ACCOUNTS: Linked via CSI_T_PARTY_ACCOUNTS.IP_ACCOUNT_ID. This references the Install Base's master definition of valid account-party relationships.
  • CSI_IPA_RELATION_TYPES: Linked via CSI_T_PARTY_ACCOUNTS.RELATIONSHIP_TYPE_CODE. This provides the valid list of relationship codes (e.g., OWNER, BILL_TO) used to classify the association.