Search Results get_first_approvers

Overview

PSP_ER_AME is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Effort Reporting module of Oracle Projects. Its primary role is to integrate Effort Reporting approval processing with Oracle Approvals Management (AME). The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the package owner, and it is classified in the ETRM repository as an OTHER API rather than a fully documented public API.

The package exists to resolve the approvers required for effort report records when approval type is configured as CUSTOM. Rather than leaving approver determination entirely to the AME engine, PSP_ER_AME coordinates a controlled invocation of AME, applying a built-in optimization so that AME is not called redundantly for every effort detail row. The optimization is driven by the global variable G_APPROVER_BASIS, a concatenated string of effort detail attributes (for example "Assignment, Expenditure_Type"). When this variable is set, AME is invoked only for each distinct combination of the specified attributes, mirroring the optimization that is already hard-coded for seeded approval options such as "Principal Investigator of Grant".

Key Procedures and Functions

The ETRM metadata documents a single public procedure: GET_FIRST_APPROVERS.

• GET_FIRST_APPROVERS — Determines and returns the first-level approvers for a set of effort report records. The procedure is driven by a request identifier and a person range, allowing the caller to define a bounded scope of people whose effort reports are being processed. It returns a status indicator to the caller so that calling programs can detect success or failure, and it accepts an optional retry request identifier used when reprocessing a previously failed or interrupted run. Internally the procedure builds the approver basis from effort detail attributes and invokes AME on a per-distinct-combination basis rather than per detail row.

No additional documented functions are exposed by this package, and the parameter lists documented above should be treated as the authoritative interface.

Tables Accessed

PSP_ER_AME reads and writes a focused set of Effort Reporting and Oracle Human Resources tables through APPS synonyms:

• PSP_EFF_REPORTS — the header effort report records being approved.
• PSP_EFF_REPORT_DETAILS — the effort detail rows that supply the attribute values used to build G_APPROVER_BASIS.
• PSP_EFF_REPORT_APPROVALS and PSP_EFF_REPORT_APPROVALS_S — the approval records where determined approvers are stored; the _S table is the sequence/primary key source.
• PSP_REPORT_TEMPLATES_H — provides the template definition, including the approval type and summarization criteria.
• PSP_REPORT_ERRORS and PSP_REPORT_ERRORS_S — capture errors encountered during approver resolution so they can be reviewed or retried.
• PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F — resolve person and assignment context for AME evaluation.
• FND_USER — used to map application users to persons where required.
• DUAL and PLITBLM — utility references; PLITBLM is the standard PL/SQL index-by table type used for internal collections.

Usage Notes

PSP_ER_AME is not intended for direct end-user invocation. It is called programmatically by the Effort Reporting approval workflow, typically from concurrent programs or from other Effort Reporting packages (the metadata records one package as referencing it). Customizations that need to trigger or re-trigger approver resolution should invoke GET_FIRST_APPROVERS with a valid request identifier and the appropriate person range, supplying the retry request identifier only when reprocessing a failed run.

Because the package is AUTHID CURRENT_USER and classified as an internal API, the interface is subject to change between releases; custom code should avoid reimplementing the approver-basis logic and should instead rely on the seeded CUSTOM approval type configuration and the G_APPROVER_BASIS optimization, which prevents excessive AME invocations when a person has many distinct project, award, task, or expenditure type combinations.