Search Results get_current_approver

Overview

OE_APPROVALS_WF is the Oracle Order Management approval workflow package. It provides the PL/SQL plumbing that drives the approval process attached to sales orders, blanket sales agreements, and the associated Oracle Workflow process types. Where the seeded Oracle Workflow definition models the approval steps as activities, OE_APPROVALS_WF supplies the named PL/SQL functions that each activity invokes at runtime.

The package therefore bridges three subsystems: Oracle Order Management, which owns the transaction documents; Oracle Workflow, which owns the process, statuses, notifications, and routing; and Oracle Approvals Management (AME), which supplies the routed approver list when the AME-based approval mode is in use. It supports both the classic approver-list approval path and the newer AME-driven path, and it exposes the internal helper functions needed to evaluate next approvers, detect AME exceptions, and translate AME responses back into the workflow.

The header identifies the API as Public, version 1.0, defined in source file OEXWAPRS.pls. The package is owned by APPS and is classified in the ETRM documentation as OTHER. It is a self-contained utility package: it is referenced by zero other packages, meaning call sites are workflow activity assignments and internal consumers rather than inter-package dependencies.

Key Procedures and Functions

The documented surface is composed of the interface procedures and functions invoked by workflow activities, plus internal helpers and AME integration routines.

• INITIATE_APPROVAL — starts the approval process for a document.
• GET_NEXT_APPROVER and GET_NEXT_APPROVER_INTERNAL — determine the next approver in the sequence; the internal variant takes a transaction identifier, item type, sales document type code, and optional query mode, and returns the approver as a VARCHAR2.
• REJECT_APPROVAL — records and routes a rejection outcome.
• APPROVE_APPROVAL — records and routes an approval outcome.
• APPROVAL_TIMEOUT and APPROVAL_TIMEOUT_AME — handle timeout outcomes for the standard and AME-driven paths respectively.
• GET_CURRENT_APPROVER and GET_CURRENT_APPROVER_INTERNAL — return the currently acting approver.
• GET_SALES_DOCUMENT_TYPE — resolves a document to its sales document type for routing and display.
• GET_AME_APPROVERS_LAUNCH, IS_AME_EXCEPTION, USE_AME_APPROVAL, and TREAT_AME_EXCEPTION_AS — call into AME, decide whether AME approval applies, detect and classify AME exceptions.
• GET_NOTIFICATION_ATTRIBUTES — populates item attributes used in approval notifications.
• PROCESS_RESPONSE_APPROVE, PROCESS_RESPONSE_REJECT, and PROCESS_BEAT_BY_FIRST — interpret approver responses, including the first-responder-wins rule.
• CHECK_PARALLEL_WF_STATUS — inspects the status of a parallel workflow branch.
• PUSH_BLOCK_ACTIVITY — surfaces the blocking activity for the document.

Tables Accessed

The package reads and writes the core Order Management approval tables through APPS synonyms:

• OE_APPROVER_LISTS, OE_APPROVER_LIST_MEMBERS, OE_APPROVER_TRANSACTIONS — define approver lists, their membership, and the approval state of each transaction.
• OE_ORDER_HEADERS_ALL, OE_BLANKET_HEADERS_ALL, OE_BLANKET_HEADERS_EXT, OE_TRANSACTION_TYPES_ALL — supply the document under approval and the document type driving routing rules.
• OE_AME_PARALLEL_S — tracks parallel AME workflow activity state.
• AP_INV_APRVL_HIST — the approval history store.
• PER_ALL_ASSIGNMENTS_F, PER_ALL_PEOPLE_F, FND_USER, HZ_PARTIES — resolve approver identities, assignments, and party information.
• FND_LOOKUP_VALUES, FND_LANGUAGES — supply lookup codes and language-specific display values.

Usage Notes

OE_APPROVALS_WF is not called directly by end users. Its procedures and functions are bound to Oracle Workflow activities in the Order Management approval process type, so the workflow engine invokes the appropriate routine as each activity executes. The itemtype, itemkey, actid, funcmode, and resultout signatures confirm this: they are the standard Workflow-standard activity callback parameters, with funcmode indicating whether the activity is running in RUN, CANCEL, or TIMEOUT mode.

Customizations and extensions typically interact with this package in two ways. First, by adding or modifying approver lists and members in the OE_APPROVER_* tables, which the package reads when resolving the next or current approver. Second, by extending or replacing workflow activities so that they point at custom packages while still calling these routines for identity resolution, response interpretation, and AME integration. Because the package is referenced by no other package, it can be deployed or patched in isolation, but any change to its public signatures or to the approval tables will affect the seeded approval workflow and must be regression tested against both the standard and AME-driven approval paths in Oracle EBS 12.1.1 and 12.2.2.