Results for “igi_dos_source_usages_v”

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

Overview

IGI_DOS_SOURCE_USAGES_V is a validity-checked database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the IGI product family — Public Sector Financials International — which supplies the grants, funds control, and budgetary execution functionality layered over the core Oracle Financials applications. The view presents source-usage definitions that describe how specific segments of an accounting key are sourced, restricted, defaulted, or made available for entry when transaction data is captured by the IGI budgeting and funds-checking components.

The object is a thin, unmaterialized view: it projects rows and columns directly from its single base object with no joins, filters, aggregation, or analytical processing. Its principal role is to expose a stable, read-only presentation interface over the underlying table so that reports, concurrent programs, Oracle Forms blocks, and integration extracts can consume source-usage metadata without binding directly to the physical base table. A distinguishing feature is the use of ROWID as an exposed selection identifier, aliased in the documented column list as ROW_ID.

Underlying Base Objects

The view is defined exclusively over the synonym IGI_DOS_SOURCE_USAGES, which resolves within the APPS schema to the corresponding base object. The metadata records no additional referenced objects, so every column in the view maps one-to-one onto a column of that single base object. Consequently, the view inherits the base object's column semantics, data types, and constraints verbatim, and it exposes audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) exactly as stored.

Because the view is a pure projection, the base object remains the authoritative source for data definition and integrity rules. Consumers of the view should treat it as a naming and access layer rather than as a transformation: there is no filtering, no deduplication, and no decoding of code values into descriptions. Validation of the view status as VALID confirms that the underlying synonym resolves correctly and that the base object is present and accessible in the EBS 12.x environment.

Key Columns

• ROW_ID — the ROWID of the corresponding base row, exposed for row-level identification; useful for debugging and for locating the physical record.
• SOURCE_ID — the identifier of the source definition to which this usage record belongs, linking the usage to its parent source configuration.
• STORED_NAME — the internal, stored identifier name for the usage entry.
• SEGMENT_NAME / SEGMENT_NAME_DSP — the accounting segment (for example, an account or fund segment) and its display value.
• SOB_ID — the set of books identifier, anchoring the usage to a specific ledger context in 12.1.1 (and its ledger equivalents in 12.2.2).
• COA_ID — the chart of accounts identifier associated with the definition.
• VISIBILITY — controls whether the segment is presented to the user during entry.
• DEFAULT_TYPE / DEFAULT_VALUE — the defaulting mechanism and the value applied when the segment is defaulted.
• UPDATABLE — indicates whether the derived or defaulted value may be changed by the user.
• Audit columns — standard WHO columns recording creation and last update metadata.

Common Use Cases and Queries

Typical usage includes diagnosing why a segment defaults to a particular value, auditing which segments are hidden or read-only for a given source, and extracting configuration for migration between environments.

• List all usages for a source definition:
  SELECT source_id, stored_name, segment_name, default_type, default_value, updatable FROM igi_dos_source_usages_v WHERE source_id = :p_source_id;
• Identify non-updatable segments exposed to users:
  SELECT segment_name_dsp, visibility, updatable FROM igi_dos_source_usages_v WHERE sob_id = :p_sob_id ORDER BY segment_name_dsp;
• Audit recent configuration changes:
  SELECT stored_name, segment_name, last_updated_by, last_update_date FROM igi_dos_source_usages_v WHERE last_update_date > SYSDATE - 30;
• Extract defaulting rules per chart of accounts:
  SELECT coa_id, segment_name, default_type, default_value FROM igi_dos_source_usages_v WHERE default_type IS NOT NULL;

Reports and integrations should select from the view rather than the base object to preserve forward compatibility across EBS patch levels.