Search Results cc_prvdr_flag




Overview
Explore in AI Chat

Overview

GMS_PROJECTS_BASIC_V is a seeded, read-only database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the GMS (Grants Accounting) product family and exposes a filtered, secured subset of project records drawn from the underlying Oracle Projects view PA_PROJECTS_BASIC_V. Its principal purpose is to present the projects that are relevant to grants accounting, specifically excluding contract-type projects and restricting output to rows that qualify as project templates.

Within the ETRM documentation this object is recorded as VALID, confirming that the view compiles and that the referenced packages and base view resolve correctly. Because the view contains no DML logic and carries no stored data, it acts purely as a reporting and integration surface.

Underlying Base Objects

The documented base objects for this view are: GMS_COMMON_PKG (PACKAGE), HR_GENERAL (PACKAGE), HR_SECURITY (PACKAGE), MO_GLOBAL (PACKAGE), PA_PROJECTS_BASIC_V (VIEW), and PA_SECURITY (PACKAGE). The view text reveals the mechanics of these dependencies:

  • PA_PROJECTS_BASIC_V supplies the driving project rows and the column projection used by the outer query.
  • GMS_COMMON_PKG.IS_PROJECT_TEMPLATE(TEMPLATE_FLAG) acts as a row filter, returning 1 for rows that represent project templates.
  • HR_GENERAL, HR_SECURITY, MO_GLOBAL, and PA_SECURITY provide the multi-org and security context applied through the base view, ensuring that users see only the operating units and projects they are authorized to access.

The WHERE clause combines two predicates: PROJECT_TYPE_CLASS_CODE <> 'CONTRACT' and the IS_PROJECT_TEMPLATE check. Results are returned in PROJECT_NUMBER order.

Key Columns

The view exposes thirteen columns. PROJECT_ID is the unique internal identifier and is the most commonly used join key. PROJECT_NUMBER, PROJECT_NAME, and LONG_NAME provide the human-readable project identifiers and descriptions. PROJECT_TYPE_CLASS_CODE and PROJECT_STATUS_CODE describe classification and lifecycle state. TEMPLATE_FLAG is central to this view's logic: it is passed to GMS_COMMON_PKG.IS_PROJECT_TEMPLATE and, because the view filters on a return value of 1, every row returned already satisfies the template condition. PM_PROJECT_REFERENCE carries the Project Management reference, PROJECT_NUMBER_SORT_ORDER provides a sortable variant of the number, and PROJECT_CURRENCY_CODE holds the project currency. CC_PRVDR_FLAG, ORG_ID, and OPERATING_UNIT support cross-charging and multi-org reporting.

Common Use Cases and Queries

Typical usage includes LOV and validation queries in Grants Accounting forms, seeded report data sources, and ad-hoc extracts of non-contract template projects. A basic query follows:

SELECT project_id, project_number, project_name, project_status_code FROM gms_projects_basic_v WHERE org_id = :p_org_id ORDER BY project_number;

For template verification, TEMPLATE_FLAG can be inspected directly, although the view guarantees template rows only:

SELECT project_number, template_flag FROM gms_projects_basic_v WHERE template_flag = 'Y';

Because the view is secured, queries issued without valid operating-unit or security context may return no rows; callers should therefore always supply or inherit the appropriate MO and PA security parameters. The view should be treated as read-only, and any requirement for contract-class projects or non-template projects must be satisfied by querying PA_PROJECTS_BASIC_V directly.