Search Results expnd_typ_start_date_active




Overview
Explore in AI Chat

Overview

APPS.GMS_PQH_EXP_TYPES_V is a supplementary database view owned by the APPS schema in Oracle E-Business Suite, registered against FND Design Data identifier GMS.GMS_PQH_EXP_TYPES_V. It is documented as a "supplementary view used to simplify forms coding," meaning it exists primarily to flatten and join data from several Grants Management (GMS) and Projects (PA) base objects so that Oracle Forms-based screens can retrieve a consolidated row set without embedding complex join logic. Oracle explicitly warns that this view is not intended for direct querying or data manipulation by customers or integrators, and that its definition may change dramatically between minor or major releases. In EBS 12.1.1 and 12.2.2 the object resolves to a VALID status, confirming that all dependencies are compiled and present. The view surfaces expenditure type eligibility information in the context of awards, projects, and tasks, and it is consumed internally by the PQH_UTILITY package. The column naming convention (EXPND_TYP_START_DATE_ACTIVE, EXPND_TYP_END_DATE_ACTIVE) reflects the date-effective pattern used throughout EBS, though the user-supplied search term "expnd_typ_start_date_active" corresponds to the actual column EXPND_TYP_START_DATE_ACTIVE.

Underlying Base Objects

The view is defined over six documented dependencies, mixing synonyms, base tables, and other views. GMS_ALLOWABLE_EXPENDITURES is the core Grants table that ties allowable expenditure types to awards and project types. GMS_AWARDS provides award header context, while GMS_PROJECT_TYPES is itself a view supplying project type classification. On the Projects side, PA_EXPENDITURE_TYPES_EXPEND_V is a view over the expenditure type definitions in PA, PA_PROJECTS_ALL supplies project header records, and PA_TASKS supplies task-level detail. The resulting join lets the view present, for each expenditure type/project/task/award combination, the effective date window and operating unit. Because GMS_PROJECT_TYPES and PA_EXPENDITURE_TYPES_EXPEND_V are views rather than tables, any structural change to those underlying views propagates into GMS_PQH_EXP_TYPES_V, reinforcing Oracle's caution against direct dependency.

Key Columns

  • EXPENDITURE_TYPE (VARCHAR2, 30) – The expenditure type name from PA, identifying the cost category.
  • PROJECT_ID (NUMBER, 15) – Foreign key to PA_PROJECTS_ALL identifying the project context.
  • TASK_ID (NUMBER, 15) – Foreign key to PA_TASKS identifying the task within the project.
  • AWARD_ID (NUMBER, 15) – Foreign key to GMS_AWARDS identifying the linked award.
  • EXPND_TYP_START_DATE_ACTIVE (DATE) – The start date from which the expenditure type is active for the given project/task/award combination.
  • EXPND_TYP_END_DATE_ACTIVE (DATE) – The end date on which the expenditure type ceases to be active; a null value typically indicates an open-ended range.
  • ORG_ID (NUMBER, 15) – The operating unit identifier, enabling multi-org security filtering.

Common Use Cases and Queries

Although Oracle discourages direct querying, developers and support analysts frequently inspect this view to diagnose why a particular expenditure type is or is not offered on a Grants transaction form. A typical diagnostic query checks the effective dates for a specific project and award:

  • SELECT expenditure_type, project_id, task_id, award_id, expnd_typ_start_date_active, expnd_typ_end_date_active, org_id FROM apps.gms_pqh_exp_types_v WHERE project_id = :p_project_id AND award_id = :p_award_id;
  • To find currently active expenditure types for an operating unit, filter where SYSDATE BETWEEN NVL(expnd_typ_start_date_active, SYSDATE) AND NVL(expnd_typ_end_date_active, SYSDATE) AND org_id = :p_org_id.
  • To audit date windows, SELECT expenditure_type, expnd_typ_start_date_active, expnd_typ_end_date_active FROM apps.gms_pqh_exp_types_v WHERE expnd_typ_start_date_active > SYSDATE ORDER BY expnd_typ_start_date_active.

Because the view is referenced by APPS.PQH_UTILITY, its primary production role is supplying the Grants forms layer rather than serving as a public reporting interface. Integrations requiring stable expenditure type data should instead query the documented base objects such as PA_EXPENDITURE_TYPES_EXPEND_V or GMS_ALLOWABLE_EXPENDITURES directly.