Search Results award_project




Overview
Explore in AI Chat

Overview

APPS.GMS_PROJECTS_BURDEN_V is a reporting view in Oracle EBS Grants Management (GMS), the module built on Oracle Projects (PA) to support sponsored research and award accounting. The view exposes a filtered list of projects from PA_PROJECTS that qualify as sponsored projects yet are not themselves award projects. Its name reflects its intended role: to surface the burden-bearing (indirect cost) project records associated with sponsored activities, distinct from the award header project that carries the award terms.

In EBS 12.1.1 and 12.2.2 the view is owned by APPS and is defined over PA_PROJECTS, GMS_PROJECT_TYPES, and the PA_PROJECT_STUS_UTILS package. It is typically consumed by burden and indirect cost calculations, sponsored project reporting, and integrations that need to enumerate active sponsored project structures. Because award-level projects are explicitly excluded, the view supports the operational (burden) side of the grant rather than the funding header. The presence of ORG_ID confirms it is a multi-org view, so queries must respect operating unit (MO) security.

Underlying Base Objects

The documented referenced base objects are:

The join is on PROJECT_TYPE between PA_PROJECTS and GMS_PROJECT_TYPES. The predicate A.PROJECT_TYPE <> 'AWARD_PROJECT' removes award headers, TEMPLATE_FLAG = 'N' excludes templates, SPONSORED_FLAG = 'Y' restricts to sponsored project types, and the status utility returns 'N' for non-closed projects. The result is a live, sponsored, non-award, non-closed, non-template project list. Note the view does not join PA_TASKS or burden schedule tables — it is project-level, not task- or cost-level, so it identifies the projects eligible for burden processing rather than computing burdens directly.

Key Columns

  • SEGMENT1 — the user-facing project number; the primary business identifier used in reports and lookups.
  • NAME — project name, as displayed in forms and inquiry screens.
  • DESCRIPTION — descriptive text for the project, useful in listings and exports.
  • PROJECT_ID — the internal primary key; join this to PA_PROJECTS, PA_TASKS, PA_EXPENDITURES, and burden tables rather than matching on SEGMENT1.
  • ORG_ID — operating unit identifier; enforces multi-org access and must be included in MO-filtered queries.

Because the view is a thin projection over PA_PROJECTS, no computed burden amounts are exposed. Any indirect cost or burden value must be retrieved from the relevant burden schedule and expenditure tables keyed by PROJECT_ID.

Common Use Cases and Queries

Typical scenarios include populating burden project LOVs, validating that a sponsored project exists and is open before running cost allocation, and reconciling the set of sponsored burden projects for a period. A search for "award_project" maps here because the view is defined precisely by the exclusion of AWARD_PROJECT types, making it the natural counterpart to award-level inquiries.

List sponsored burden projects for an operating unit:

  • SELECT segment1, name, project_id, org_id FROM apps.gms_projects_burden_v WHERE org_id = :p_org_id ORDER BY segment1;

Retrieve a single project by number:

  • SELECT segment1, name, description, project_id FROM apps.gms_projects_burden_v WHERE segment1 = :p_number AND org_id = :p_org_id;

Join to tasks or expenditures for cost analysis:

  • SELECT v.segment1, t.task_number, e.raw_cost FROM apps.gms_projects_burden_v v, pa_tasks t, pa_expenditures e WHERE t.project_id = v.project_id AND e.task_id = t.task_id AND v.org_id = :p_org_id;

Always filter on ORG_ID to satisfy multi-org security, and avoid ordering by unindexed columns on large PA_PROJECTS populations.