Results for “igi_bud_summary_combs_v”

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

Overview

IGI_BUD_SUMMARY_COMBS_V is an Oracle E-Business Suite (EBS) APPS schema view belonging to the IGI — Public Sector Financials International product family. It presents a denormalized, flattened representation of General Ledger code combination records joined with GL summary template information, exposing every accounting flexfield segment as an individual column. In Oracle EBS 12.1.1 and 12.2.2, this view serves as a reporting and integration surface for budget execution, funds control, and budgetary account derivation logic used by IGI public-sector features, which rely on full segment-level visibility of the accounting key rather than the composite concatenated description stored in GL_CODE_COMBINATIONS.

Underlying Base Objects

Per the ETRM documentation, the view is defined over two referenced base objects, both accessed through APPS synonyms:

• GL_CODE_COMBINATIONS (SYNONYM) — the Alias CC in the view text; supplies the segment columns, account type, posting flags, enabled and summary flags, template reference, and descriptive attributes.
• GL_SUMMARY_TEMPLATES (SYNONYM) — Alias T; supplies SET_OF_BOOKS_ID via the join through the code combination's TEMPLATE_ID.

The join links each code combination to its assigned summary template, allowing budget summary hierarchies to be resolved against the underlying chart of accounts. The view is therefore a read-only projection: DML against it is not supported, and it inherits the row-level security and security rules configured on its base tables.

Key Columns

• ROW_ID — the ROWID of the underlying GL_CODE_COMBINATIONS row, useful for correlated updates or precise row identification.
• SET_OF_BOOKS_ID — ledger identifier sourced from the summary template.
• CODE_COMBINATION_ID — primary key of the accounting combination.
• CHART_OF_ACCOUNTS_ID, ACCOUNT_TYPE, TEMPLATE_ID — structural and classification attributes used by IGI budget derivation.
• DETAIL_POSTING_ALLOWED_FLAG, DETAIL_BUDGETING_ALLOWED_FLAG, ENABLED_FLAG, SUMMARY_FLAG — control flags governing whether the combination may be posted, budgeted, or used as a summary (parent) account.
• SEGMENT1 through SEGMENT30 — each accounting flexfield segment value exposed as an individual column, enabling segment-specific filtering such as SEGMENT_ATTRIBUTE42 discovery.
• SEGMENT_ATTRIBUTE1 through SEGMENT_ATTRIBUTE20 — descriptive flexfield attribute values mapped to the Segment Attributes region.
• ATTRIBUTE1 through ATTRIBUTE10 and CONTEXT — standard descriptive flexfield context and attribute columns.
• DESCRIPTION, START_DATE_ACTIVE, END_DATE_ACTIVE, ALLOCATION_CREATE_FLAG, LAST_UPDATE_DATE, LAST_UPDATED_BY — maintenance and audit context.

Common Use Cases and Queries

The view is most often queried to resolve budget-eligible account combinations at segment granularity, to reconcile summary templates with detail accounts, or to expose accounting flexfield segments to IGI funds-control and appropriations reporting.

A query locating a specific segment attribute (for example, SEGMENT_ATTRIBUTE42, which appears only where the user-facing segment-attribute numbering extends beyond the documented SEGMENT_ATTRIBUTE1 to SEGMENT_ATTRIBUTE20 excerpt) would typically reference the highest available attribute columns exposed by the view in a given environment:

• SELECT code_combination_id, segment1, segment2, segment3, segment_attribute1 FROM igi_bud_summary_combs_v WHERE set_of_books_id = :p_sob AND detail_budgeting_allowed_flag = 'Y';
• SELECT code_combination_id, segment1, segment2, template_id FROM igi_bud_summary_combs_v WHERE summary_flag = 'Y' AND enabled_flag = 'Y';
• SELECT segment1, segment2, segment3, segment4, segment5 FROM igi_bud_summary_combs_v WHERE chart_of_accounts_id = :p_coa AND end_date_active IS NULL;

Because the column count exceeds the documented excerpt, implementations should verify against ALL_TAB_COLUMNS whether higher-numbered SEGMENT_ATTRIBUTE columns (such as SEGMENT_ATTRIBUTE42) are actually exposed in the target instance before referencing them in customer extensions or reports.