Search Results sponsored_flag




Overview
Explore in AI Chat

Overview

APPS.GMS_PROJECT_TYPES is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes a filtered and normalized projection of project type definitions used by the Grants Management (GMS) module and the Projects (PA) foundation. The view derives its data entirely from PA_PROJECT_TYPES, applying two transformations at the view layer: a predicate that excludes the internal 'AWARD_PROJECT' project type, and a DECODE expression that converts a NULL SPONSORED_FLAG value into the literal 'N'. These transformations make the view suitable for downstream consumers—concurrent programs, BI Publisher reports, Forms LOVs, and interface tables—that expect a clean, consistently populated sponsored indicator and that must not treat the internal award project construct as a user-selectable project type. Because the object is owned by APPS and defined over a synonym, it participates in the standard EBS security and synonym-resolution model and is ordinarily granted to reporting responsibilities and integration schemas through the APPS account.

Underlying Base Objects

The view is defined over a single documented base object, PA_PROJECT_TYPES, which the view text references through its synonym in the APPS schema. PA_PROJECT_TYPES is the Projects application's repository of project type definitions and stores the classification, description, sponsored indicator, and operating unit context for each type. No joins, aggregates, or subqueries appear in the documented view text, so cardinality is preserved: one row in PA_PROJECT_TYPES that satisfies the WHERE predicate yields exactly one row in GMS_PROJECT_TYPES. The only row-eliminating condition is that PA.PROJECT_TYPE must not equal 'AWARD_PROJECT'; this reserves the award project type for internal GMS processing rather than exposing it as a general project type. All column values are passed through unchanged except SPONSORED_FLAG, which is normalized as described below. Because the source is a synonym, the view follows the standard APPS-shared object pattern and remains valid across the 12.1.1 and 12.2.2 releases documented in ETRM.

Key Columns

  • PROJECT_TYPE — The project type identifier, carried directly from PA_PROJECT_TYPES.PROJECT_TYPE. It is the principal lookup key and the column commonly joined to project and award records.
  • DESCRIPTION — The user-facing name or description of the project type, exposed unchanged from the base table.
  • PROJECT_TYPE_CLASS_CODE — The classification code that groups project types into functional categories, again passed through from the base table.
  • SPONSORED_FLAG — The key derived column. The view applies DECODE(SPONSORED_FLAG, NULL, 'N', SPONSORED_FLAG), so a NULL stored value is presented as 'N' and any non-NULL value is returned as-is. This eliminates three-valued logic issues for consumers that filter or report on the sponsored indicator.
  • ORG_ID — The operating unit identifier associated with the project type, exposed from the base table and used for multi-org (MOAC) filtering in reports and integrations.

Common Use Cases and Queries

The view is most often used to populate project type lists in integration flows and to drive sponsored-versus-non-sponsored reporting. A representative query retrieves the sponsored project types for the current operating unit:

  • SELECT project_type, description, sponsored_flag FROM apps.gms_project_types WHERE sponsored_flag = 'Y' ORDER BY description;
  • SELECT project_type, description, project_type_class_code FROM apps.gms_project_types WHERE org_id = :org_id;
  • SELECT project_type, COUNT(*) FROM apps.gms_project_types GROUP BY project_type ORDER BY project_type;

Because the view guarantees that SPONSORED_FLAG is never NULL, predicates such as sponsored_flag = 'N' reliably return the non-sponsored set, a common requirement when validating project type selection during award and project setup. Consumers should remember that the view intentionally omits the 'AWARD_PROJECT' type, so any reconciliation back to PA_PROJECT_TYPES must account for that exclusion when comparing row counts.