Search Results gms_projects_burden_v




Overview
Explore in AI Chat

Overview

GMS_PROJECTS_BURDEN_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the GMS - Grants Accounting product family. Its purpose is to expose the subset of sponsored projects that remain burdenable — that is, active, sponsored, non-template projects that have not been closed. The view joins project master data from PA_PROJECTS against sponsored project type definitions in GMS_PROJECT_TYPES, filtering out award-level container projects and inactive project statuses.

Because the view resides in the APPS schema and is registered as VALID in both ETRM 12.1.1 and 12.2.2, it is treated as a supported integration surface for grants-related reporting. It abstracts several join and filter conditions into a single object, allowing report authors, concurrent programs, and third-party integrations to retrieve a clean list of burdenable sponsored projects without re-implementing the underlying business logic.

Underlying Base Objects

The view is defined over three documented base objects:

  • PA_PROJECTS (referenced as a synonym) — the core projects table in the Projects module, supplying segment, name, description, project identifier, and operating unit context.
  • GMS_PROJECT_TYPES (referenced as a view) — provides the sponsored classification used to identify grants-funded project types.
  • PA_PROJECT_STUS_UTILS (referenced as a package) — supplies the IS_PROJECT_STATUS_CLOSED function used to exclude projects in a closed status.

The defining query restricts results using these predicates: the project type must match a sponsored project type (SPONSORED_FLAG = 'Y'), the project type must not equal 'AWARD_PROJECT', the project must not be a template (TEMPLATE_FLAG = 'N'), and the project status must not be closed according to the status utility function. This effectively yields sponsored, operational projects eligible for burden and cost allocation processing.

Key Columns

  • SEGMENT1 — the user-visible project number from PA_PROJECTS, used as the primary business identifier in reports and integrations.
  • NAME — the descriptive project name.
  • DESCRIPTION — the free-form project description.
  • PROJECT_ID — the internal surrogate key for the project; the join column to downstream awards, tasks, budgets, and expenditure items.
  • ORG_ID — the operating unit identifier, enabling multi-org security filtering across business groups.

Common Use Cases and Queries

Typical usage includes burden and indirect cost reporting, grants dashboards, and integration extracts that need a current list of sponsored projects still open for cost charging. A basic query returns the active sponsored project set:

  • SELECT PROJECT_ID, SEGMENT1, NAME, ORG_ID FROM APPS.GMS_PROJECTS_BURDEN_V WHERE ORG_ID = :p_org_id;
  • A join to PA_PROJECTS ensures the view remains in sync with live project data when combined with expenditure or budget queries.
  • Integration extracts commonly filter by PROJECT_ID to feed burden schedules or allocate indirect costs to sponsored grants.

Because the view derives status dynamically through PA_PROJECT_STUS_UTILS, results reflect the current project lifecycle state at query time, making it suitable for recurring concurrent programs rather than static snapshots.