Results for “igi_dos_source_accounts”

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

Overview

APPS.IGI_DOS_SOURCE_ACCOUNTS is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, owned by the APPS schema and delivered by the IGI – Public Sector Financials International product. Its status is VALID in the ETRM metadata, indicating that the view is compiled and available for query. The view exposes a security-filtered, human-readable presentation of accounting flexfield combinations that are valid for a given source within a dossier. It exists primarily to support the Document on Source (DOS) functionality used by public sector implementations, where accounting distributions and source documents are validated against defined source ranges.

Functionally, the view answers the question: for a given source (identified by SOURCE_ID), which code combinations fall within the defined low/high concatenated segment bounds, and which segments should be masked because they are not visible or not updatable for that source? This makes the view relevant to both reporting and integration, particularly for LOVs, validation logic, and downstream processing that must respect segment-level visibility and updatability.

Underlying Base Objects

The ETRM metadata documents the view as being defined over four referenced objects:

• GL_CODE_COMBINATIONS_KFV (VIEW) – the key flexfield view that supplies the accounting flexfield segments and the concatenated segment string.
• IGI_DOS_DOC_TYPES (SYNONYM) – the DOS document types, joined via DOSSIER_ID.
• IGI_DOS_SOURCES (SYNONYM) – the DOS sources, providing SOURCE_ID, DOSSIER_ID and the segment range bounds SEGMENTS_LOW_CCID_DESC and SEGMENTS_HIGH_CCID_DESC.
• IGI_DOS_SOURCE_USAGES (SYNONYM) – self-joined six times (aliases SUSE1 through SUSE6) to obtain per-segment visibility and updatability attributes.

The joins enforce that the dossier identifier links document types to sources, that SOURCE_ID links the source to each segment usage row, and that SEGMENT_NAME equals SEGMENT1 through SEGMENT6 respectively. The range predicate constrains KFV.CONCATENATED_SEGMENTS between the source's low and high description bounds.

Key Columns

The SELECT list exposes the following significant columns:

• A derived, hyphen-separated masked segment string built from SEGMENT1 through SEGMENT6. Each segment is passed through DECODE(SUSE.VISIBILITY,'N',TRANSLATE(segment, segment,'X'), segment), so segments marked not visible are replaced with 'X'.
• SOURCE_ID – the DOS source identifier, the primary filter key and the value the user searched for.
• DOSSIER_ID – the dossier to which the document type and source belong.
• ROWID, CODE_COMBINATION_ID, CHART_OF_ACCOUNTS_ID, CONCATENATED_SEGMENTS – identifiers linking back to GL code combinations.
• SEGMENT1–SEGMENT6 and their paired UPDATABLE flags from each segment usage alias.

Common Use Cases and Queries

Typical usage includes validating that a code combination is permissible for a source, driving segment-level security in forms, and generating masked account displays for reporting. Because the view is DISTINCT, duplicate combination rows are eliminated.

Example: retrieve all valid, masked accounts for a specific source.

• SELECT SOURCE_ID, DOSSIER_ID, CONCATENATED_SEGMENTS, CODE_COMBINATION_ID, SEGMENT1 FROM APPS.IGI_DOS_SOURCE_ACCOUNTS WHERE SOURCE_ID = :p_source_id;

Example: identify accounts where the first segment is not updatable.

• SELECT SOURCE_ID, CONCATENATED_SEGMENTS FROM APPS.IGI_DOS_SOURCE_ACCOUNTS WHERE SEGMENT1_UPDATABLE = 'N';

These queries should be executed with the appropriate APPS responsibility context, since IGI DOS records are secured by dossier and operating unit.