Search Results psp_effort_report_details




Overview
Explore in AI Chat

Overview

The PSP_EFFORT_REPORT_DETAILS table is a core transactional data object within the Oracle E-Business Suite (EBS) Labor Distribution module (PSP). It functions as the detailed line-item repository for effort reports, which are critical documents used to certify and distribute payroll and labor costs to appropriate funding sources, such as grants, projects, or general ledger accounts. Each record in this table represents a specific charging line on an effort report, linking a portion of an individual's compensated effort to a particular project, task, expenditure type, and accounting code combination. Its primary role is to store the auditable detail that supports the financial distribution of labor expenses, ensuring compliance with internal policies and external regulatory requirements.

Key Information Stored

The table's structure is defined by a composite primary key consisting of EFFORT_REPORT_ID, VERSION_NUM, and EFFORT_REPORT_LINE_NUM, which uniquely identifies each detail line across all versions of an effort report. Key columns include foreign key references to define the charging context: PROJECT_ID and TASK_ID from Oracle Projects, ELEMENT_TYPE_ID (linking to both PSP_EFFORT_REPORT_ELEMENTS and PA_EXPENDITURE_TYPES), and GL_CODE_COMBINATION_ID for the target general ledger account. The EXPENDITURE_ORGANIZATION_ID links to the HR organization unit. Crucially, the table stores the percentage or amount of effort being charged to the specified combination for the report period, forming the basis for cost distribution calculations.

Common Use Cases and Queries

A primary use case is the generation of detailed audit trails for effort certification and labor cost distribution. Financial analysts run queries against this table to reconcile certified effort with posted journal entries. Common SQL patterns involve joining to parent and reference tables to produce human-readable reports. For example, a query to list all detail lines for a specific effort report would join PSP_EFFORT_REPORTS for header information and reference tables like PA_PROJECTS_ALL and GL_CODE_COMBINATIONS for descriptive values. Another critical use case is supporting the recalculation and adjustment process when effort reports are revised (indicated by VERSION_NUM), where historical detail lines are preserved for audit purposes. System interfaces and custom reports also query this table to extract distributed labor costs for project accounting and grant management reporting.

Related Objects

PSP_EFFORT_REPORT_DETAILS maintains integral relationships with several key EBS tables, primarily through foreign key constraints. The documented relationships are as follows:

  • PSP_EFFORT_REPORTS: The parent table. Joined via EFFORT_REPORT_ID and VERSION_NUM to retrieve header-level information like the employee, certification status, and report period.
  • PSP_EFFORT_REPORT_ELEMENTS: Joined via ELEMENT_TYPE_ID to access labor distribution-specific element setup.
  • PA_EXPENDITURE_TYPES: Also joined via ELEMENT_TYPE_ID to obtain the standard Oracle Projects expenditure type.
  • PA_PROJECTS_ALL: Joined via PROJECT_ID to retrieve the charged project details.
  • PA_TASKS: Joined via TASK_ID to retrieve the charged task details.
  • GL_CODE_COMBINATIONS: Joined via GL_CODE_COMBINATION_ID to obtain the target accounting flexfield combination.
  • HR_ALL_ORGANIZATION_UNITS: Joined via EXPENDITURE_ORGANIZATION_ID to identify the incurring organization.

These relationships are essential for any comprehensive reporting or data validation involving certified labor distributions.