Search Results old_party_account_id




Overview
Explore in AI Chat

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

Overview

CSI_IP_ACCOUNTS_H is the audit and history table for the CSI_IP_ACCOUNTS association in the Oracle E-Business Suite Install Base (CSI) module. Whereas CSI_IP_ACCOUNTS stores the current relationship between an install base instance (item instance) and a party account — for example a customer account identified as bill-to, ship-to, or another relationship type — CSI_IP_ACCOUNTS_H preserves the full before-and-after image of every change made to those associations. Each row captures one versioned state transition of an instance-to-account link, written when the parent association is created, updated, or otherwise modified through Install Base transactions.

Because the table is keyed from the underlying association and transaction, it is a pure change-capture structure. From a dimensional modeling perspective, the ETRM metadata classifies this object heuristically as a link (Data Vault classification). This reflects the fact that each row associates two business entities — a party account and a transaction — and, through its OLD_/NEW_ paired columns, records the deltas applied to that association over time. The table is owned by the CSI schema and contains 58 documented columns in the 12.2.2 physical schema.

Key Information Stored

The central identity of a history row is its surrogate primary key, IP_ACCOUNT_HISTORY_ID, defined by the primary key constraint CSI_IP_ACCOUNTS_H_PK and also enforced by unique index CSI_IP_ACCOUNTS_H_U01. This is the column referenced by the user search term "ip_account_history_id" and is the recommended column for point lookups and for joining history rows back to a specific change event.

Two business-key candidates are documented. Unique index CSI_IP_ACCOUNTS_H_U02 spans TRANSACTION_ID and IP_ACCOUNT_ID, meaning a given association may appear at most once per change transaction; this makes the pair a reliable natural key for correlating history to the driving Install Base transaction.

The most important content columns are the OLD_ and NEW_ paired fields that describe the state before and after the change:

Common Use Cases and Queries

The primary reporting scenario is reconstructing the audit trail of an instance-to-account association. Analysts join history rows to the live association and to transaction records to determine who changed an account relationship, when, and under which transaction:

  • Point lookup by surrogate key: SELECT * FROM csi.csi_ip_accounts_h WHERE ip_account_history_id = :id;
  • Full change history for one association: select all rows sharing the same IP_ACCOUNT_ID, ordered by CREATION_DATE.
  • Reconciliation by transaction: query on TRANSACTION_ID (usable via index CSI_IP_ACCOUNTS_H_U02 in combination with IP_ACCOUNT_ID) to list every association affected by a given Install Base transaction.
  • Account reassignment reporting: filter rows where OLD_PARTY_ACCOUNT_ID differs from NEW_PARTY_ACCOUNT_ID to identify accounts moved between customers.
  • Effective-dating and status reconstruction: compare OLD_/NEW_ pairs on the active start/end date columns to rebuild the relationship timeline as of a past date.

Because of the high column count (58), selective column lists are strongly recommended in reporting queries to avoid unnecessary I/O.

Related Objects

  • CSI_IP_ACCOUNTS — the current-state parent table; joined on CSI_IP_ACCOUNTS_H.IP_ACCOUNT_ID = CSI_IP_ACCOUNTS.IP_ACCOUNT_ID.
  • CSI_TRANSACTIONS — the driving change transaction; joined on CSI_IP_ACCOUNTS_H.TRANSACTION_ID = CSI_TRANSACTIONS.TRANSACTION_ID.
  • FND_SECURITY_GROUPS — security partitioning; joined on CSI_IP_ACCOUNTS_H.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
  • CSI_IP_ACCOUNTS_H_PK / CSI_IP_ACCOUNTS_H_U01 / CSI_IP_ACCOUNTS_H_U02 — the primary key and unique indexes that enforce identity and the (TRANSACTION_ID, IP_ACCOUNT_ID) business key.
  • HZ_CUST_ACCOUNTS and related party model tables — referenced indirectly through the party account identifiers held in OLD_/NEW_PARTY_ACCOUNT_ID.
  • Install Base public APIs (CSI_IP_ACCOUNTS related) — the interface layer that inserts into CSI_IP_ACCOUNTS and consequently writes corresponding history rows into this table.