Search Results igw_budget_category




Overview
Explore in AI Chat

Overview

IGW_REPORT_BUDGET_SEED_V is an Oracle E-Business Suite view owned by the APPS schema. It exposes a denormalized, reporting-friendly projection of proposal budget category data used by Oracle Grants Management (part of the Oracle E-Business Suite grants and proposals functionality). The view joins budget category codes stored on the report budget seed table to the human-readable lookup meaning maintained in the IGW lookup value source, producing a concise result set containing the budget category description, its code, and the associated proposal form number. In the context of Oracle EBS 12.1.1 and 12.2.2, this view serves as a read-only presentation layer so that reporting tools, concurrent programs, OBIEE extracts, and custom SQL can resolve lookup codes to meaningful descriptions without re-implementing the lookup join logic.

The name of the view indicates it is a seeding or staging view. It is not a transactional interface, and it is generally consumed rather than maintained. Because the view is a DISTINCT query, duplicate rows introduced by the underlying lookup join are collapsed, which makes the output suitable for direct use in value lists and dimension tables.

Underlying Base Objects

As documented in the ETRM metadata, the view is defined over two database objects:

  • IGW_REPORT_BUDGET_SEED (aliased as IR) — the primary source of proposal budget category codes and proposal form numbers.
  • IGW_LOOKUPS_V (aliased as IL) — the lookup view that resolves lookup codes to meanings for a given lookup type.

The join predicate is IR.PROPOSAL_BUDGET_CATEGORY_CODE = IL.LOOKUP_CODE, constrained by IL.LOOKUP_TYPE = 'IGW_BUDGET_CATEGORY'. This restricts the result to only those codes that belong to the IGW budget category lookup type, preventing unrelated lookup codes from being joined. The ETRM documentation lists no further base objects, so the view is a thin join over these two sources rather than a complex composite. Note that one of the referenced objects (the lookup view) is itself a view, so the effective base object chain includes the underlying lookup tables maintained by the lookup framework.

Key Columns

The view projects three columns:

  • PROPOSAL_BUDGET_CATEGORY — the lookup meaning (description) associated with the budget category, sourced from IGW_LOOKUPS_V.MEANING. This is the user-facing label.
  • PROPOSAL_BUDGET_CATEGORY_CODE — the lookup code from the report budget seed table, matched against IGW_LOOKUPS_V.LOOKUP_CODE. This is the key carried on transactional records.
  • PROPOSAL_FORM_NUMBER — the proposal form number from the report budget seed table, associating the category with a specific proposal form.

This column naming echoes the "igw_budget_category" lookup type that users typically search for, indicating the intended purpose: mapping IGW budget category codes to their meanings for reporting.

Common Use Cases and Queries

Typical scenarios include building budget category value lists, cross-referencing proposal form numbers with their budget categories, and feeding extracts for grants reporting. The following query lists all budget categories and their associated proposal forms:

SELECT DISTINCT proposal_budget_category,
          proposal_budget_category_code,
          proposal_form_number
FROM  apps.igw_report_budget_seed_v
ORDER BY proposal_budget_category;

A filtered variant retrieves the category for a specific form:

SELECT proposal_budget_category, proposal_budget_category_code
FROM  apps.igw_report_budget_seed_v
WHERE proposal_form_number = :p_form_number;

Because the view already joins the lookup, it eliminates the need to write custom joins against IGW_LOOKUPS_V and reduces the risk of missing the IGW_BUDGET_CATEGORY lookup type constraint. For high-volume reporting, use it as a dimension source rather than a transactional driver.