Search Results notify_supplier_rejected

Overview

POS_SPM_WF_PKG1 is an Oracle Application Object Library package owned by the APPS schema that supports the Oracle Supplier Lifecycle Management (SPM) module within Oracle E-Business Suite. Its primary business function is to generate and dispatch Oracle Workflow notifications associated with supplier registration, supplier profile maintenance, and buyer-driven approval activities. The package acts as a centralized notification layer: rather than embedding Workflow API calls directly within each supplier-facing package, the SPM application delegates notification logic to POS_SPM_WF_PKG1, which resolves recipients, constructs notification payloads, and initiates the appropriate Workflow processes.

The package is classified as OTHER in the documented API classification, indicating that it is an internal implementation component rather than a published integration API. It is not intended for direct customer invocation. The package name contains the "WF" token, confirming its role as the Workflow-facing utility for supplier profile management.

Key Procedures and Functions

ETRM documents 43 procedures and functions, of which the following are representative. The naming convention splits cleanly into "NOTIFY_" routines that raise Workflow notifications and note-related routines that record buyer input.

• NOTIFY_ADDR_CREATED / NOTIFY_ADDR_UPDATED / NOTIFY_ADDR_REMOVED — raise notifications when an address associated with a supplier or supplier site is added, changed, or deleted.
• NOTIFY_BUS_CLASS_CREATED / NOTIFY_BUS_CLASS_UPDATED / NOTIFY_BUS_CLASS_REMOVED — notify stakeholders of changes to supplier business classification assignments.
• NOTIFY_CONTACT_CREATED / NOTIFY_CONTACT_UPDATED / NOTIFY_CONTACT_REMOVED — handle notifications for supplier contact records.
• NOTIFY_CONTACT_LINK_CREATED / NOTIFY_CONTACT_LINK_REMOVED — notify when a contact is linked to or unlinked from a supplier site or address.
• NOTIFY_PRODUCT_CREATED / NOTIFY_PRODUCT_REMOVED — notify on changes to a supplier's registered products or categories.
• NOTIFY_SUPPLIER_REGISTERED / NOTIFY_SUPPLIER_APPROVED / NOTIFY_SUPPLIER_REJECTED — the core registration lifecycle notifications delivered to the prospective supplier and to internal buyers.
• NOTIFY_DUP_SUPPLIER_REG — alerts reviewers when a duplicate supplier registration is detected.
• NOTIFY_ACCOUNT_CREATE — notification tied to bank account creation for a supplier.
• BUYER_NOTE / BANK_ACCT_BUYER_NOTE — record free-text buyer commentary against a supplier or a bank account, typically surfaced in the approval workflow.

Tables Accessed

The package reads and writes a mix of Oracle Supplier Management, Trading Community Architecture (TCA), and Oracle Application Framework foundation tables.

• AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL — supplier header and site information used to resolve notification recipients and to populate message content.
• HZ_PARTIES, HZ_PARTY_SITES, HZ_PARTY_USG_ASSIGNMENTS, HZ_RELATIONSHIPS — TCA registry entities describing the party, its site addresses, usage assignments, and contact relationships.
• POS_ADDRESS_REQUESTS, POS_BUS_CLASS_REQS, POS_CONTACT_REQUESTS — SPM registration request records that trigger the address, business classification, and contact notifications.
• FND_USER, FND_RESPONSIBILITY, FND_MENU_ENTRIES, FND_FORM_FUNCTIONS, FND_LOOKUP_VALUES, FND_TERRITORIES — used to resolve Workflow role recipients, responsibility assignments, and standardized lookup and territory values.

Usage Notes

POS_SPM_WF_PKG1 is invoked indirectly rather than by end users. It is referenced by four other APPS packages — POS_REQUEST_UTILS_PKG, POS_SBD_PKG, POS_SUPPLIER_NOTIFY_PKG, and POS_VENDOR_REG_PKG — and by itself, forming the notification backbone for supplier registration and profile change flows. Typical invocation occurs when an Oracle Application Framework (OAF) supplier registration or profile management page commits a change; the calling package then invokes the appropriate NOTIFY_ routine to place a notification in the recipient's Workflow worklist or to deliver an outbound message.

Because the object is classified OTHER and is undocumented as a public API, customizations should not call these procedures directly. Any extension that requires supplier notifications should be implemented by wrapping or subscribing to the surrounding Workflow process rather than by invoking POS_SPM_WF_PKG1 members. The package relies only on SYS.STANDARD for compilation dependencies and presents no external database links, keeping it portable across both 12.1.1 and 12.2.2 releases where the SPM module is licensed.