Results for “pspfv_template_awards”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PSPFV_TEMPLATE_AWARDS is a read-only Oracle EBS database view defined in the PSP (Labor Distribution) product family. It serves as a denormalized reporting and integration layer that joins effort report templates to the awards against which labor effort is recorded. The view exposes a single row for each template-to-award association, enriched with award descriptive attributes drawn from Oracle Grants Accounting. Its principal role is to allow reporting, concurrent programs, and downstream integrations to retrieve award identification and naming information for a given effort reporting template without requiring the calling component to join PSP and GMS base tables directly.
The view is declared with the WITH READ ONLY clause, confirming that it is intended strictly for query access. DML against the view is not supported, and any maintenance of the underlying associations must be performed on the base tables. The ETRM metadata notes the object as "Not implemented in this database," indicating that in the environment where the metadata was harvested the view was not physically present; the definition below reflects the documented ETRM 12.2.2 text.
Underlying Base Objects
The view text identifies three referenced base objects:
- PSP_TEMPLATE_AWARDS (PTA) — the driving table holding the association between a template and an award, supplying TEMPLATE_ID, AWARD_ID, and the standard WHO/audit columns.
- PSP_EFFORT_REPORT_TEMPLATES (PER) — the effort reporting template header, supplying TEMPLATE_NAME.
- GMS_AWARDS_ALL (GAA) — the Oracle Grants Accounting awards table, supplying AWARD_NUMBER, AWARD_SHORT_NAME, and AWARD_FULL_NAME.
The join predicates are equijoins on PTA.AWARD_ID = GAA.AWARD_ID and PTA.TEMPLATE_ID = PER.TEMPLATE_ID. Because GMS_AWARDS_ALL is a _ALL table, the view inherits the multi-org (operating unit) security model of that table. No additional base objects are documented in the ETRM metadata beyond these three tables.
Key Columns
- TEMPLATE_ID — the primary identifier of the effort report template; the join key to PSP_EFFORT_REPORT_TEMPLATES.
- TEMPLATE_NAME — the descriptive name of the effort report template, sourced from the template header.
- AWARD_ID — the internal identifier of the award; the join key to GMS_AWARDS_ALL and the foreign key from PSP_TEMPLATE_AWARDS.
- AWARD_NUMBER — the user-facing award number from Grants Accounting.
- AWARD_SHORT_NAME — the abbreviated award name, commonly used in list-of-values and compact reporting.
- AWARD_FULL_NAME — the complete descriptive title of the award; this is the column most directly associated with the search term "award_full_name" and is typically the human-readable label displayed in reports.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard Oracle WHO audit columns carried forward from PSP_TEMPLATE_AWARDS, supporting change tracking and audit reporting.
Common Use Cases and Queries
Typical uses include listing all awards associated with an effort reporting template, resolving an award name from a template-award association, and feeding award descriptive data into labor distribution extracts.
To list all awards for a specific template by name:
- SELECT template_name, award_number, award_full_name FROM pspfv_template_awards WHERE template_name = :template_name;
To resolve the award full name for a known award identifier:
- SELECT award_number, award_short_name, award_full_name FROM pspfv_template_awards WHERE award_id = :award_id;
To report template-to-award mappings across a range of awards:
- SELECT template_id, template_name, award_id, award_full_name FROM pspfv_template_awards ORDER BY template_name, award_full_name;
Because the view is read-only and defined over GMS_AWARDS_ALL, all queries automatically respect the operating unit context that applies to Grants Accounting award data. Consumers should therefore supply the appropriate org context, or join to organizational security structures, where multiple operating units are in scope.
-
View: PSPFV_TEMPLATE_AWARDS 12.1.1
Not implemented in this database·Explore PSP module →
-
View: PSPFV_TEMPLATE_AWARDS 12.2.2
Not implemented in this database·Explore PSP module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2