Results for “get_external_userlist”
24 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PO_VENDORS_GRP is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the Oracle Purchasing (PO) module and is classified in the ETRM repository as a "GRP" (group) package, indicating that it aggregates a small number of related API entry points rather than implementing a full business entity. Its functional scope is narrow but operationally significant: it exposes supplier user information associated with a given purchasing document. In the procurement workflow, a document such as a purchase order, RFQ, or quotation can carry references to supplier-side contacts who are expected to act on that document through Oracle iSupplier Portal or a comparable collaboration channel. PO_VENDORS_GRP provides the programmatic means of retrieving those users. The package name and its persistent header comment ("POXGVENS.pls", header version 120.1, dated 2005) place it in a stable, long-lived portion of the Purchasing code line that has survived largely unchanged across the 12.1.x and 12.2.x family. A package-level constant, g_fnd_debug, is initialized from the FND profile option AFLOG_ENABLED, and a module prefix constant (po.plsql.PO_VENDORS_GRP.) is defined, indicating that the package participates in the standard Oracle Applications debugging and message-logging framework. This is consistent with the "GRP" convention, in which a thin grouping layer wraps business logic while remaining instrumented for diagnostics.
Key Procedures and Functions
The ETRM metadata documents two procedures, both named GET_EXTERNAL_USERLIST. The duplicate count reflects an overloaded procedure signature rather than two distinct operations, which is a common PL/SQL pattern in EBS public APIs.
- GET_EXTERNAL_USERLIST — retrieves the list of external (supplier-side) users associated with a given purchasing document. Inputs identify the document and its type, and optionally a specific external contact; outputs follow the standard EBS API convention of x_return_status, x_msg_count, and x_msg_data. Results are returned through a PL/SQL associative array of FND_USER.USER_NAME values, declared in the package specification as the type external_user_tbl_type.
- GET_EXTERNAL_USERLIST (overloaded) — the same operation with an extended output signature. In addition to the user table, it returns a supplier user list, a variant of that list formatted for use in SQL, a count of users, and the associated vendor identifier. The overload exists so that callers requiring the vendor context, a user count, or a SQL-ready string can obtain them in a single database round trip.
Tables Accessed
Two tables are documented as being referenced through APPS synonyms.
- FND_USER — the Oracle Applications user repository. It supplies the user_name values placed into the returned external_user_tbl_type collection, and is the source for resolving which application users correspond to the external contacts on the document.
- PO_HEADERS — the purchasing document header table. It anchors the p_document_id and p_document_type inputs, linking the calling context to the correct purchase order or related document so that the appropriate supplier contacts can be identified.
The metadata does not indicate any writes; the package functions as a read-only query facade over these two tables.
Usage Notes
PO_VENDORS_GRP is an internal rather than a formally published interface. The ETRM record shows it is referenced by four other packages, meaning its primary consumers are Oracle Purchasing and iSupplier Portal code paths that need to resolve which supplier users should receive or act upon a document. It is not normally invoked from a concurrent program or directly from an Oracle Forms event; instead it is called from other PL/SQL units during document rendering, notification, or access-control checks. Because the returned collection is an INDEX BY BINARY_INTEGER table of VARCHAR2, callers must declare a variable of the matching type from the package specification, or the call will fail to compile. Custom code should treat the package as Oracle-internal: parameters and behavior are not contractually guaranteed across patches, and the header comment carries the "noship" designation typical of files not shipped as a supported extension point. Where a supported interface is required, the standard Purchasing and Supplier APIs should be used instead. Debug output is controlled through the AFLOG_ENABLED profile option, so enabling FND logging at the appropriate level will produce module-prefixed trace messages when diagnosing supplier user resolution problems.
-
PACKAGE: APPS.PO_VENDORS_GRP 12.2.2
-
PACKAGE: APPS.PO_VENDORS_GRP 12.1.1