Results for “igi_dos_bud_ass_cand_v”

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

Overview

IGI_DOS_BUD_ASS_CAND_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGI – Public Sector Financials International product family. The view exposes the set of "candidate" budget assignment accounts — that is, the detail, expenditure-type, non-summary code combinations that fall within the account ranges assigned to a given budget entity and budget version. Although the object itself is a reporting and integration convenience view rather than a base transaction table, it encapsulates the join logic between Oracle General Ledger budgeting entities and the chart of accounts, allowing downstream IGI functionality and inquiry screens to identify which accounts are legitimately addressable under a specific budget.

Because it presents a pre-joined, filtered projection over standard GL budget objects, the view is typically consumed by diagnostic queries, budget setup validation, and custom reporting in public sector implementations. Users searching for gl_entity_budgets will frequently arrive at this view, since GL_ENTITY_BUDGETS is one of its core underlying objects and is the table that binds a budget version to a budgeting entity.

Underlying Base Objects

The view is defined over a combination of GL budget tables, views, and synonyms. Per the documented view text, the FROM clause references:

• GL_BUDGETS (SYNONYM) – supplies BUDGET_NAME and BUDGET_TYPE, the budget definition itself.
• GL_BUDGET_VERSIONS (SYNONYM) – supplies BUDGET_VERSION_ID and links a budget name/type to a specific version.
• GL_ENTITY_BUDGETS (SYNONYM) – the association table that relates a budget version to a budget entity; it is joined via BUDGET_VERSION_ID and BUDGET_ENTITY_ID.
• GL_BUDGET_ENTITIES (SYNONYM) – provides BUDGET_ENTITY_ID and the entity name exposed as BUDGET_ENTITY_NAME.
• GL_BUDGET_ASSIGNMENT_RANGES_V (VIEW) – provides the SEGMENTn_LOW and SEGMENTn_HIGH range boundaries used to test which accounts belong to the entity.
• GL_CODE_COMBINATIONS_KFV (VIEW) – the key flexfield concatenated view that supplies CODE_COMBINATION_ID, CONCATENATED_SEGMENTS, GL_ACCOUNT_TYPE, SUMMARY_FLAG, and the individual segments used in the range predicate.

The joins are chained: BUDGET_NAME and BUDGET_TYPE link GL_BUDGETS to GL_BUDGET_VERSIONS; BUDGET_VERSION_ID links GL_BUDGET_VERSIONS to GL_ENTITY_BUDGETS; BUDGET_ENTITY_ID links GL_ENTITY_BUDGETS to GL_BUDGET_ENTITIES and to GL_BUDGET_ASSIGNMENT_RANGES_V; and the code combination is matched to the assignment range through a concatenated segment comparison.

Key Columns

• CODE_COMBINATION_ID – the unique identifier of the eligible account combination.
• CONCATENATED_SEGMENTS – the human-readable, dash-delimited account string from the key flexfield view.
• BUDGET_NAME – the name of the budget to which the candidate assignment belongs.
• BUDGET_ENTITY_ID – the identifier of the budgeting entity associated with the account.
• BUDGET_ENTITY_NAME – the descriptive name of that entity (aliased from GL_BUDGET_ENTITIES.NAME).
• CHART_OF_ACCOUNTS_ID – the chart of accounts to which the combination belongs, useful for multi-chart environments.

Common Use Cases and Queries

Typical uses include verifying that a budget entity's assignment ranges capture the intended expenditure accounts, troubleshooting why a given account is not selectable in budget entry, and generating lists of candidate accounts for integration feeds. Because the view already restricts results to GL_ACCOUNT_TYPE = 'E' and SUMMARY_FLAG <> 'Y', it returns only postable expense accounts.

A representative query lists all candidate accounts for a named budget:

• SELECT code_combination_id, concatenated_segments, budget_entity_name, budget_name FROM igi_dos_bud_ass_cand_v WHERE budget_name = :p_budget_name ORDER BY concatenated_segments;

To scope by entity and chart of accounts:

• SELECT concatenated_segments, budget_entity_id FROM igi_dos_bud_ass_cand_v WHERE budget_entity_id = :p_entity_id AND chart_of_accounts_id = :p_coa_id;

As with any view layered over GL budget objects, performance depends on the selectivity of the budget entity and range predicates; queries should always constrain budget name, entity, or chart to avoid full scans of the code combination view.