Search Results igi_dos_trx_headers_pk

Overview

IGI_DOS_TRX_HEADERS is a transaction header table owned by the IGI schema and delivered as part of the IGI – Public Sector Financials International product family in Oracle E-Business Suite releases 12.1.1 and 12.2.2. The table stores header-level information for transactions processed within the IGI Dossier (DOS) subsystem, which supports public sector financial management requirements such as funds control, commitments, obligations, and document tracking against dossiers.

From a dimensional modeling perspective, the documented foreign key pattern — a reference to a dossier identifier (DOSSIER_ID) plus a child table (IGI_DOS_TRX_DEST) that references the header through TRX_ID — suggests a satellite-leaning classification. This heuristic indicates that the table behaves primarily as a descriptive extension keyed by a surrogate identifier, rather than as a pure hub or link table, and should be modeled accordingly when building reporting or warehousing layers.

Key Information Stored

The table contains 48 documented columns. The most operationally significant include:

• TRX_ID — surrogate primary key, enforced by IGI_DOS_TRX_HEADERS_PK and also documented on the unique index IGI_DOS_TRX_HEADERS_U1. This is the primary join key to dependent tables.
• TRX_NUMBER — the user-facing transaction identifier, typically the business reference displayed in forms and reports.
• DOSSIER_ID — foreign key to the dossier master entity; the parent business key that anchors the transaction.
• DOSSIER_NAME — descriptive name of the dossier associated with the transaction.
• DOSSIER_TRANSACTION_NAME — the transaction type or template name assigned to the dossier transaction.
• TRX_STATUS — current workflow or processing status of the transaction header.
• FUNDS_STATUS — indicator of funds-check or funds-reservation outcome, central to public sector funds control.
• PACKET_ID — grouping identifier linking the transaction to a processing packet or batch.
• SOB_ID — set of books identifier, tying the record to a ledger context.
• PARENT_TRX_ID / PARENT_TRX_NUMBER — self-referencing parent linkage supporting hierarchical or adjustment transaction relationships.
• DESCRIPTION — free-text narrative for the transaction.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the standard Oracle EBS descriptive flexfield (DFF) columns, used for client-specific extensions.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture the standard who/when audit trail.

Common Use Cases and Queries

Typical usage centers on reporting transaction activity against dossiers, tracing funds status, and joining headers to their destination lines. A representative query to list open transactions for a dossier is:

• SELECT trx_id, trx_number, trx_status, funds_status FROM igi_dos_trx_headers WHERE dossier_id = :p_dossier_id AND trx_status = 'OPEN';
• Funds control reporting: aggregate counts of transactions by FUNDS_STATUS for a given set of books using GROUP BY sob_id, funds_status.
• Hierarchy resolution: self-join on child.parent_trx_id = parent.trx_id to walk adjustment chains.
• Packet reconciliation: group transactions by PACKET_ID to validate batch completeness.
• Flexfield reporting: join or filter on ATTRIBUTE_CATEGORY and the appropriate ATTRIBUTEn column for client-specific dimensions.

Related Objects

• IGI_DOS_TRX_DEST — the primary child table; joined via IGI_DOS_TRX_DEST.TRX_ID = IGI_DOS_TRX_HEADERS.TRX_ID, holding transaction destination or distribution detail lines.
• Dossier master entity (referenced by DOSSIER_ID) — the parent business object that groups transactions.
• IGI_DOS_TRX_HEADERS_PK / IGI_DOS_TRX_HEADERS_U1 — the primary key constraint and unique index on TRX_ID, which together define the access path for all dependent joins.
• Public sector funds control and commitment objects within the IGI/GL integration layer, linked through SOB_ID and FUNDS_STATUS.
• Standard audit and DFF configuration objects (descriptive flexfield definitions) that govern the ATTRIBUTE_CATEGORY/ATTRIBUTE1–30 columns.

In 12.1.1 and 12.2.2 the table is identical in structure; the primary difference lies in the surrounding multi-org and subledger accounting context rather than in IGI_DOS_TRX_HEADERS itself.