Results for “igi_dos_trx_dest_u1”

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

Overview

IGI.IGI_DOS_TRX_DEST is a transactional table in the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 environment, residing in the IGI schema (the schema associated with the Public Sector / Federal Financials "IGI" product family, which includes the Dossier and Funds Control functionality). The table stores destination transaction entries that act as the balancing side of a source transaction posting. In double-entry funds-control processing, every source transaction recorded against a source of funds must be offset by a corresponding destination entry; IGI_DOS_TRX_DEST captures that offsetting side together with the budget impact it produces.

Physically, the table is stored in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. The documented physical schema in ETRM 12.2.2 lists 76 columns. Its unique index, IGI_DOS_TRX_DEST_U1, is defined on the DEST_TRX_ID column and is hosted in the APPS_TS_TX_IDX tablespace. The primary key constraint, IGI_DOS_TRX_DEST_PK, is likewise defined on DEST_TRX_ID.

From a dimensional modeling perspective, the mined Data Vault classification for this object is link. This is a heuristic suggestion rather than an enforced model: the table behaves as an associative structure connecting a transaction header, a source transaction, and a destination, while carrying descriptive and financial-measure attributes. Where the funds-control ledger requires historical tracking of budget, funds-available, and new-balance values, those measures are typically audited through satellites rather than held as the anchor of the link.

Key Information Stored

The surrogate primary key of the table is DEST_TRX_ID, which is also the sole business-key candidate exposed through the unique index IGI_DOS_TRX_DEST_U1. The remaining columns fall into three functional groups.

• SOB_ID — the Set of Books identifier that scopes every row to a ledger.
• TRX_ID — foreign reference to the transaction header in IGI_DOS_TRX_HEADERS.
• SOURCE_TRX_ID — the originating source transaction entry, referencing IGI_DOS_TRX_SOURCES.
• SOURCE_ID — the source-of-funds identifier associated with the entry.
• DESTINATION_ID — foreign reference to IGI_DOS_DESTINATIONS, identifying the destination fund or account.
• CODE_COMBINATION_ID — the accounting flexfield combination that receives the posting.
• BUDGET_ENTITY_ID — foreign reference to GL_BUDGET_ENTITIES, tying the line to a specific budget entity.
• BUDGET_AMOUNT, FUNDS_AVAILABLE, and NEW_BALANCE — the principal financial measures produced by the destination posting.
• CURRENCY_CODE — the currency in which those measures are expressed.
• PROFILE_CODE and BUDGET_NAME — descriptive attributes identifying the funds-control profile and budget.
• VISIBLE_SEGMENTS / ACTUAL_SEGMENTS — the concatenated accounting segment strings, stored up to 2,000 characters.
• DOSSIER_ID, PERIOD_NAME, PERIOD_YEAR, and PERIOD_NUM — the dossier and accounting-period context of the transaction.
• STATUS and PERCENTAGE — the processing state of the destination record and any allocation percentage applied.

Numerous MRC_* columns (for example MRC_BUDGET_AMOUNT, MRC_FUNDS_AVAIL, MRC_NEW_BALANCE, each with exchange rate, rate type, date, and status companions) carry the Multi-Reporting Currencies equivalent of the primary currency measures. The SEGMENT1 through SEGMENT30 columns persist individual accounting flexfield segments, and the standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) record row provenance.

Common Use Cases and Queries

The most frequent access pattern is reconciliation: confirming that each source transaction is offset by exactly one destination entry and that the budget impact nets to zero. A representative query joins the table to its transaction header and destination master:

• Joining IGI_DOS_TRX_DEST to IGI_DOS_TRX_HEADERS on TRX_ID to report destination activity per transaction.
• Joining to IGI_DOS_DESTINATIONS on DESTINATION_ID to attribute budget consumption to a named destination.
• Aggregating BUDGET_AMOUNT, FUNDS_AVAILABLE, and NEW_BALANCE by SOB_ID, PERIOD_NAME, and DESTINATION_ID for funds-availability reporting.
• Filtering by DOSSIER_ID to reproduce the destination side of a specific dossier.
• Comparing CURRENCY_CODE-denominated measures against the MRC_* counterparts to validate multi-currency translation.
• Detecting orphaned entries via a LEFT OUTER JOIN from IGI_DOS_TRX_SOURCES on SOURCE_TRX_ID where DEST_TRX_ID IS NULL.
• Point-in-time auditing by constraining on LAST_UPDATE_DATE and querying the WHO columns.

Because DEST_TRX_ID is a numeric surrogate and the unique index is a single-column index, lookups by DEST_TRX_ID are the most efficient access path. Filtering by TRX_ID or SOURCE_TRX_ID is supported through the foreign-key relationships described below.

Related Objects

• IGI.IGI_DOS_TRX_HEADERS — referenced through TRX_ID; the header record for the transaction to which the destination line belongs.
• IGI.IGI_DOS_TRX_SOURCES — referenced through SOURCE_TRX_ID; the balanced source-side entry.
• IGI.IGI_DOS_DESTINATIONS — referenced through DESTINATION_ID; the destination master definition.
• GL.GL_BUDGET_ENTITIES — referenced through BUDGET_ENTITY_ID; defines the budget entity against which funds are reserved.
• IGI_DOS_TRX_DEST_PK / IGI_DOS_TRX_DEST_U1 — the primary key constraint and unique index on DEST_TRX_ID.
• IGI.IGI_DOS_DOSSIERS — implicitly related through DOSSIER_ID, grouping destination entries by dossier.

No documented forms, concurrent programs, or PL/SQL APIs were supplied with the ETRM excerpt; the objects above are confined to those evidenced by the provided foreign-key and index metadata.