Search Results psp_effort_report_templates




Overview
Explore in AI Chat

Overview

The PSP_EFFORT_REPORT_TEMPLATES table is a core data object within the Oracle E-Business Suite (EBS) Labor Distribution module (PSP). It serves as the master repository for defining the criteria and configuration of effort reporting templates. These templates are fundamental to the effort certification process, which is a critical compliance function for organizations, particularly in research, government contracting, and higher education, to verify that labor charges align with actual effort expended on projects and awards. The table stores the high-level definition of a report, which is then used to generate individual effort reports for employees or contingent workers based on specific time periods and labor distribution data.

Key Information Stored

The table's primary key is the TEMPLATE_ID, a unique system-generated identifier. Based on the documented foreign key relationships, the table stores key configuration parameters that define the scope and rules for an effort report. This includes links to the reporting period (EFFORT_REPORT_PERIOD_NAME), the set of books (SET_OF_BOOKS_ID) for financial context, and the business group (BUSINESS_GROUP_ID) for HR security. It also holds references to default accounting and project data, such as a default GL code combination (GL_CODE_COMBINATION_ID), a default task (TASK_ID), and a default expenditure type (ELEMENT_TYPE_ID). The PEOPLE_GROUP_ID links to a defined group of employees, allowing the template to target specific populations. Additional descriptive columns, not explicitly listed but typical for such control tables, would include fields for the template name, description, status, and various control flags.

Common Use Cases and Queries

The primary use case is the setup and generation of effort reports for compliance audits. Administrators define templates to specify which employees, during which period, and for which projects or awards effort must be certified. Common queries involve listing active templates, diagnosing report generation issues, or analyzing template coverage. A typical SQL pattern retrieves template details with their associated period and business group information:

  • SELECT t.template_id, t.template_name, t.effort_report_period_name, hou.name business_group FROM psp_effort_report_templates t, hr_all_organization_units hou WHERE t.business_group_id = hou.organization_id AND t.enabled_flag = 'Y';

Another critical query joins to child tables to understand the full scope of projects or awards included in a specific template, which is essential for troubleshooting why certain labor distributions appear or do not appear on a generated report.

Related Objects

PSP_EFFORT_REPORT_TEMPLATES is a central hub with numerous foreign key relationships. It is the parent table for several detail tables that define the specific scope of a template: PSP_TEMPLATE_PROJECTS, PSP_TEMPLATE_AWARDS, and PSP_TEMPLATE_ORGANIZATIONS. The generated reports and any associated errors are stored in child tables PSP_EFFORT_REPORTS and PSP_EFFORT_ERRORS, linked via TEMPLATE_ID. For configuration and default values, it references key setup tables across EBS modules: PSP_EFFORT_REPORT_PERIODS (PSP), PAY_PEOPLE_GROUPS (Payroll), GL_CODE_COMBINATIONS and GL_SETS_OF_BOOKS_11I (General Ledger), PA_EXPENDITURE_TYPES and PA_TASKS (Projects), and HR_ALL_ORGANIZATION_UNITS (Human Resources).