Results for “igw_expenditure_types_v”

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

Overview

IGW_EXPENDITURE_TYPES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, defined within the IGW (Grants Proposal) product family. It exposes expenditure type definitions used by the Grants Proposal module and is validated as a VALID object under both EBS 12.1.1 and 12.2.2. The view serves as an abstraction layer that presents a single, normalized list of expenditure types regardless of whether the Oracle Grants Management (GMS) subsystem is enabled in the environment. Because grants proposal functionality must coexist with deployments where GMS is not licensed or enabled, the view dynamically selects the appropriate source of expenditure type records at runtime by branching on the IGW_SECURITY.GMS_ENABLED profile value. This conditional union makes the view a stable contract for forms, reports, and integrations that require expenditure type lookups without needing to know which underlying table stores the authoritative data.

Underlying Base Objects

The view is defined over two distinct source paths joined by a UNION ALL operation, gated by the IGW_SECURITY.GMS_ENABLED security function:

• IGW_EXPENDITURE_TYPES — used when GMS_ENABLED = 'N'. This table stores expenditure types native to the IGW schema for non-GMS-enabled installations.
• PA_EXPENDITURE_TYPES joined to IGW_EXPENDITURE_CATEGORIES — used when GMS_ENABLED = 'Y'. In GMS-enabled environments, expenditure types are drawn from the Projects (PA) module's master table, restricted to the expenditure categories that IGW recognizes through IGW_EXPENDITURE_CATEGORIES.

Both branches project an identical column list, including ROWID as ROW_ID, ensuring the view presents a consistent shape to consumers. No documented base objects were recorded in the ETRM metadata, but the view text confirms the two-branch structure and the IGW_SECURITY.GMS_ENABLED driving condition.

Key Columns

• ROW_ID — the ROWID of the source row, useful for identifying the physical record in the originating table.
• EXPENDITURE_CATEGORY — the category to which the expenditure type belongs; used to group and filter expenditure types within grants proposals.
• EXPENDITURE_TYPE — the code identifying the expenditure type; the primary business key presented by the view.
• DESCRIPTION — the descriptive name of the expenditure type as shown to users.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range during which the expenditure type is active.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns reflecting who created or last modified the record and when.

Common Use Cases and Queries

The view is typically used in grants proposal setup, validation logic, and reporting where a unified expenditure type list is required. Typical scenarios include populating LOVs, validating budget or proposal line entries, and extracting expenditure type reference data for integration or analysis.

Retrieving all currently active expenditure types:

• SELECT expenditure_category, expenditure_type, description FROM igw_expenditure_types_v WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE) ORDER BY expenditure_category, expenditure_type;

Listing expenditure types for a specific category:

• SELECT expenditure_type, description FROM igw_expenditure_types_v WHERE expenditure_category = :category;

Because the view resolves the GMS-enabled branch internally, the same query returns correct results whether or not Oracle Grants Management is installed, eliminating the need for environment-specific logic in downstream code.