Results for “igi_dos_destination_usages”

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

Overview

The IGI_DOS_DESTINATION_USAGES table is a component of the Oracle E-Business Suite product IGI — Public Sector Financials International. As documented in the ETRM repository for release 12.2.2 (with equivalent availability in 12.1.1), the table records usages of the destinations defined within the IGI Destination/Organization Structure (DOS) framework. Its role is to associate a configured destination with the accounting flexfield segments and ledger context under which that destination is valid, thereby governing how destination-based data is presented and consumed by downstream public sector financials functionality.

From a data-modeling perspective, the FK-derived Data Vault classification heuristically suggests a satellite-leaning object. In Data Vault terms, a satellite stores descriptive, time-variant attributes that hang off a hub or link; the single foreign key on DESTINATION_ID pointing to the parent destination entity supports this interpretation, while the presence of audit columns (CREATION_DATE, LAST_UPDATE_DATE and their system-user counterparts) reinforces the descriptive, mutable nature of the record set. This classification is a modeling suggestion only and should be validated against the complete IGI data model.

Key Information Stored

The table is defined in the IGI schema and, per the documented physical schema, contains 14 columns. The most significant columns for functional and query purposes are:

• DESTINATION_ID — The foreign key referencing the parent destination definition. This is the primary join column to the destination master data and forms the leading column of the unique business-key index.
• SEGMENT_NAME — Identifies the accounting flexfield segment associated with the destination usage. Together with DESTINATION_ID it constitutes the unique business-key candidate (index IGI_DOS_DESTINATION_USAGES_U1).
• SEGMENT_NAME_DSP — The display form of the segment name, used for user-facing presentation.
• SOB_ID — The Set of Books identifier, anchoring the usage to a specific ledger/book context in 12.1.1 terminology.
• COA_ID — The Chart of Accounts identifier, defining the accounting structure against which the segment is interpreted.
• VISIBILITY — Controls whether the destination/segment usage is exposed to users.
• DEFAULT_TYPE and DEFAULT_VALUE — Define defaulting behavior for the usage, specifying how and what value is applied by default.
• UPDATABLE — Indicates whether the usage record may be modified.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard EBS who/when auditability.

Note that no surrogate system-generated primary key column is documented; the unique index IGI_DOS_DESTINATION_USAGES_U1 on (DESTINATION_ID, SEGMENT_NAME) serves as the business-key candidate.

Common Use Cases and Queries

Typical usage centers on resolving which accounting segments and ledgers a given destination is active for, and how defaulting behaves. A representative query joins usages to their parent destination:

• Listing all segment usages for a destination: SELECT u.DESTINATION_ID, u.SEGMENT_NAME, u.SEGMENT_NAME_DSP, u.SOB_ID, u.COA_ID FROM IGI.IGI_DOS_DESTINATION_USAGES u WHERE u.DESTINATION_ID = :destination_id;
• Filtering by ledger and chart of accounts: add WHERE u.SOB_ID = :sob_id AND u.COA_ID = :coa_id.
• Reporting defaulting rules: select DEFAULT_TYPE, DEFAULT_VALUE, UPDATABLE where VISIBILITY indicates an active usage.
• Audit and change tracking: order by LAST_UPDATE_DATE to identify recently modified usage records.

Related Objects

Relationships are defined chiefly through the foreign key on DESTINATION_ID. The most significant related objects are:

• Parent destination entity (referenced by IGI_DOS_DESTINATION_USAGES.DESTINATION_ID) — the master destination definition this table extends.
• IGI_DOS_DESTINATIONS — the likely destination master joined on DESTINATION_ID.
• FND_ID_FLEX_SEGMENTS / FND_ID_FLEX_STRUCTURES — key flexfield metadata underpinning SEGMENT_NAME and COA_ID.
• GL_SETS_OF_BOOKS / GL_LEDGERS — resolve SOB_ID to ledger context.
• GL_CODE_COMBINATIONS — chart of accounts context for COA_ID.
• FND_USER — resolves CREATED_BY and LAST_UPDATED_BY audit identifiers.

Consult the complete IGI DOS entity set in the ETRM repository to confirm inverse relationships and dependent views or concurrent programs.