Search Results is_ame_reqapprv_workflow




Overview
Explore in AI Chat

Overview

POR_AME_APPROVAL_LIST is an APPS-owned PL/SQL package in Oracle E-Business Suite 12.1.1 and 12.2.2 that mediates between Oracle Purchasing requisition approval processing and the Oracle Approvals Management (AME) engine. Its primary responsibility is to assemble, order, and present the list of approvers for a given requisition header, applying the approval rules configured in AME and translating the resulting approver hierarchy into a delimited string that the Purchasing middle tier can render and process.

The package operates specifically within the purchasing module (application_id 201) and is tied to the PURCHASE_REQ transaction type constant. It supports both the current AME-driven approval path and the legacy (pre-AME) approval list retrieval, which is significant for organizations operating in a mixed or transitional approval configuration. Several error constants define the outcomes of list-manipulation operations, including approver-found, no-next-approver-found, invalid-approver, no-available-insertion, and generic exception states, indicating that the package returns structured status rather than raising naive errors.

Key Procedures and Functions

The documented interface comprises eighteen procedures and functions, several of which are central to the approval-list workflow:

  • GET_AME_APPROVAL_LIST — Builds the current AME-derived approval list for a requisition header, returning the delimited approver string, the count of approvers, the quote character and field delimiter used in the string, and the applicable approval action.
  • GET_OLD_APPROVAL_LIST — Retrieves the pre-AME (legacy) approval list for the same requisition, preserving backward compatibility for installations not fully migrated to AME.
  • CHANGE_FIRST_APPROVER — Replaces the leading approver in the assembled list with a nominated person and returns the updated list.
  • INSERT_APPROVER — Inserts an approver into the list at a specified position, supplying authority, approver category, approver number, insertion type, and approver name.
  • DELETE_APPROVER — Removes an approver from the requisition approval list. This is the object referenced by the delete_approver search term and is the counterpart to the insertion routine, allowing Purchasing forms to prune an approver that the buyer or administrator has chosen to exclude.
  • IS_AME_REQAPPRV_WORKFLOW — Determines whether the requisition is governed by the AME approval workflow.
  • IS_REQ_PRE_APPROVED — Indicates whether the requisition has already been pre-approved.
  • GET_FIRST_AUTHORITY_APPROVER — Identifies the first approver holding the required authority level.
  • CAN_DELETE_OAM_APPROVERS — Validates whether deletion of OAM (Oracle Approval Management) approvers is permissible.
  • RETRIEVE_APPROVAL_INFO / RETRIEVE_APPROVER_INFO — Return descriptive metadata about the approval list and individual approvers respectively.
  • GET_APPROVAL_GROUP_NAME — Resolves the approval group name associated with the requisition.
  • GET_AME_APPROVAL_LIST_HISTORY — Returns historical approval-list information for auditing and display.
  • GETAMETRANSACTIONTYPE — Returns the AME transaction type for the transaction.
  • GET_NEXT_APPROVERS_INFO — Returns information about the approvers who follow the current approver.
  • GET_PERSON_INFO — Retrieves person details used to label approvers in the list.
  • IS_REQ_FORWARD_VALID — Validates whether a requisition can be forwarded.
  • CLEAR_AME_APPRV_LIST_REJECT — Clears rejection state on the AME approval list.

Tables Accessed

The package reads and writes against the core Purchasing and HR tables that underlie requisition approval. PO_REQUISITION_HEADERS and PO_REQUISITION_HEADERS_ALL supply the requisition being processed, while PO_ACTION_HISTORY, PO_CHANGE_REQUESTS, and PO_DOCUMENT_TYPES (with PO_DOCUMENT_TYPES_ALL and PO_DOCUMENT_TYPES_ALL_B) provide workflow history, change-request context, and document-type configuration. PLITBLM is used for name/value list handling, particularly for displaying approver strings. On the HR side, PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_ALL_POSITIONS, PER_ASSIGNMENT_STATUS_TYPES, and PER_JOBS resolve approver identity, assignment, position, and job details. FND_USER provides the E-Business Suite user identity associated with each approver. All access is through APPS synonyms.

Usage Notes

POR_AME_APPROVAL_LIST is not a public API in the sense of a documented integration interface; it is invoked primarily by Purchasing forms and workflow notification code rather than by customer-written programs. The package is referenced by four other packages, indicating that the approval-list assembly logic is reused across the requisition lifecycle. The delete_approver procedure in particular is exercised when a user adjusts the approver list from the requisition approval user interface. Custom code should avoid direct invocation because the package relies on internal constants, the PLITBLM string format, and AME configuration state; modifications to approver lists should instead go through supported Purchasing forms or AME configuration.