Search Results igi_bud_code_combinations_v




Overview
Explore in AI Chat

Overview

IGI_BUD_CODE_COMBINATIONS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGI — Public Sector Financials International product. The view is defined over GL_CODE_COMBINATIONS, the central repository of accounting flexfield combinations in Oracle General Ledger, and exposes the full chart of accounts structure, segment values, control flags, and descriptive attributes relevant to budgetary processing. Within the IGI module, the view provides a denormalized, read-only presentation of code combinations that supports budget execution, funds availability checking, and public-sector financial reporting. Because it is a view rather than a table, it introduces no additional storage and always reflects the current state of the underlying GL_CODE_COMBINATIONS records, subject to the join logic embedded in its definition.

For implementers and technical consultants, the view is significant because it abstracts the detail budgeting and detail posting flags that determine whether a code combination may be used in budget entries versus actual transactions. This makes it a convenient source for validation logic, concurrent reporting, and integration extracts, particularly in environments where budgetary control is enforced at the code combination level.

Underlying Base Objects

The ETRM metadata documents the view as based on GL_CODE_COMBINATIONS, accessed through a synonym, with GL_LOOKUPS (itself a view) referenced for lookup description resolution. The view text confirms this relationship: code combination columns are selected from the aliased source CC, while a lookup join (aliased LK) supplies the SHOW_ACCOUNT_TYPE column, which translates the ACCOUNT_TYPE code into a human-readable description. GL_LOOKUPS is the standard EBS lookup view that resolves lookup codes against lookup types; here it is used with the account type lookup to present descriptive text alongside the stored code. No other base tables are documented. As with most APPS-owned views, permissions are controlled through grants and synonyms, and the object should be treated as read-only in custom code.

Key Columns

The view exposes the full set of accounting flexfield segments, SEGMENT1 through SEGMENT30, along with the identifying CODE_COMBINATION_ID and CHART_OF_ACCOUNTS_ID. Control columns include DETAIL_POSTING_ALLOWED_FLAG and DETAIL_BUDGETING_ALLOWED_FLAG, which govern whether the combination can be used for actual postings or budget entries respectively, plus ENABLED_FLAG and SUMMARY_FLAG. ACCOUNT_TYPE carries the stored account type, while SHOW_ACCOUNT_TYPE provides its lookup description. Effective dating is supported by START_DATE_ACTIVE and END_DATE_ACTIVE. Descriptive and reference fields include DESCRIPTION, TEMPLATE_ID, and ATTRIBUTE1 through ATTRIBUTE10, with CONTEXT and SEGMENT_ATTRIBUTE1 through SEGMENT_ATTRIBUTE30 available for descriptive flexfield storage. A ROW_ID column exposes the underlying row identifier.

Notably for users searching on "jgzz_recon_flag": this flag is a descriptive flexfield attribute commonly stored in the ATTRIBUTE or SEGMENT_ATTRIBUTE columns of GL_CODE_COMBINATIONS, depending on configuration. The view therefore surfaces it indirectly through those generic attribute columns rather than as a named column, and reconciliation logic typically resolves it by inspecting the appropriate attribute position or the associated descriptive flexfield context.

Common Use Cases and Queries

Typical scenarios include listing all enabled detail-budgeting combinations for a chart of accounts, validating whether a combination permits budget entry, and extracting segment values for reconciliation or interface loads.

  • Retrieve budget-enabled combinations for a specific chart:

    SELECT CODE_COMBINATION_ID, SEGMENT1, SEGMENT2, SEGMENT3, SHOW_ACCOUNT_TYPE FROM IGI_BUD_CODE_COMBINATIONS_V WHERE CHART_OF_ACCOUNTS_ID = :chart_id AND DETAIL_BUDGETING_ALLOWED_FLAG = 'Y' AND ENABLED_FLAG = 'Y';

  • Identify combinations active as of a given date:

    SELECT CODE_COMBINATION_ID, DESCRIPTION FROM IGI_BUD_CODE_COMBINATIONS_V WHERE TRUNC(SYSDATE) BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, TRUNC(SYSDATE));

  • Reconciliation support for jgzz_recon_flag, where the flag is held in a flexfield attribute: examine the relevant ATTRIBUTE or SEGMENT_ATTRIBUTE column for the combination and compare against the expected indicator.

Because the view reads live GL data, queries should be tuned with predicates on CHART_OF_ACCOUNTS_ID, ENABLED_FLAG, or CODE_COMBINATION_ID to avoid full scans of GL_CODE_COMBINATIONS in large implementations.