Search Results get_external_userlist

Overview

APPS.PO_VENDORS_GRP is a public wrapper package in the Oracle E-Business Suite Procurement module, classified under ETRM as a GRP (group) API. Its documented purpose is to expose selected supplier-facing service routines so that external application teams—code that does not own the Purchasing schema and therefore cannot call private APIs directly—can invoke supported supplier logic through a stable, published interface. The package body carries the header identifier $Header: POXGVENB.pls 120.2, dating the implementation lineage to 2005, and remains present in both the 12.1.1 and 12.2.2 code lines.

The single documented procedure, get_external_userlist, addresses a specific integration requirement: determining which supplier users should receive business document notifications. Rather than embedding supplier-user resolution logic inside each calling application, the GRP package centralizes it and allows external consumers to obtain a consistent answer from Oracle's own supplier data model. Only get_external_userlist is documented (one procedure), although the ETRM record notes two total documented program units, and the package is referenced by four other packages within the EBS codebase.

Key Procedures and Functions

• GET_EXTERNAL_USERLIST — The documented entry point of the package. Its stated function is to act as a wrapper over the procedure get_supplier_userlist in PO_VENDORS_PVT, making that internal supplier-user retrieval logic callable by external applications. Per the in-source comments, it exists so that external application teams can determine the supplier users to send notifications to. The procedure is called with a PO header identifier and a business document type (for example PA_BLANKET or PO_STANDARD, which is parsed to derive the underlying PO document type), plus an optional supplier contact identifier on the deliverable. It accepts standard API framework parameters—API version and an initialization flag for the message list—and returns the standard FND_API return status values (G_RET_STS_SUCCESS, G_RET_STS_ERROR, G_RET_STS_UNEXP_ERROR) together with a message count and message data.

The principal output is a PL/SQL table of supplier user names. The source comments record an important forward-compatibility caveat: the underlying get_supplier_userlist currently returns supplier user names both as VARCHAR2 and as a PL/SQL table, but its signature may in future be changed to return only the PL/SQL table. Any recoding of the wrapper to accommodate that change will not alter the signature of the GRP API itself, preserving stability for external callers.

Tables Accessed

• PO_HEADERS — Read to resolve the purchasing document identified by the incoming PO header ID, and to derive the PO document type used when determining the applicable supplier users.
• FND_USER — Read to obtain the application user records corresponding to the supplier contacts who are to be notified, supplying the user names returned to the caller.

Access is described in the source as read-only in intent: the procedure documentation states that it modifies nothing and locks nothing. Tables are reached through APPS synonyms, consistent with standard EBS schema conventions.

Usage Notes

The procedure is designed for invocation by external applications and integration code rather than from the Purchasing forms themselves. Typical callers are notification and workflow-related components that must resolve the supplier user population for a given purchasing document before dispatching messages. Because the routine is a GRP-class API, it follows the standard EBS API conventions: callers should pass a valid API version, honour the initialize-message-list flag, and inspect x_return_status before consuming x_external_user_tbl. Error conditions are reported through the message count and message data outputs rather than through unhandled exceptions. As a wrapper, the procedure adds no business logic of its own; behaviour is entirely determined by PO_VENDORS_PVT.get_supplier_userlist, so consumers should expect the GRP signature to remain stable even if the private procedure changes.