Search Results template_flag




Overview
Explore in AI Chat

Overview

APPS.GMS_PROJECTS_BASIC_V is a reporting and integration view in Oracle E-Business Suite (12.1.1 and 12.2.2) that exposes a curated, security-aware subset of project header information drawn from the Oracle Projects foundation. Its name and definition tie it to the Grants Management (GMS) subsystem, which relies heavily on Oracle Projects to store award-linked and non-contract project structures. The view is owned by APPS and is intended for read-only consumption by reports, concurrent programs, Discoverer workbooks, OBIEE extracts, and inbound/outbound interfaces.

Two filters define its behavior. First, it excludes records where PROJECT_TYPE_CLASS_CODE equals 'CONTRACT', so contract-type projects are intentionally omitted. Second, it retains only rows for which GMS_COMMON_PKG.IS_PROJECT_TEMPLATE(TEMPLATE_FLAG) returns 1, thereby restricting output to records the GMS package classifies as templates. The result set is ordered by PROJECT_NUMBER, producing a stable, human-readable sequencing useful for LOVs and lookups keyed on project number.

Underlying Base Objects

The view's primary source is the Oracle Projects view PA_PROJECTS_BASIC_V, from which it projects thirteen columns without modification. Because PA_PROJECTS_BASIC_V is itself a secured view, row-level access to projects is enforced as part of its definition before GMS_PROJECTS_BASIC_V further narrows the result set.

Several PL/SQL packages appear in the dependency chain. GMS_COMMON_PKG supplies IS_PROJECT_TEMPLATE, the predicate that determines template eligibility. HR_GENERAL and HR_SECURITY supply the standard Oracle EBS security primitives (organization and business-group access) used throughout Projects views. PA_SECURITY provides the Projects-specific security model, including project-level and organization-level authorization. MO_GLOBAL supplies multi-org context resolution, which is consistent with the presence of ORG_ID and OPERATING_UNIT in the projection.

Key Columns

  • PROJECT_ID — Internal surrogate key for the project; the join key to underlying Projects tables.
  • PROJECT_NUMBER — The user-facing project identifier. This is the column most frequently searched, and the view's ORDER BY clause sorts on it.
  • PROJECT_NAME and LONG_NAME — Short and extended descriptive names for display and reporting.
  • PROJECT_TYPE_CLASS_CODE — Classification of the project type; values other than 'CONTRACT' are retained.
  • PROJECT_STATUS_CODE — Lifecycle status of the project, useful for filtering active versus closed records.
  • TEMPLATE_FLAG — Indicator consumed by GMS_COMMON_PKG.IS_PROJECT_TEMPLATE to qualify template records.
  • PM_PROJECT_REFERENCE — Cross-reference to the Project Management project reference.
  • PROJECT_NUMBER_SORT_ORDER — Sort key supporting alphanumeric ordering of project numbers.
  • PROJECT_CURRENCY_CODE — Functional currency for the project.
  • CC_PRVDR_FLAG — Cross-charge provider indicator.
  • ORG_ID and OPERATING_UNIT — Legal entity and operating unit context for multi-org security.

Common Use Cases and Queries

Typical uses include populating template selection LOVs, validating a project number during GMS award or budget entry, and feeding downstream reporting that must exclude contract projects.

  • Lookup by project number: 
    SELECT project_id, project_number, project_name
FROM   apps.gms_projects_basic_v
WHERE  project_number = :p_project_number;
  • Listing available templates: 
    SELECT project_number, project_name, project_status_code
FROM   apps.gms_projects_basic_v
WHERE  project_status_code = 'APPROVED'
ORDER BY project_number;
  • Validating a project in an interface: join PROJECT_ID back to Projects tables to confirm existence and template eligibility before inserts.

Because template qualification is enforced through GMS_COMMON_PKG, results reflect the same rules used by GMS forms, ensuring consistency between UI and reports.