Search Results csi_ip_accounts_h




Overview
Explore in AI Chat

Overview

The CSI_IP_ACCOUNTS_H table is a core history table within the Oracle E-Business Suite Install Base (CSI) module, present in both releases 12.1.1 and 12.2.2. It serves as a permanent audit trail for changes made to the association between an installed product instance and its related party accounts. This table is fundamental for tracking the historical ownership, billing, and service relationships of assets over their lifecycle. When an account association for an instance is created, updated, or ended in the primary table (CSI_IP_ACCOUNTS), a corresponding historical record is inserted into CSI_IP_ACCOUNTS_H. This enables comprehensive reporting, auditing, and analysis of account assignment changes for support, financial, and compliance purposes.

Key Information Stored

The table's primary purpose is to capture the state of an account association at the moment of a change. Its structure is centered on a unique historical identifier and links to the source transaction and master record. The most critical columns include:

  • IP_ACCOUNT_HISTORY_ID: The primary key, a system-generated unique identifier for each historical entry.
  • IP_ACCOUNT_ID: A foreign key referencing the CSI_IP_ACCOUNTS table, identifying the specific master account association record that was modified.
  • TRANSACTION_ID: A foreign key referencing the CSI_TRANSACTIONS table, linking the historical record to the precise business event (e.g., a move, update, or split transaction) that triggered the change.
  • Additional columns (implied by its function) would typically capture the account details (e.g., party, account role, start date, end date) as they existed at the time of the transaction, along with standard who-columns (CREATED_BY, CREATION_DATE).

Common Use Cases and Queries

This table is essential for historical reporting and troubleshooting. A common use case is auditing the complete chain of account ownership for a specific installed asset. Support personnel may query it to determine which account was responsible for an asset on a given date for billing or service history. Financial audits may leverage it to verify asset accountability over time. A typical query pattern involves joining to the instance and transaction tables to provide context.

Sample SQL Pattern:
SELECT h.*, t.transaction_date, t.transaction_type_id
FROM csi_ip_accounts_h h,
     csi_ip_accounts a,
     csi_transactions t
WHERE a.instance_id = :p_instance_id
  AND h.ip_account_id = a.ip_account_id
  AND h.transaction_id = t.transaction_id
ORDER BY t.transaction_date;

Related Objects

The CSI_IP_ACCOUNTS_H table has defined foreign key relationships with two primary Install Base tables, forming a key part of the data model:

  • CSI_IP_ACCOUNTS: The master table for current instance-to-account associations. The join is made on the column CSI_IP_ACCOUNTS_H.IP_ACCOUNT_ID = CSI_IP_ACCOUNTS.IP_ACCOUNT_ID.
  • CSI_TRANSACTIONS: The central transaction log for all Install Base activities. The join is made on the column CSI_IP_ACCOUNTS_H.TRANSACTION_ID = CSI_TRANSACTIONS.TRANSACTION_ID. This link provides the business context (date, type, who) for each historical change.