Search Results gms_pqh_exp_types_v




Overview
Explore in AI Chat

Overview

The view GMS_PQH_EXP_TYPES_V is an Oracle EBS database object owned by the APPS schema and defined within the GMS – Grants Accounting product family. It is a denormalized reporting view that consolidates expenditure type information with the project, task, and award context required to evaluate allowable costs against sponsored grants. The name reflects its purpose: the "PQH" segment relates to sponsored project/quadrant hierarchy processing, while "EXP_TYPES_V" indicates that the view exposes expenditure type data.

In Oracle EBS 12.1.1 and 12.2.2, this view serves as a bridge between the Purchasing/Projects expenditure type definitions (PA_EXPENDITURE_TYPES_EXPEND_V) and the Grants Accounting allowability framework (GMS_ALLOWABLE_EXPENDITURES, GMS_AWARDS). It allows users and downstream reports to identify, for any sponsored project or task, which expenditure types are valid and the date range over which they are active. Because allowability is governed by award-level schedules, the view effectively translates award configuration into project/task-level expenditure type availability.

Note that users searching for the similar object PA_EXPENDITURE_TYPES_EXPEND_V may in fact need GMS_PQH_EXP_TYPES_V, since the latter incorporates the former as one of its base objects and adds Grants-specific filtering.

Underlying Base Objects

According to the documented 12.2.2 metadata, GMS_PQH_EXP_TYPES_V is defined over the following referenced objects:

  • PA_EXPENDITURE_TYPES_EXPEND_V (VIEW) – the source of the expenditure type definition and its active date range.
  • GMS_ALLOWABLE_EXPENDITURES (SYNONYM) – links expenditure types to allowability schedules.
  • GMS_AWARDS (SYNONYM) – supplies the AWARD_ID and ORG_ID context.
  • GMS_PROJECT_TYPES (VIEW) – used to restrict to sponsored (grant-funded) project types via SPONSORED_FLAG = 'Y'.
  • PA_PROJECTS_ALL (SYNONYM) – provides the project definition and project type.
  • PA_TASKS (SYNONYM) – provides the task identifier within the project.

The join logic is significant: the view filters on PET.SYSTEM_LINKAGE_FUNCTION = 'PJ' (Projects), joins allowable expenditures to awards through ALLOWABILITY_SCHEDULE_ID, and restricts the project population to sponsored project types. This ensures only grant-relevant combinations of project, task, award, and allowable expenditure type are returned.

Key Columns

  • EXPENDITURE_TYPE – the expenditure type name (from PA_EXPENDITURE_TYPES_EXPEND_V), the core value being validated for allowability.
  • PROJECT_ID – the sponsored project to which the expenditure type applies.
  • TASK_ID – the specific task within the project, enabling task-level expenditure control.
  • AWARD_ID – the grant award whose allowability schedule governs the expenditure type.
  • EXPND_TYP_START_DATE_ACTIVE – the date on which the expenditure type becomes active for the combination.
  • EXPND_TYP_END_DATE_ACTIVE – the date on which the expenditure type ceases to be active.
  • ORG_ID – the operating unit / organization identifier, supporting multi-org security and reporting.

Common Use Cases and Queries

Typical uses include validating whether a proposed expenditure type is allowability-scheduled for a given sponsored project/task, populating expenditure entry validation lists, and supporting Grants Accounting reporting. A representative query follows:

SELECT e.expenditure_type,
       e.project_id,
       e.task_id,
       e.award_id,
       e.expnd_typ_start_date_active,
       e.expnd_typ_end_date_active,
       e.org_id
FROM   apps.gms_pqh_exp_types_v e
WHERE  e.project_id = :p_project_id
AND    e.org_id     = :p_org_id
AND    TRUNC(SYSDATE) BETWEEN e.expnd_typ_start_date_active
                          AND e.expnd_typ_end_date_active;

Because the view is already joined and filtered to sponsored projects, no additional GMS allowability joins are required in most reporting scenarios.