Search Results igi_dos_trx_dest_hist




Overview
Explore in AI Chat

Overview

IGI_DOS_TRX_DEST_HIST is a table in the IGI schema, owned by the Oracle E-Business Suite product IGI - Public Sector Financials International. Its documented purpose is to store historical destination transactions. It functions as the historical mirror of the destination transaction records maintained by the IGI Document on-Site (DOS) budgeting and funds-control feature set used by public sector organizations, typically capturing budget checking, funds reservation, and destination-level allocation activity for audit and reporting purposes.

The table is classified VALID in the ETRM 12.2.2 data dictionary and, per the documented physical schema, contains 77 columns. Based on the foreign key relationships mined from the ETRM metadata (a heuristic Data Vault classification), the object leans toward a satellite. It records descriptive and measurable attributes — budget amounts, funds available, balances, period and segment context — keyed by references to upstream transactional and dimensional tables, rather than acting as a hub or a pure link.

Key Information Stored

The most significant columns fall into several functional groups. The transaction identity columns include TRX_ID, the documented primary surrogate key DEST_TRX_ID, and HISTORY_TRX_ID, which anchors the row to the historical header record. Business context is supplied by DESTINATION_ID, SOURCE_ID, SOURCE_TRX_ID, DOSSIER_ID, CODE_COMBINATION_ID, PROFILE_CODE, and BUDGET_ENTITY_ID.

Financial and funds-control measures are held in BUDGET_AMOUNT, FUNDS_AVAILABLE, NEW_BALANCE, BUDGET_NAME, CURRENCY_CODE, PERCENTAGE, and STATUS. The MRC_ columns (for example MRC_BUDGET_AMOUNT, MRC_FUNDS_AVAIL, and MRC_NEW_BALANCE, each with associated exchange rate, rate type, exchange date, and exchange status fields) store reporting-currency equivalents for multi-reporting-currency environments.

Accounting period context is captured by PERIOD_NAME, PERIOD_YEAR, PERIOD_NUM, QUARTER_NUM, BUDGET_VERSION_ID, and SOB_ID. Descriptive accounting flexfield detail is stored in VISIBLE_SEGMENTS, ACTUAL_SEGMENTS, and the denormalized SEGMENT1 through SEGMENT30 columns. Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — complete the record. GROUP_ID and LINE_NUM provide grouping and sequencing.

Common Use Cases and Queries

Typical uses center on historical funds-control reconciliation, budget consumption reporting, and audit trails of past destination transactions. A common pattern joins the historical destination rows back to the current destination definition and to the historical transaction header:

  • Reconciling budget check results by destination and period for a given set of books.
  • Reporting historical funds available and new balance movements against a budget entity.
  • Auditing changes to destination-level allocations by comparing history to current records, restricted by LAST_UPDATE_DATE.
  • Multi-reporting-currency reporting using the MRC_ measure and exchange attribute sets.

Illustrative SQL: SELECT h.DEST_TRX_ID, h.DESTINATION_ID, h.BUDGET_AMOUNT, h.FUNDS_AVAILABLE, h.NEW_BALANCE, h.PERIOD_NAME FROM IGI.IGI_DOS_TRX_DEST_HIST h WHERE h.HISTORY_TRX_ID = :hist_trx_id ORDER BY h.LINE_NUM;

Related Objects

The documented foreign keys tie this table to several principal objects:

These relationships confirm that IGI_DOS_TRX_DEST_HIST serves as the historical detail layer beneath the DOS transaction header history, providing the destination-level financial detail needed for reporting and audit.