Search Results show_account_type




Overview
Explore in AI Chat

Overview

IGI_BUD_CODE_COMBINATIONS_V is a supplementary view owned by the APPS schema in Oracle EBS 12.1.1 and 12.2.2, registered under FND Design Data as IGI.IGI_BUD_CODE_COMBINATIONS_V. Its purpose is to simplify forms coding within the Oracle Grants/IGI budgeting modules rather than to serve as a general-purpose reporting interface. Oracle explicitly warns that this view is a supplementary view intended for form-level use and that direct querying or alteration of data through it is not recommended, since its definition may change dramatically in subsequent minor or major releases. Despite this caveat, the view is frequently surfaced by tools and integrators searching for the familiar "gl_code_combinations" access pattern, because it exposes the standard accounting flexfield segment structure and code combination attributes that developers recognize from the GL_CODE_COMBINATIONS base table. It effectively provides a budgeting-oriented projection of accounting flexfield data, allowing forms to present and validate code combinations without querying the base table directly.

Underlying Base Objects

The documented view metadata identifies two referenced base objects: GL_CODE_COMBINATIONS (accessed via a synonym) and GL_LOOKUPS (a view). GL_CODE_COMBINATIONS supplies the core accounting flexfield structure — the CODE_COMBINATION_ID, CHART_OF_ACCOUNTS_ID, enabled and summary flags, and the twenty-plus SEGMENTn columns that constitute the key flexfield. GL_LOOKUPS contributes descriptive values, most notably the SHOW_ACCOUNT_TYPE column documented with a length of 240, which provides the decoded account type description used for display in the budgeting forms. The view therefore sits as a thin abstraction layer over the accounting flexfield repository, joining lookup-driven display values so that IGI budgeting screens can render code combinations with human-readable account type information. Because the base object is referenced as a synonym, the physical table remains GL.GL_CODE_COMBINATIONS owned by the GL schema, while all access flows through the APPS synonym layer.

Key Columns

  • ROW_ID – ROWID (10); the row identifier inherited from the base row.
  • CODE_COMBINATION_ID – NUMBER (15); the unique accounting flexfield combination identifier and primary join key throughout EBS.
  • CHART_OF_ACCOUNTS_ID – NUMBER (15); identifies the chart of accounts to which the combination belongs.
  • DETAIL_POSTING_ALLOWED_FLAG / DETAIL_BUDGETING_ALLOWED_FLAG – indicate whether posting and budgeting respectively are permitted at the detail level.
  • ACCOUNT_TYPE and SHOW_ACCOUNT_TYPE – the account type indicator and its lookup-derived display description (length 240) sourced via GL_LOOKUPS.
  • ENABLED_FLAG and SUMMARY_FLAG – standard GL control flags governing whether the combination is active and whether it is a summary (parent) combination.
  • SEGMENT1 through SEGMENT22 – VARCHAR2 (25) columns representing each key flexfield segment value in the accounting flexfield.

Common Use Cases and Queries

Typical usage resolves a code combination for budgeting forms or validates that a combination is enabled and budgeting-permitted before display. A representative query retrieves the descriptive segments for a given combination:

  • SELECT code_combination_id, segment1, segment2, segment3, show_account_type FROM apps.igi_bud_code_combinations_v WHERE code_combination_id = :p_ccid;
  • SELECT code_combination_id FROM apps.igi_bud_code_combinations_v WHERE enabled_flag = 'Y' AND detail_budgeting_allowed_flag = 'Y';

Because Oracle discourages direct querying of supplementary views, integration and reporting code should prefer GL_CODE_COMBINATIONS or the supported GL_CODE_COMBINATIONS_KFV / _KFV interfaces where a stable contract is required, reserving this view for form-driven budgeting contexts.