Search Results igi_dos_destinations_pk

Overview

IGI_DOS_DESTINATIONS is a transactional configuration table in the IGI (Public Sector Financials International) product family of Oracle E-Business Suite, resident in the IGI schema and valid in both 12.1.1 and 12.2.2. The table stores destination definitions associated with a dossier, providing the funding allocation targets — budget entities, account segment ranges, and budget versions — against which public sector commitments and obligations are recorded. It forms part of the Dossier (DOS) subsystem used for budget execution, funds control, and expenditure tracking in government and public sector implementations.

From a Data Vault modeling perspective, the FK structure suggests this object behaves as a link: it resolves associations between a dossier (IGI_DOS_DOC_TYPES via DOSSIER_ID), a source (IGI_DOS_SOURCES via SOURCE_ID), and a budget entity hierarchy (GL_BUDGET_ENTITIES via BUDGET_ENTITY_ID). It carries descriptive attributes but its principal purpose is to relate those entities together, hence the heuristic classification of link rather than hub or satellite.

Key Information Stored

The physical schema documents 79 columns. The surrogate primary key is DESTINATION_ID, backed by unique index IGI_DOS_DESTINATIONS_PK and business-key candidate IGI_DOS_DESTINATIONS_U1 (also on DESTINATION_ID). The most significant columns are:

• DESTINATION_ID — surrogate primary key and unique business key candidate.
• DOSSIER_ID — foreign key to IGI_DOS_DOC_TYPES, identifying the parent dossier.
• SOURCE_ID — foreign key to IGI_DOS_SOURCES, identifying the funding source.
• BUDGET_ENTITY_ID — foreign key to GL_BUDGET_ENTITIES defining the budget entity target.
• BUDGET_ENTITY_NAME — denormalized descriptive name of the budget entity.
• BUDGET, BUDGET_VERSION_ID, SOB_ID, COA_ID — budget name, version, set of books, and chart of accounts context.
• SEGMENT1_LOW … SEGMENT30_HIGH — low/high ranges across up to thirty account segments defining destination applicability.
• SEGMENTS_LOW_CCID, SEGMENTS_HIGH_CCID — concatenated segment code combination identifiers, with matching _DESC descriptions.
• LINE_NUM — ordering of destination lines within a dossier.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical usage centers on reporting which destinations are defined for a given dossier, resolving budget entity and segment ranges for funds checking, and auditing downstream transaction drill-downs. Representative query patterns:

• List destinations for a dossier: SELECT d.destination_id, d.dossier_id, d.budget_entity_name, d.budget FROM igi_dos_destinations d WHERE d.dossier_id = :dossier_id ORDER BY d.line_num;
• Join to source and dossier metadata: SELECT d.*, s.source_name FROM igi_dos_destinations d, igi_dos_sources s WHERE d.source_id = s.source_id;
• Resolve the budget entity: SELECT d.destination_id, be.name FROM igi_dos_destinations d, gl_budget_entities be WHERE d.budget_entity_id = be.budget_entity_id;
• Trace transactions to a destination via IGI_DOS_TRX_DEST.DESTINATION_ID.

Related Objects

• IGI_DOS_DOC_TYPES — parent dossier; join on DOSSIER_ID.
• IGI_DOS_SOURCES — funding source; join on SOURCE_ID.
• GL_BUDGET_ENTITIES — budget entity; join on BUDGET_ENTITY_ID.
• IGI_DOS_TRX_DEST — active transactions referencing DESTINATION_ID.
• IGI_DOS_TRX_DEST_HIST — historical transaction destinations.
• FTE_LANE_VEHICLES, FTE_LANE_GROUP_COMPONENTS, FTE_MILE_DOWNLOAD_LINES — FTE logistics objects referencing DESTINATION_ID.
• HR_DM_RESOLVE_PKS — resolution view/table referencing DESTINATION_ID.