Search Results proposal_form_number




Overview
Explore in AI Chat

Overview

The view IGW_REPORT_BUDGET_SEED_V belongs to the IGW – Grants Proposal product family within Oracle E-Business Suite. The ETRM metadata explicitly labels this module as Obsolete and annotates the view with the description "10SC Only", indicating that it was scoped to a specific historical release context rather than the general 12.1.1 or 12.2.2 code line.

Functionally, the view exposes a denormalized, reporting-friendly projection of proposal budget categories. It joins a seed table of budget category codes to a lookup view in order to resolve each code to its user-facing meaning, and it carries the associated PROPOSAL_FORM_NUMBER across the join. This makes it a reporting artifact rather than a transactional object: it consolidates the code/meaning pairing and the form context into a single result set so that downstream reports, extracts, or integrations do not have to perform the lookup join themselves. The user search term "proposal_form_number" maps directly to one of the three columns the view projects.

The ETRM record also states "Not implemented in this database" in the Implementation/DBA Data section, which is a critical practical caveat. In many Oracle EBS environments — and apparently in the environment from which this metadata was harvested — the view does not physically exist and therefore cannot be queried.

Underlying Base Objects

The view text references two objects:

The join predicate is an equijoin on IR.PROPOSAL_BUDGET_CATEGORY_CODE = IL.LOOKUP_CODE, combined with the static lookup-type filter. A SELECT DISTINCT is applied to eliminate duplicate rows that would otherwise arise from the lookup relationship. The documented ETRM metadata lists no referenced base objects and does not record an owner, meaning the dependency chain stops at the two objects named in the view text; the underlying physical tables behind IGW_LOOKUPS_V are not itemized in this record.

Key Columns

  • PROPOSAL_BUDGET_CATEGORY — the descriptive meaning resolved from IGW_LOOKUPS_V.MEANING for the IGW_BUDGET_CATEGORY lookup type. This is the human-readable label intended for display.
  • PROPOSAL_BUDGET_CATEGORY_CODE — the underlying lookup code, retained so that reports can join back to transaction data or sort and group deterministically.
  • PROPOSAL_FORM_NUMBER — the proposal form identifier carried from the seed table, associating each budget category row with the form under which it is defined. This is the column most commonly referenced by name.

Common Use Cases and Queries

Typical usage is to enumerate the budget categories available for a given proposal form, resolving codes to meanings for presentation in a report or interface extract:

  • Populating a report layout or LOV-style extract with category code/meaning pairs.
  • Confirming which budget categories are seeded for a specific proposal form number.
  • Data-validation and reconciliation checks between seeded categories and lookup definitions.

A representative query:

SELECT proposal_form_number, proposal_budget_category_code, proposal_budget_category FROM igw_report_budget_seed_v ORDER BY proposal_form_number, proposal_budget_category_code;

Because the ETRM record states the view is not implemented in the documented database and is marked obsolete, consumers should first verify existence via ALL_VIEWS or DBA_VIEWS before relying on it, and should treat IGW_REPORT_BUDGET_SEED and the IGW_BUDGET_CATEGORY lookup as the authoritative sources where the view is unavailable.