Search Results segment_attribute2

Overview

The view APPS.IGC_CBC_SUMMARY_COMBINATIONS_V is a reporting and inquiry construct owned by the APPS schema and delivered with the IGC — Contract Commitment product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its stated purpose in the ETRM metadata is to present a joined result set based on GL code combinations and summary templates, specifically to support the Account Inquiry flex block. In practical terms, the view flattens the relationship between a stored accounting flexfield combination (held in GL_CODE_COMBINATIONS) and the summary template definition (GL_SUMMARY_TEMPLATES) so that the Account Inquiry form can display summary-oriented combination data without issuing separate queries against each base table.

Because the view exposes all thirty segment columns and the full set of descriptive and control attributes on the code combination, it functions as a denormalized projection layer. It is read-only and carries no validation or derivation logic beyond the underlying join; the ETRM metadata records a status of VALID, indicating the view compiles successfully against its base objects in the supported releases.

Underlying Base Objects

The documented base objects referenced by the view are two synonyms in the APPS schema:

• GL_CODE_COMBINATIONS (SYNONYM) — the chart of accounts combination table that supplies the code combination identifier, segment values, account type, enabled and summary flags, and descriptive flexfield context and attribute columns.
• GL_SUMMARY_TEMPLATES (SYNONYM) — the summary template definitions used to group code combinations for account inquiry and summary reporting.

The view text aliases GL_CODE_COMBINATIONS as CC and the template object as T, and it exposes the row identifier of the combination as ROW_ID. The presence of CC.TEMPLATE_ID in the select list indicates the template association is carried on the combination record itself, while T.SET_OF_BOOKS_ID supplies the ledger context for the summary template. No user-exit or PL/SQL logic is involved; the object is a straightforward SELECT-based view.

Key Columns

The column set falls into several functional groups:

• Identity and ledger context: ROW_ID, CODE_COMBINATION_ID, SET_OF_BOOKS_ID, CHART_OF_ACCOUNTS_ID, and TEMPLATE_ID.
• Control flags: DETAIL_POSTING_ALLOWED_FLAG, DETAIL_BUDGETING_ALLOWED_FLAG, ENABLED_FLAG, SUMMARY_FLAG, ALLOCATION_CREATE_FLAG, and ACCOUNT_TYPE.
• Accounting flexfield segments: SEGMENT1 through SEGMENT30, exposing the full segment string of the combination.
• Descriptive and audit attributes: DESCRIPTION, START_DATE_ACTIVE, END_DATE_ACTIVE, LAST_UPDATE_DATE, LAST_UPDATED_BY, CONTEXT, and ATTRIBUTE1 through ATTRIBUTE10.
• Segment qualifiers: SEGMENT_ATTRIBUTE1 and the corresponding SEGMENT_ATTRIBUTE2 and subsequent columns, which carry the per-segment qualifier information used by the account inquiry flex block. This is the column family most relevant to users searching for "segment_attribute1", as SEGMENT_ATTRIBUTE1 stores the qualifier value for the first segment of the combination.

Common Use Cases and Queries

The view is typically consumed by Account Inquiry forms and by custom reports that need combination data enriched with summary template context. A representative query is:

SELECT code_combination_id,
       set_of_books_id,
       segment1,
       segment2,
       segment_attribute1,
       template_id,
       enabled_flag,
       summary_flag
FROM   apps.igc_cbc_summary_combinations_v
WHERE  set_of_books_id = :p_sob_id
AND    enabled_flag = 'Y';

Additional scenarios include validating that a combination participates in a summary template before posting, extracting the SEGMENT_ATTRIBUTE1 qualifier for reconciliation, and joining the view to contract commitment lines by CODE_COMBINATION_ID for account inquiry drill-down. Because the view operates over synonyms, querying it as APPS or as a user with appropriate privileges returns the same result set.