Search Results igi_dos_trx_headers_u1

Overview

IGI.IGI_DOS_TRX_HEADERS is a transactional header table within the Oracle E-Business Suite Treasury (ETRM) module, owned by the IGI schema. The table stores header-level information for dossier transactions, which represent groupings of financial instruments, payments, or cash movements tracked against a dossier. Dossiers are the ETRM construct used to associate transactions with a specific counterparty, instrument, or portfolio for reporting and settlement purposes. This table is the anchor point for dossier transaction processing, providing the primary header record to which destination and detail rows are attached.

With 48 documented columns, the object is structured around a single-column surrogate primary key (TRX_ID) supplemented by an extensive descriptive flexfield (DFF) block spanning ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30, along with standard Who columns for auditability. Its heuristic Data Vault classification is satellite-leaning, which suggests the table functions primarily as a source of descriptive, context-dependent attributes attached to a transaction hub rather than as a hub or link itself. In a modeled warehouse, TRX_ID would typically act as the transaction business key referencing a central hub, while the descriptive columns would populate a satellite.

Key Information Stored

The principal identifier is TRX_ID, the surrogate primary key and the column on which the unique index IGI_DOS_TRX_HEADERS_U1 (tablespace APPS_TS_TX_IDX) is defined. Both IGI_DOS_TRX_HEADERS_PK and IGI_DOS_TRX_HEADERS_U1 are documented on TRX_ID, making it the definitive unique business-key candidate as well as the access path for most queries.

• SOB_ID — Set of Books identifier, establishing the ledger context for the dossier transaction.
• TRX_NUMBER — The externally visible dossier transaction number (VARCHAR2 40), commonly used as a user-facing reference.
• DOSSIER_ID — Foreign key to the dossier definition; the primary grouping attribute for the transaction.
• DOSSIER_NAME and DOSSIER_TRANSACTION_NAME — Descriptive labels (60 and 80 characters respectively) for the dossier and the transaction within it.
• PACKET_ID — Identifies the packet with which the transaction is associated, supporting batch or settlement grouping.
• TRX_STATUS — Current lifecycle state of the dossier transaction (VARCHAR2 30).
• FUNDS_STATUS — Funds status of the dossier, indicating whether funds are confirmed, pending, or otherwise dispositioned.
• DESCRIPTION — Free-text description (80 characters).
• PARENT_TRX_ID and PARENT_TRX_NUMBER — Self-referencing columns that support hierarchical or generated transactions linked to a parent.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — Descriptive flexfield segments (each VARCHAR2 150) enabling client-specific extensions without schema change.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Who columns for audit and change tracking.

Common Use Cases and Queries

The most frequent access pattern resolves a transaction by its business number or status. A typical lookup filters on TRX_NUMBER or TRX_STATUS and joins to the destination table to retrieve line-level settlement detail. Because TRX_ID is unique and indexed, point queries on this column are optimal.

A representative query selects the header attributes for a given dossier and set of books:

• SELECT h.trx_id, h.trx_number, h.dossier_name, h.trx_status, h.funds_status FROM igi.igi_dos_trx_headers h WHERE h.dossier_id = :dossier_id AND h.sob_id = :sob_id AND h.trx_status = 'ACTIVE';
• SELECT h.trx_number, d.* FROM igi.igi_dos_trx_headers h, igi.igi_dos_trx_dest d WHERE h.trx_id = d.trx_id AND h.trx_number = :trx_number;

Reporting use cases include reconciliation of dossier transactions by funds status, aging analysis using CREATION_DATE and LAST_UPDATE_DATE, DFF-driven extracts for regulatory reporting by querying ATTRIBUTE_CATEGORY and specific ATTRIBUTE segments, and parent-child rollups using PARENT_TRX_ID. Auditors frequently use the Who columns to trace who created or last modified a transaction and when.

Related Objects

The most significant dependent object is IGI.IGI_DOS_TRX_DEST, which references IGI_DOS_TRX_HEADERS.TRX_ID as a foreign key and holds destination or distribution-level detail for each header. The DOSSIER_ID column links to the dossier definition table, providing the dossier master context. The PARENT_TRX_ID column implicitly joins back to the same table for hierarchical transactions. In practice, ETRM dossier transaction processing also draws on the packet identifier to relate headers to packet, settlement, and accounting entry tables within the IGI schema, and on the set of books identifier to relate to the ledger. Because the DFF attributes are exposed through the standard descriptive flexfield mechanism, they are surfaced through the FND descriptive flexfield views native to the E-Business Suite.