Search Results psp_effort_reports_s

Overview

The APPS.PSP_CREATE_EFF_REPORTS package body is a core component of the Oracle E-Business Suite Effort Reporting (part of Oracle Projects / Grants Management) module. Its principal business function is to generate effort reports — the periodic statements of effort certification required under OMB Circular A-133, Uniform Guidance, and institutional sponsored-research policies — from the underlying payroll, assignment, and project-transaction data captured in Oracle HRMS and Oracle Projects.

The package reads payroll action results, assignment actions, and project/task expenditure information, consolidates them into effort-report header and detail records, and persists them in the PSP effort-reporting tables. It also performs validation against project, task, award, and organization/employee (PTAOE) combinations and writes any processing exceptions to the PSP_REPORT_ERRORS infrastructure. The package is registered as a VALID package body in the APPS schema and is classified generically as an "OTHER" API — i.e., it is not exposed via the standard PL/SQL API naming conventions, but is called from concurrent programs and internal Effort Reporting logic.

Key Procedures and Functions

The documented package exposes seven procedures/functions:

• PSPREP_INIT — Initialization routine for the effort-reporting run. It establishes the concurrent request context, profile settings (via FND_PROFILE and FND_GLOBAL), and any run-time parameters required by subsequent processing steps.
• EFFORT_ASG_ACTION_CODE — Derives or resolves the assignment action code associated with an effort-reporting event. This is used to correlate payroll/assignment action records (PAY_ASSIGNMENT_ACTIONS_S) with effort-report output.
• EFFORT_ARCHIVE — Archives previous effort-report output, allowing a re-run to supersede or preserve prior versions while maintaining audit trails.
• CREATE_EFFORT_REPORTS — The primary driver. It builds the effort-report headers and detail rows from the selected population of persons, assignments, and project transactions, and writes them to the PSP effort-report tables.
• POPULATE_EFF_TABLES — Bulk-loads the staging/selection tables (e.g., PSP_SELECTED_PERSONS_T, PSP_SUPERCEDE_PERSONS_GT) with the persons and assignment rows targeted for reporting, based on the template selection logic.
• POPULATE_ERROR_TABLE — Transfers validation exceptions and processing messages into the error tables (PSP_REPORT_ERRORS / PSP_REPORT_ERRORS_S) and associated message infrastructure (PSP_MESSAGE_S) for user review.
• VALIDATE_PTAOE — Validates the Project, Task, Award, Organization, and Employee (PTAOE) combination for each effort-report line, ensuring the referenced project/task/award/employee data is valid before certification.

Tables Accessed

The package reads and writes the following documented tables (via APPS synonyms):

• Payroll and HRMS sources: PAY_ASSIGNMENT_ACTIONS_S, PAY_PAYROLL_ACTIONS, PAY_TEMP_OBJECT_ACTIONS, PER_ALL_ASSIGNMENTS_F, PER_ALL_PEOPLE_F — provide the employee, assignment, and payroll-action basis for effort computations.
• Project sources: PA_PROJECTS_ALL, PA_TASKS_EXPEND_V, and PSP_ADJUSTMENT_LINES — supply project/task context and any manual effort adjustments.
• Effort-report output: PSP_EFF_REPORTS (headers) and PSP_EFF_REPORT_DETAILS (lines), with surrogate keys from PSP_EFFORT_REPORTS_S and PSP_EFF_REPORT_DETAILS_S, and PSP_EFF_REPORT_DETAILS_API for programmatic writes.
• Error/message tables: PSP_REPORT_ERRORS and PSP_REPORT_ERRORS_S — the search term "psp_report_errors_s" maps directly here; this is the error-capture table written by POPULATE_ERROR_TABLE.
• Concurrent management: FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS — used to identify the running concurrent request and its parameters. FND_FILE is used for log/output writes; FND_MESSAGE, FND_DATE, FND_API, and PSP_XMLGEN provide messaging, date conversion, API error-handling, and XML generation utilities.

Usage Notes

PSP_CREATE_EFF_REPORTS is invoked primarily through the Effort Reporting concurrent program that generates effort reports for a selected reporting period and population. It is not intended for direct ad-hoc calls from end users, and its procedures assume the concurrent manager session context (FND_GLOBAL, FND_CONCURRENT_REQUESTS) is already established.

Effort Reporting administrators typically schedule the generating concurrent program after payroll costing and project transactions have been processed for the period. Output is written to the PSP effort-report tables and can then be reviewed through the Effort Reporting workbench and certification forms. Errors encountered during PTAOE validation or data consolidation appear in PSP_REPORT_ERRORS / PSP_REPORT_ERRORS_S and should be resolved before the reports are released for certification.

Because the package body is not referenced by any other database object, it functions as a top-level entry point; custom code integrating with Effort Reporting should invoke the concurrent program rather than call the package directly, to preserve audit, logging, and error-handling behavior maintained through FND_API and PSP_MESSAGE_S.