Search Results psp_report_templates




Overview
Explore in AI Chat

Overview

The PSP_REPORT_TEMPLATES table is a core data object within the Oracle E-Business Suite (EBS) Labor Distribution module (PSP). It serves as the primary repository for the definition and configuration of Effort Report templates. Effort reporting is a critical compliance and accounting function, particularly in environments such as higher education and government contracting, where labor costs must be certified and allocated to specific projects or funding sources. This table stores the master template definitions that govern the layout, content, and rules for generating these standardized reports, enabling organizations to consistently track and certify employee effort against grants, projects, and other awards.

Key Information Stored

While the provided metadata does not list specific columns, the primary key and foreign key relationships define its essential structure. The central column is TEMPLATE_ID, which uniquely identifies each effort report template. Based on its role, the table likely stores descriptive and control attributes for each template, such as the template name, effective dates, status (e.g., Active, Inactive), associated business group, and configuration flags that determine report behavior. These flags could control aspects like certification requirements, display formats for cost information, and the inclusion of specific data sections. The TEMPLATE_ID is the critical foreign key referenced by child tables that store the detailed components of the template.

Common Use Cases and Queries

The primary use case is the administration and generation of certified effort reports. System administrators query this table to manage the lifecycle of templates, while the application uses it to retrieve the active template for a given employee or project during report generation. Common SQL operations include retrieving a list of all active templates for a business group or identifying the template assigned to a specific project or operating unit. A typical query pattern would join PSP_REPORT_TEMPLATES with related setup tables, such as HR_ORGANIZATION_UNITS, to filter templates by organization.

  • Sample Query: SELECT template_id, template_name, effective_start_date, effective_end_date FROM psp_report_templates WHERE business_group_id = :p_bg_id AND sysdate BETWEEN effective_start_date AND NVL(effective_end_date, sysdate);

Related Objects

The most direct relationship, as documented, is with the PSP_REPORT_TEMPLATE_DETAILS table. This child table holds the specific lines, columns, and criteria that constitute the body of the report template, linked via the TEMPLATE_ID foreign key. In a broader functional context, PSP_REPORT_TEMPLATES is integral to the Effort Reporting workflow. It is referenced by the core effort reporting tables (e.g., PSP_EFFORT_REPORTS, PSP_REPORT_LINES) to determine which template rules apply to a given report instance. The data is typically accessed via the application's public interfaces or through dedicated APIs within the PSP_ packages, rather than via direct SQL in a production environment.