Search Results igi_dos_trx_headers_hist




Overview
Explore in AI Chat

Overview

The table IGI.IGI_DOS_TRX_HEADERS_HIST is a historical transaction header table within the Oracle E-Business Suite product IGI – Public Sector Financials International. It stores historical transaction header information associated with the IGI Document On-line System (DOS) functionality, which supports public sector financials processing such as commitment control, funds checking, and document tracking. In Oracle EBS releases 12.1.1 and 12.2.2 the object is documented as VALID, owned by the IGI schema, and exposes 49 physical columns.

The table records the historical state of transaction headers. Each row represents a preserved version of a transaction header, retained so that prior document states, statuses, and attribute values remain queryable after the live record has moved forward. From a data modeling perspective, the ETRM metadata returns a heuristic Data Vault classification of satellite-leaning. This classification should be treated as a modeling suggestion: the table behaves like a satellite structure, capturing descriptive, time-relevant attributes attached to a parent business key, rather than acting as an independent hub or a linking table between multiple hubs. The presence of audit columns and a large ATTRIBUTE1 through ATTRIBUTE30 (DESC) block further reinforces the satellite interpretation, since descriptive and reference attributes dominate the row shape.

Key Information Stored

The table's primary key is defined by the constraint IGI_DOS_TRX_HEADERS_HIST_PK on the column HISTORY_TRX_ID, which acts as the surrogate identifier for each historical row. A unique index, IGI_DOS_TRX_HEADERS_HIST_U1, also exists on HISTORY_TRX_ID, making it the principal business-key candidate in the documented schema.

Among the 49 columns, the most operationally significant include:

  • TRX_ID — the identifier of the originating transaction header; used to relate historical rows back to their live counterpart.
  • TRX_NUMBER — the human-readable transaction number used in reporting and reconciliation.
  • DOSSIER_ID and DOSSIER_NAME — identify the dossier (document type) associated with the transaction.
  • DOSSIER_TRANSACTION_NAME — the descriptive name of the transaction within its dossier.
  • TRX_STATUS and FUNDS_STATUS — status flags capturing workflow and funds-checking state at the time of archival.
  • SOB_ID — the Set of Books identifier, tying the record to a specific accounting context.
  • PACKET_ID — groups related transactions processed together.
  • PARENT_TRX_ID and PARENT_TRX_NUMBER — establish hierarchical linkage to a parent transaction.
  • DESCRIPTION and ATTRIBUTE_CATEGORY — free-form and descriptive fields.
  • ATTRIBUTE1 through ATTRIBUTE30 — the DFF (Descriptive Flexfield) segment block supporting customer-specific extensions.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — standard Oracle EBS Who columns for audit traceability.

Common Use Cases and Queries

Typical reporting and reconciliation scenarios retrieve the prior state of a transaction by joining the history row to the live header on TRX_ID. A representative query pattern:

SELECT h.HISTORY_TRX_ID, h.TRX_ID, h.TRX_NUMBER,
       h.TRX_STATUS, h.FUNDS_STATUS, h.CREATION_DATE
FROM   IGI.IGI_DOS_TRX_HEADERS_HIST h
WHERE  h.SOB_ID = :sob_id
AND    h.TRX_ID = :trx_id
ORDER BY h.CREATION_DATE;

Status-change auditing uses TRX_STATUS and FUNDS_STATUS to trace progression across versions. Funds control reporting filters on SOB_ID and FUNDS_STATUS to reconcile balances against archived states. Users also join child history tables such as IGI_DOS_TRX_SOURCES_HIST and IGI_DOS_TRX_DEST_HIST on HISTORY_TRX_ID to reconstruct complete historical documents.

Related Objects

  • IGI_DOS_TRX_DEST_HIST — references this table via HISTORY_TRX_ID; child destination history records.
  • IGI_DOS_TRX_SOURCES_HIST — references this table via HISTORY_TRX_ID; child source history records.
  • IGI_DOS_DOC_TYPES — parent table for the DOSSIER_ID foreign key.
  • The live transaction header table referenced by TRX_ID — the active counterpart maintained alongside this historical archive.

Together these objects form the archival backbone of IGI DOS transaction processing, enabling retention and auditability of public sector financial documents.