Results for “seed_data_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGW_REPORT_SEED_HEADER_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, registered with a status of VALID. It belongs to the IGW product family — Grants Proposal — which supports the administration, budgeting, and reporting of sponsored research proposals within Oracle Grants Management and the associated proposal reporting facilities.

The ETRM documentation explicitly annotates this object with the description "10SC Only," identifying it as a component that applies solely to the 10SC (ten-something configuration) variant of the product line rather than to the general IGW installation. This annotation is significant because it signals that the view is not intended for broad deployment across all EBS environments; it exists to support a restricted configuration, and its use should be validated against the specific environment in which Grants Proposal has been implemented.

Functionally, the view serves as a lightweight, de-duplicated header-level access point for proposal report seed records. It exposes the distinctive combination of proposal form number and seed data flag, allowing downstream reporting and integration logic to enumerate the seed headers that exist in the underlying seed repository without retrieving the full detail rows held in the base table. In Oracle EBS reporting, such header views are typically joined to detail views to build complete report datasets while avoiding redundant scanning of transactional columns.

Underlying Base Objects

The view text is documented as a single-table definition over IGW_REPORT_BUDGET_SEED. The select list is SELECT DISTINCT PROPOSAL_FORM_NUMBER, SEED_DATA_FLAG FROM IGW_REPORT_BUDGET_SEED. The DISTINCT keyword is the defining characteristic of this view: IGW_REPORT_BUDGET_SEED may contain multiple budget seed rows for the same proposal form, and the view collapses them into one row per distinct combination of proposal form number and seed data flag. This provides a header-level projection rather than a row-level extract.

No other referenced base objects are documented in the ETRM metadata beyond IGW_REPORT_BUDGET_SEED. Because the view is a simple projection with DISTINCT and no joins, aggregates, or functions, it is not updateable and cannot be used as a DML target through the view. Its relationship to the base table is strictly one of filtering and de-duplication; no data transformation occurs, and all values returned are the stored column values from the seed table.

Key Columns

• PROPOSAL_FORM_NUMBER — Identifies the proposal form to which a set of budget seed records belongs. This is the primary grouping key for the header view and is the column most frequently used in joins to proposal and budget report objects.
• SEED_DATA_FLAG — A flag indicating the seed data classification of the underlying records. Because the view applies DISTINCT across both columns, each returned row represents a unique proposal form/flag pairing, effectively revealing which seed-data states exist for each proposal form.

These are the only two columns exposed. The narrow projection is deliberate: the view is designed for existence checking and header enumeration rather than detailed data extraction.

Common Use Cases and Queries

The primary use case is identifying which proposal forms have seed data present in the report budget seed repository, and under which flag values, before querying the detail table. A representative query follows:

• SELECT PROPOSAL_FORM_NUMBER, SEED_DATA_FLAG FROM APPS.IGW_REPORT_SEED_HEADER_V ORDER BY PROPOSAL_FORM_NUMBER;
• SELECT PROPOSAL_FORM_NUMBER FROM APPS.IGW_REPORT_SEED_HEADER_V WHERE SEED_DATA_FLAG = 'Y';
• Existence check: SELECT COUNT(*) FROM APPS.IGW_REPORT_SEED_HEADER_V WHERE PROPOSAL_FORM_NUMBER = :form_number;

Because the view restricts output to the 10SC configuration, it should be used in conjunction with the IGW_REPORT_BUDGET_SEED detail table when full budget seed content is required; the header view supplies the distinct keys, and a join on PROPOSAL_FORM_NUMBER and SEED_DATA_FLAG retrieves the corresponding rows. All access should be made through the APPS schema or a synonym created under the responsibility-owning schema, and usage should be confirmed against the specific EBS 12.1.1 or 12.2.2 environment where 10SC is enabled.