Results for “actual_segments”

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

Overview

IGI_DOS_TRX_SOURCES_HIST is a table in the IGI schema (Public Sector Financials International) within Oracle EBS 12.1.1 and 12.2.2. It stores historical source transactions used by the IGI budgetary control and funds-checking engine to record the transactions that influenced budget balances, funds availability, and dossier processing. In effect, it acts as the archival counterpart to the operative source-transaction table, preserving prior states of each source record for audit, reconciliation, and year-end reporting across multiple sets of books.

From a Data Vault modeling heuristic, the FK structure suggests a satellite-leaning classification: the table is dominated by descriptive and monetary attributes tied to a source transaction identity, with limited outward referencing. This classification should be treated as a modeling suggestion rather than a binding design assertion.

Key Information Stored

The table contains 75 documented columns. The most operationally significant are:

• TRX_ID – primary identifier of the historical transaction record.
• SOURCE_TRX_ID – business-key reference to the originating source transaction; also participates in a self-referencing foreign key.
• SOURCE_ID and LINE_NUM – identify the specific source document and line.
• HISTORY_TRX_ID – FK to IGI_DOS_TRX_HEADERS_HIST, linking the row to its historical transaction header.
• DOSSIER_ID – FK to IGI_DOS_DOC_TYPES, identifying the dossier or document type context.
• BUDGET_ENTITY_ID – FK to GL_BUDGET_ENTITIES, tying the transaction to a budget entity.
• CODE_COMBINATION_ID – accounting flexfield combination affected by the transaction.
• BUDGET_AMOUNT, FUNDS_AVAILABLE, NEW_BALANCE – core funds-checking amounts before and after the transaction.
• CURRENCY_CODE and the MRC_* columns – currency and multiple reporting currency (MRC) equivalents for budget, funds available, and new balance, including exchange rates and rate types.
• PERIOD_NAME, PERIOD_YEAR, QUARTER_NUM, PERIOD_NUM – period context for budgetary reporting.
• STATUS, PROFILE_CODE, BUDGET_NAME, BUDGET_VERSION_ID – transaction state and budget profile metadata.
• SEGMENT1 through SEGMENT30 – denormalized accounting flexfield segment values.
• WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) – audit tracking.

TRX_ID serves as the surrogate primary key, while SOURCE_TRX_ID combined with related source identifiers represents the principal business-key candidate.

Common Use Cases and Queries

Typical usage centers on funds-checking audits, budget reconciliation, and historical balance reporting. A common pattern joins the table to its historical header and budget entity:

• Reconciling NEW_BALANCE against current budget balances for a given PERIOD_NAME and BUDGET_ENTITY_ID.
• Tracing a source transaction lineage via SOURCE_TRX_ID or HISTORY_TRX_ID.
• Reporting MRC-equivalent amounts by CURRENCY_CODE for multi-currency consolidation.
• Auditing STATUS transitions and SEGMENT-level impact over time.

Sample query pattern: SELECT t.SOURCE_TRX_ID, t.BUDGET_AMOUNT, t.FUNDS_AVAILABLE, t.NEW_BALANCE FROM IGI.IGI_DOS_TRX_SOURCES_HIST t WHERE t.BUDGET_ENTITY_ID = :entity AND t.PERIOD_NAME = :period ORDER BY t.CREATION_DATE DESC;

Related Objects

• IGI_DOS_TRX_HEADERS_HIST – joined on HISTORY_TRX_ID; provides historical header context.
• GL_BUDGET_ENTITIES – joined on BUDGET_ENTITY_ID; defines budget entity.
• IGI_DOS_DOC_TYPES – joined on DOSSIER_ID; identifies dossier/document type.
• IGI_DOS_TRX_SOURCES_HIST (self) – self-referencing FK via SOURCE_TRX_ID.
• GL_CODE_COMBINATIONS – joined on CODE_COMBINATION_ID for accounting flexfield detail.
• GL_BUDGETS / GL_BUDGET_VERSIONS – joined via BUDGET_NAME and BUDGET_VERSION_ID for budget definition context.