Search Results gp_pk

Overview

GMS_PROJECT_TYPES is a reference (lookup) table within the Oracle EBS Grants Accounting (GMS) module. It stores the valid project type classifications that can be assigned to grant-funded and sponsored projects. In the Oracle EBS data model, project type is a segment-level classification used throughout Grants Accounting to filter, group, and report on projects by their funding nature, award characteristics, or administrative category. Because the table functions purely as a controlled vocabulary of codes and their descriptive attributes, it does not carry transactional or historical state.

The ETRM metadata records that this object is not implemented in the database from which the documentation was mined, and that the heuristic Data Vault classification is standalone. Under a Data Vault modeling convention, this suggests the table would map most naturally to a hub for project type (with the natural business key PROJECT_TYPE), optionally paired with a small satellite for descriptive attributes. No foreign-key relationships were mined, reinforcing its position as an independent reference entity rather than a link or dependent satellite.

Key Information Stored

The documented metadata identifies only two meaningful columns, which is consistent with a lean code table:

• GP_PK — The surrogate primary key of the table. It uniquely identifies each project-type row and is used for internal referential integrity. GP_PK is the documented primary key of GMS_PROJECT_TYPES.
• PROJECT_TYPE — The business-key candidate. This is the meaningful code or name that other Grants Accounting objects and reports reference when classifying a project. Because it is the human-readable discriminator, PROJECT_TYPE is expected to be unique in practice and is the column joined against in downstream queries.

Descriptive columns such as a project-type name or description are typical of a GMS lookup of this kind, but the documented metadata does not enumerate them, so consumers should verify the actual column list against their instance (for example, via ALL_TAB_COLUMNS on GMS_PROJECT_TYPES) before relying on any attribute beyond GP_PK and PROJECT_TYPE.

Common Use Cases and Queries

This table is most commonly used to drive drop-down lists and validation logic on project setup forms, and to decorate project reports with a readable project-type label. Typical usage patterns include:

• Populating LOVs and picklists during award or project definition, restricting users to valid project types.
• Joining to project/award tables to translate a stored project-type code into a descriptive label for reporting.
• Grouping and filtering grant portfolios by project type for compliance and sponsor reporting.

Representative SQL patterns:

• Listing all defined types: SELECT gp_pk, project_type FROM gms_project_types ORDER BY project_type;
• Decorating a project query: SELECT p.project_number, t.project_type FROM ... p, gms_project_types t WHERE p.project_type = t.project_type;
• Counting projects per type for a portfolio summary: SELECT t.project_type, COUNT(*) FROM gms_project_types t JOIN <project> p ON p.project_type = t.project_type GROUP BY t.project_type;

Because this table is documented as not implemented in the source database, sites on other instances should confirm it is populated and enabled before depending on it in concurrent programs or reports.

Related Objects

The documented metadata reports no foreign-key relationships (standalone classification), so the following represent the most significant objects that would logically reference or depend on GMS_PROJECT_TYPES through the PROJECT_TYPE value rather than through an enforced FK constraint:

• GMS_PROJECTS / Grants project base tables — store the assigned PROJECT_TYPE value for each sponsored project.
• Award and award-project tables in GMS — carry project-type classification for award funding and reporting.
• Grant Accounting lookup and validation code — uses PROJECT_TYPE as the valid-values source for project classification fields.
• Reporting views over GMS projects — join on PROJECT_TYPE to produce descriptive portfolio and compliance reports.
• Concurrent programs and Standard Reports in Grants Accounting — filter project sets by the codes defined here.

Because no real FK data was mined, the join column to assume across these objects is PROJECT_TYPE (business key), with GP_PK reserved for internal row identity.