Search Results get_emd_update_url

Overview

The APPS.PON_AUCTION_APPROVAL_PKG package body encapsulates the PL/SQL routines that drive the approval lifecycle for Oracle Sourcing negotiations and auctions. It is the server-side engine behind approval workflow activities such as submitting a negotiation for approval, collecting approver decisions, updating document status, and dispatching and resolving Oracle Workflow notifications. Because it is classified as an OTHER API, it is intended primarily for internal consumption by the Sourcing application and its workflow-integrated components rather than as a public, supported extension point.

The package body header identifies the source file as PONAPPRB.pls. Its documented history includes fixes such as Bug 4295915 (missing owner in Sourcing notifications, resolved by a call to WF_ENGINE.SetItemOwner) and ECO 4456420, which added setting of ORIGIN_USER_NAME to the current user for most operations. These entries confirm the package's tight coupling to Oracle Workflow and to the identity of the acting user.

Key Procedures and Functions

The package exposes 24 documented procedures and functions. The main approval-cycle routines are:

• SUBMIT_FOR_APPROVAL – Initiates the approval process for a negotiation document.
• STARTUSERAPPROVALPROCESS – Launches the user approval workflow for the document.
• STARTEMDAPPROVALPROCESS – Launches the approval workflow associated with the EMD (electronic media/document) path.
• USER_APPROVED / USER_REJECTED – Record an individual approver's decision within the workflow.
• USER_DECISION_WITHOUT_WF – Applies an approver decision without invoking the standard workflow path.
• DOC_APPROVED / DOC_REJECTED / DOC_TIMEDOUT – Resolve the document-level outcome once decisions are complete or a timeout elapses.
• EMD_USER_APPROVED / EMD_USER_REJECTED – Apply approver decisions on the EMD approval path.
• UPDATE_DOC_TO_CANCELLED and CANCEL_NOTIFICATION – Cancel the document's approval state and any outstanding notifications.
• UPDATE_NOTIF_ONLINE and SET_NOTIFICATION_SUBJECT – Maintain notification content, status, and subject lines.
• UPD_AUCTION_STATUSHISTORY – Write status-history records tracking the negotiation's progression.
• CLOSE_CHILD_PROCESS – Terminate child workflow processes spawned by the approval.
• GET_EMD_HEADERID, GET_CNF_DOC_PARAMS_WF, and CREATE_CNF_DOC_CLM – Support retrieval of EMD header identity and construction of confirmation-document parameters and claims for workflow processing.

Tables Accessed

The package operates against the following documented APPS synonyms:

• PON_AUCTION_HEADERS_ALL – The negotiation/auction header, holding document state and status.
• PON_AUCTION_WF_APPROVALS_S – Stores the approval records tying documents to workflow items and approvers.
• PON_ACTION_HISTORY – Action-history audit trail for negotiation events.
• PON_AUC_DOCTYPES – Document type definitions that drive approval routing.
• PON_NEG_TEAM_MEMBERS – Negotiation team members eligible as approvers.
• WF_NOTIFICATIONS and FND_NEW_MESSAGES – Notification generation and messaging in the workflow notification store.
• WF_ITEM_ACTIVITY_STATUSES – Workflow activity status used to determine where an approval stands.
• FND_USER and PER_ALL_PEOPLE_F – User and person identity resolution for approvers and notification owners.
• DUAL – Singleton queries for lookups and profile-based constructs.

Usage Notes

In EBS 12.1.1 and 12.2.2, this package is invoked from the Oracle Sourcing forms and OAF pages when a buyer submits a negotiation, and from Oracle Workflow function activities as approvers act on notifications. The notification-handling routines (CANCEL_NOTIFICATION, UPDATE_NOTIF_ONLINE, SET_NOTIFICATION_SUBJECT) execute as workflow callbacks, so mail and worklist links resolve back into this package. Profile options such as PON_EXT_APPS_FRAMEWORK_AGENT and APPS_FRAMEWORK_AGENT influence the construction of EMD update URLs, as shown by GET_EMD_UPDATE_URL.

Because the package is classified as OTHER and is referenced by only one other package, custom code should not call it directly; supported integration should instead use the Sourcing functional flows or the workflow APIs. Direct invocation risks conflict with concurrent workflow processing and with the internal state maintained in PON_AUCTION_WF_APPROVALS_S. The search term conc_req_submitted does not correspond to a documented routine in this package; that identifier appears in Oracle Purchasing/Requisition workflow contexts rather than in the Sourcing negotiation approval body, and its presence in a query likely reflects tracing a workflow item attribute across the requisition-to-sourcing boundary rather than a callable element of PON_AUCTION_APPROVAL_PKG.