Search Results get_po_user_msg_attribute




Overview
Explore in AI Chat

Overview

PO_WF_PO_NOTIFICATION is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as a notification-generation utility within the Purchasing module. Its principal business role is to assemble, format, and render the content of Oracle Workflow notification messages that are raised against purchasing documents — most notably purchase orders and purchase order distributions — during approval routing and post-approval processing. Because Purchasing approval in Release 12.1.1 and 12.2.2 is orchestrated by the PO Approval workflow (POAPPRV), notification bodies cannot rely on static message text; they must be built dynamically from live document data such as supplier, operating unit, currency, ship-to location, line, and unit of measure information. PO_WF_PO_NOTIFICATION encapsulates that dynamic assembly logic, exposing typed functions that the Workflow engine calls when constructing the notification payload presented to approvers and requesters.

The package is self-contained in terms of call dependents: no other package in the APPS schema references it, which confirms that it is invoked by the workflow layer rather than by other PL/SQL APIs. Only the SYS.STANDARD package is an inbound dependency, and the APPS.PO_WF_PO_NOTIFICATION package body itself is listed as an internal reference. The object carries a VALID status in the documented environment.

Key Procedures and Functions

Seven documented program units are exposed, each supporting a distinct aspect of notification content or document context evaluation:

  • GET_PO_APPROVE_MSG — Assembles the primary approval notification message text for a purchase order, producing the human-readable body that an approver reviews when acting on a routing step.
  • GET_PO_LINES_DETAILS — Retrieves and formats purchase order line-level detail for inclusion in a notification, allowing approvers to see item, quantity, and measurement information without opening the document.
  • GET_ACTION_HISTORY — Returns the approval action history associated with a document, so that the notification can present the sequence of prior approvals, rejections, or reassignments.
  • POST_APPROVAL_NOTIF — Drives notification activity that occurs after approval has been completed, such as informing the requester or buyer that the document has progressed.
  • GET_PO_USER_MSG_ATTRIBUTE — Resolves a user-defined or message attribute value used to personalize the notification content for a specific recipient.
  • GETDISPLAYVALUE — Performs display-value resolution, converting stored codes into user-facing descriptions for presentation in the notification body.
  • IS_OPEN_DOCUMENT_ALLOWED — Evaluates whether the document may be opened from the notification, supporting security and document-viewing context rules.

Parameter lists are not documented and should not be assumed; callers should obtain signatures from the package specification in the target environment.

Tables Accessed

The package reads through APPS synonyms across several functional areas. Purchasing document data comes from PO_DOCUMENT_TYPES and PO_DOCUMENT_TYPES_TL (document type name translation), PO_DISTRIBUTIONS (account and charge distribution detail), PO_ACTION_HISTORY (approval audit trail), and MTL_SYSTEM_ITEMS_KFV and MTL_UNITS_OF_MEASURE (item and UOM presentation). Supplier and location context is resolved via HZ_PARTIES, HZ_LOCATIONS, and HR_LOCATIONS_ALL. Personnel and user identity come from PER_ALL_PEOPLE_F and FND_USER. Currency and language presentation rely on FND_CURRENCIES and FND_LANGUAGES, while FINANCIALS_SYSTEM_PARAMETERS supplies operating unit defaults. FND_NEW_MESSAGES provides the Workflow message repository entries that the notification text populates. Writes are not documented explicitly but are implied for notification output.

Usage Notes

PO_WF_PO_NOTIFICATION is not a standalone API and should not be called directly by custom extensions expecting a general-purpose interface. It is invoked by the PO Approval workflow as part of notification construction during standard purchase order approval in Release 12.1.1 and 12.2.2. Customers customizing approval notification text typically do so through Oracle Workflow Builder message attributes and the standard notification mailer configuration rather than by modifying this package. Where the packaged message body does not meet requirements, the recommended extension point is Workflow message customization or a notification mailer/attribute extension, not direct patching of the package body, since it is a shipped APPS object.