Search Results g_approver_basis

Overview

PSP_ER_AME (Effort Reporting – Approvals Management Engine integration) is an Oracle Applications package body owned by the APPS schema that supports the Oracle E-Business Suite self-service Effort Reporting module, part of the Enterprise Project Management and Grants Accounting family of applications. Its primary business function is to determine and persist the first-level approvers for effort reports generated by employees, so that the subsequent approval workflow can route each report to the correct manager or designated approver based on the reporting hierarchy and assignment relationships defined in Oracle HR. The package consolidates report detail rows, resolves the responsible person through the assignments and people tables, records any approver determination against the effort report approval records, and provides a centralized error handling mechanism that writes messages to the reporting framework for later review by administrators.

The package header carries a source control identifier dated 2005, indicating the object originated in the earlier 11i generation and has been carried forward into EBS 12.1.1 and 12.2.2 with minimal or no functional change. It is classified as an "OTHER" API in the ETRM metadata, meaning it is not a formally published public API but a supporting internal routine invoked by the Effort Reporting concurrent programs and forms.

Key Procedures and Functions

• GET_FIRST_APPROVERS — The single documented procedure in this package and the routine the user searched for. It accepts a request identifier together with a starting and ending person range, returns a status value, and optionally accepts a retry request identifier. Its purpose is to iterate over effort report records within the specified person range, resolve the first approver for each report using HR assignment and people data, and record the resulting approver against the effort report approval records. Internally it declares a record structure containing effort report detail identifiers, person, assignment, project, award, task, expenditure organization and expenditure type attributes, plus a large set of descriptive flexfield segments (segment1 through segment28), reflecting the need to carry full project and award accounting context through the approver determination logic.
• INSERT_ERROR — A private (undocumented in the public API list) error-logging procedure in the package body. It delegates to PSP_GENERAL.ADD_REPORT_ERROR to write an error message for a given request, source and message level, and raises an exception if the logging call itself returns an error status, ensuring that failures during approver resolution are not silently lost.

The body also declares internal exceptions including no_approver_found, populate_error and failed_insertion, plus a package-level variable g_retry_request_id used to carry retry context between calls.

Tables Accessed

• PSP_EFF_REPORTS and PSP_EFF_REPORT_DETAILS — the core effort report and report line tables read to identify which reports require approvers.
• PSP_EFF_REPORT_APPROVALS and PSP_EFF_REPORT_APPROVALS_S — written with the resolved first approver for each report, forming the basis of the approval history.
• PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F — read to resolve the person and assignment of the report owner and to establish supervisory or assignment-based approver relationships.
• FND_USER — read to map the resolved approver to a valid application user for workflow routing.
• PSP_REPORT_ERRORS and PSP_REPORT_ERRORS_S — written via the error insertion routine to record determination failures.
• PSP_REPORT_TEMPLATES_H — read for report template configuration that governs approval rules.
• DUAL and PLITBLM — used for scalar evaluation and for bulk PL/SQL table operations.

Usage Notes

PSP_ER_AME is not intended for direct invocation by end users or custom integrators. It is called by the Effort Reporting approval processing logic — typically a concurrent program or the self-service Effort Reporting form flow — during the stage in which approvers are derived. The ETRM metadata records that it is referenced by one other package, confirming its role as a downstream dependency rather than an entry point. When the approver resolution fails to identify a valid approver, the package raises internal exceptions and writes diagnostic messages through PSP_REPORT_ERRORS so administrators can review them and, where applicable, re-run processing using the retry request identifier parameter supported by the procedure.