Search Results igi_dos_destinations_u1

Overview

IGI.IGI_DOS_DESTINATIONS is a transactional configuration table within the Oracle E-Business Suite Public Sector / Financials dossier management schema (IGI). It stores the destination lines defined against a dossier type, captured through the Dossier Types Setup screen. Each row associates a dossier with a source, a destination, and an accounting flexfield (Key Flexfield) range expressed as low/high segment pairs, along with an optional budget and budget entity. In Oracle EBS 12.1.1 and 12.2.2 the table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and its indexes live in APPS_TS_TX_IDX.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this object heuristically as a link. The table resolves associations between multiple reference entities — dossier types, sources, and GL budget entities — rather than acting as a standalone hub or a descriptive satellite. Implementers designing a dimensional or Data Vault abstraction should treat IGI_DOS_DESTINATIONS as the connective artifact joining those business keys.

Key Information Stored

The physical schema (documented for 12.2.2) contains 79 columns; the most operationally significant are summarized below.

• DESTINATION_ID — Surrogate primary key. Enforced by the unique index IGI_DOS_DESTINATIONS_U1 (type NORMAL, uniqueness UNIQUE) on APPS_TS_TX_IDX. This is the business-key candidate referenced by all downstream tables.
• DOSSIER_ID — Dossier identifier; foreign key to IGI_DOS_DOC_TYPES. Identifies the dossier type against which the destination is defined.
• SOURCE_ID — Source identifier; foreign key to IGI_DOS_SOURCES. Indexed non-uniquely by IGI_DOS_DESTINATIONS_N1.
• BUDGET_ENTITY_ID and BUDGET_ENTITY_NAME — Budget entity identifier (FK to GL_BUDGET_ENTITIES) and its descriptive name. Indexed non-uniquely by IGI_DOS_DESTINATIONS_N2.
• SOB_ID and COA_ID — Set of Books identifier and Chart of Accounts identifier, anchoring the accounting context.
• BUDGET and BUDGET_VERSION_ID — Budget name and version context for the destination line.
• SEGMENT1_LOW/HIGH … SEGMENT30_LOW/HIGH — Accounting Key Flexfield range columns. Each flexfield segment is stored as a low/high pair (VARCHAR2(30)) defining an inclusive account range for the destination.
• SEGMENTS_LOW_CCID / SEGMENTS_HIGH_CCID and their _DESC companions — Pre-resolved code combination identifiers and descriptions for the low and high ends of the flexfield range.
• LINE_NUM — Ordering attribute for destination lines within a dossier.
• Standard WHO audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical reporting and validation scenarios include reconciling dossier destinations to their sources and budget entities, and validating flexfield ranges for account derivation.

• Retrieve all destinations for a dossier type:

  SELECT d.destination_id, d.dossier_id, d.source_id, d.budget_entity_name FROM igi.igi_dos_destinations d WHERE d.dossier_id = :p_dossier_id ORDER BY d.line_num;

• Join destinations to their sources and budget entities:

  SELECT d.destination_id, s.source_name, d.budget_entity_name FROM igi.igi_dos_destinations d, igi.igi_dos_sources s, gl_budget_entities b WHERE d.source_id = s.source_id AND d.budget_entity_id = b.budget_entity_id;

• Trace downstream transaction usage via the history table:

  SELECT h.* FROM igi.igi_dos_trx_dest_hist h WHERE h.destination_id = :p_destination_id;

The unique index IGI_DOS_DESTINATIONS_U1 guarantees single-row lookup by DESTINATION_ID, making it the preferred access path for point queries and for FK joins from dependent transaction and FTE tables.

Related Objects

• IGI.IGI_DOS_DOC_TYPES — joined on IGI_DOS_DESTINATIONS.DOSSIER_ID; parent dossier type definition.
• IGI.IGI_DOS_SOURCES — joined on IGI_DOS_DESTINATIONS.SOURCE_ID; source master.
• GL_BUDGET_ENTITIES — joined on IGI_DOS_DESTINATIONS.BUDGET_ENTITY_ID; budget entity reference.
• IGI.IGI_DOS_TRX_DEST and IGI.IGI_DOS_TRX_DEST_HIST — depend on DESTINATION_ID; transaction destination and history records.
• FTE_LANE_GROUP_COMPONENTS, FTE_LANE_VEHICLES, FTE_MILE_DOWNLOAD_LINES — FTE objects referencing DESTINATION_ID.
• HR_DM_RESOLVE_PKS — references DESTINATION_ID in HR data-merge resolution.