Results for “igi_gl_summary_combinations_v”

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

Overview

IGI_GL_SUMMARY_COMBINATIONS_V is a PL/SQL-view owned by the APPS schema and defined in the IGI — Public Sector Financials International product. The view exposes General Ledger accounting flexfield combinations that participate in summary or rollup reporting, drawing its data from GL_CODE_COMBINATIONS and joining against GL_SUMMARY_TEMPLATES. In Oracle EBS 12.1.1 and 12.2.2, this object serves as a reporting and integration surface for public-sector customers who need to identify summary (parent) accounts and their associated posting/budgeting attributes without querying the underlying GL_CODE_COMBINATIONS table directly.

Because the underlying code combination table is multi-org and validation-intensive, this view consolidates the segment columns, descriptive attributes, and control flags into a single, easily consumed rowset. It is commonly referenced by IGI reporting programs, concurrent requests, and custom extensions that must resolve a code combination to its summary template context.

Underlying Base Objects

The documented definition is based on GL_CODE_COMBINATIONS (aliased CC) and GL_SUMMARY_TEMPLATES (aliased T). The ETRM metadata further records DUAL as a referenced object, which is a synonym used in the count/validation fragments common to such views. The view selects CC.ROWID as ROW_ID and carries T.SET_OF_BOOKS_ID and T.TEMPLATE_ID through from the summary template join, allowing the caller to correlate each combination with its owning set of books and summary template without an additional lookup. Key combination columns (segments, attributes, flags, active dates) are passed through directly from CC.

Key Columns

• ROW_ID — The ROWID of the underlying GL_CODE_COMBINATIONS row, used for direct row addressing during DML or update processing.
• SET_OF_BOOKS_ID — The ledger/set of books from the summary template, identifying the accounting context.
• CODE_COMBINATION_ID — The primary key of the accounting flexfield combination.
• CHART_OF_ACCOUNTS_ID — The chart of accounts the combination belongs to.
• SEGMENT1 through SEGMENT30 — The individual accounting flexfield segment values.
• SEGMENT_ATTRIBUTE1, SEGMENT_ATTRIBUTE2, SEGMENT_ATTRIBUTE3… — Descriptive flexfield segment attributes; users searching for segment_attribute1 are typically resolving descriptive segment metadata here.
• SUMMARY_FLAG, DETAIL_POSTING_ALLOWED_FLAG, DETAIL_BUDGETING_ALLOWED_FLAG, ENABLED_FLAG — Control flags governing posting, budgeting, and enablement.
• ACCOUNT_TYPE, DESCRIPTION, START_DATE_ACTIVE, END_DATE_ACTIVE — Account classification, description, and active date range.
• ATTRIBUTE1 through ATTRIBUTE10, CONTEXT — Descriptive flexfield context and attribute columns.

Common Use Cases and Queries

Typical use cases include identifying summary combinations for a given template, locating active combinations by segment value, and validating posting restrictions before feeding data into IGI public-sector reports. A representative query follows:

• Retrieve summary combinations for a template:
  SELECT CODE_COMBINATION_ID, SEGMENT1, SEGMENT2, SUMMARY_FLAG FROM APPS.IGI_GL_SUMMARY_COMBINATIONS_V WHERE TEMPLATE_ID = :p_template_id;
• Locate active detail-posting combinations by segment attribute:
  SELECT CODE_COMBINATION_ID, SEGMENT1, SEGMENT_ATTRIBUTE1 FROM APPS.IGI_GL_SUMMARY_COMBINATIONS_V WHERE SEGMENT_ATTRIBUTE1 = :p_attr AND ENABLED_FLAG = 'Y';
• Correlate combinations to their set of books:
  SELECT SET_OF_BOOKS_ID, CODE_COMBINATION_ID FROM APPS.IGI_GL_SUMMARY_COMBINATIONS_V WHERE SET_OF_BOOKS_ID = :p_sob_id;

Because the view exposes ROW_ID, it is also used in update/delete routines where the base GL_CODE_COMBINATIONS row must be addressed precisely. All queries should be schema-qualified with APPS. and executed within the appropriate MO/operating unit context.