Search Results segment_attribute2




Overview
Explore in AI Chat

Overview

GL_SUMMARY_COMBINATIONS_V is an APPS-owned database view in the Oracle E-Business Suite General Ledger (GL) module. Its ETRM description is recorded simply as "10SC ONLY," indicating that the object belongs to the localization scope designated for the 10SC (a country-specific/localization) context rather than the core global GL data model. In Oracle EBS 12.1.1 and 12.2.2, the view exposes a denormalized, reporting-friendly projection of account code combinations linked to summary account definitions and ledger context. It is primarily used by reporting, integration, and diagnostic queries that need to resolve summary template combinations together with their individual segment values.

The view is a conventional (non-materialized) view; it does not store data but derives its rows at runtime from the documented base synonyms. Its role in Oracle EBS is therefore read-only reporting and integration access, allowing custom reports, concurrent programs, and interfaces to reference summary combinations without joining GL_CODE_COMBINATIONS and GL_SUMMARY_TEMPLATES directly.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both exposed as synonyms in the APPS schema:

The view text carries the standard EBS header comment ($HEADER: GLGVWREG.LDT 120.29.12020000.1 2012/06/27 14:57:54 APPLDEV SHIP), confirming it was deployed from the GL registration file at the 12.0.29 version level. Because the definition joins CC.ROWID as ROW_ID, the view preserves row-level identity for the combinations it projects.

Key Columns

Given that the user searched for "segment_attribute1," SEGMENT_ATTRIBUTE1 is among the most relevant columns exposed by this view. The structure includes:

  • CODE_COMBINATION_ID — primary key of the underlying code combination row.
  • LEDGER_ID — the ledger to which the summary combination belongs.
  • SEGMENT1 … SEGMENT30 — the individual key flexfield segment values that make up the account combination.
  • SEGMENT_ATTRIBUTE1 … SEGMENT_ATTRIBUTEn — the descriptive/qualifier attributes attached to each segment of the code combination; SEGMENT_ATTRIBUTE1 typically carries the primary segment qualifier (for example, the account type or balancing qualifier) associated with the segment value.
  • CHART_OF_ACCOUNTS_ID — identifies the accounting key flexfield structure.
  • ENABLED_FLAG, SUMMARY_FLAG, DETAIL_POSTING_ALLOWED_FLAG, DETAIL_BUDGETING_ALLOWED_FLAG — status and posting controls.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the active date range of the combination.
  • ATTRIBUTE1 … ATTRIBUTE10 — the generic descriptive flexfield attribute columns.
  • TEMPLATE_ID — links the combination to its summary template definition.

Common Use Cases and Queries

Because the metadata identifies this view as "10SC ONLY," access is generally limited to localization-specific logic. Typical uses include resolving summary combinations for a ledger and inspecting segment qualifiers via SEGMENT_ATTRIBUTE1.

  • List summary combinations for a ledger: 
    SELECT code_combination_id, ledger_id, segment1, segment_attribute1
FROM   apps.gl_summary_combinations_v
WHERE  ledger_id = :ledger_id;
  • Filter by a specific segment qualifier: 
    SELECT code_combination_id, segment1, segment_attribute1
FROM   apps.gl_summary_combinations_v
WHERE  segment_attribute1 = :qualifier;
  • Identify active, posting-enabled summary combinations: 
    SELECT code_combination_id, segment1, enabled_flag, summary_flag
FROM   apps.gl_summary_combinations_v
WHERE  enabled_flag = 'Y';

All queries should be executed in the APPS schema or through a responsibility with appropriate grants, since the view reconciles data from both GL_CODE_COMBINATIONS and GL_SUMMARY_TEMPLATES at runtime.