Search Results csi_systems_h




Overview
Explore in AI Chat

Overview

The CSI_SYSTEMS_H table is a core history table within the Oracle E-Business Suite Install Base (CSI) module. It serves as the primary audit and historical repository for changes made to tracked assets, or "systems," in the application. Every time a significant transaction or update is applied to a system record in the main transactional table (CSI_SYSTEMS_B), a corresponding historical snapshot is typically created in CSI_SYSTEMS_H. This enables comprehensive tracking of a system's lifecycle, including changes to its configuration, location, status, and ownership over time, which is critical for asset management, warranty tracking, service history, and compliance reporting.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the structure of a history table and the documented foreign keys indicate it contains several critical types of data. The primary key, SYSTEM_HISTORY_ID, uniquely identifies each historical record. The table holds a denormalized snapshot of a system's attributes (e.g., serial number, item, instance details) as they existed at a point in time. Crucially, it links this snapshot to two key entities: the SYSTEM_ID foreign key to CSI_SYSTEMS_B, which identifies the specific asset, and the TRANSACTION_ID foreign key to CSI_TRANSACTIONS, which identifies the business event (e.g., shipment, return, repair, update) that caused the historical record to be created. Other typical columns would include creation date and the user who performed the transaction.

Common Use Cases and Queries

The primary use case is auditing and reporting on the complete lifecycle of an installed asset. Support and service teams query this table to understand the sequence of events applied to a system, such as tracking all location changes or status transitions for troubleshooting. Financial and operational reports use it to analyze asset depreciation, warranty periods, or maintenance history. A common query pattern involves joining CSI_SYSTEMS_H with CSI_SYSTEMS_B for current details and CSI_TRANSACTIONS for transaction context.

SELECT csh.system_id,
       csh.instance_number,
       csh.serial_number,
       ct.transaction_date,
       ct.transaction_type_id,
       ct.transaction_sub_type
FROM   csi_systems_h csh,
       csi_transactions ct
WHERE  csh.transaction_id = ct.transaction_id
AND    csh.system_id = :p_system_id
ORDER BY ct.transaction_date;

Related Objects

CSI_SYSTEMS_H is centrally connected to other core Install Base tables via documented foreign key relationships.

  • CSI_SYSTEMS_B: This is the main transactional table for system instances. The relationship is defined by CSI_SYSTEMS_H.SYSTEM_ID = CSI_SYSTEMS_B.SYSTEM_ID. Every historical record is for a specific system in this table.
  • CSI_TRANSACTIONS: This table logs all business events in Install Base. The relationship is defined by CSI_SYSTEMS_H.TRANSACTION_ID = CSI_TRANSACTIONS.TRANSACTION_ID. This join provides the "why" and "when" for each historical snapshot.

Additionally, CSI_SYSTEMS_H is likely referenced by various Install Base reports, interfaces, and product-specific history views within the EBS schema.