Results for “po_vendors_pvt”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PO_VENDORS_PVT is a private PL/SQL package within the Oracle E-Business Suite Purchasing (PO) module, classified as a PVT (private) API, meaning it is intended strictly for internal use by other Oracle EBS packages rather than for direct invocation by customer code. The package resides in the APPS schema and is defined with AUTHID CURRENT_USER, so name resolution for unqualified references follows the privileges of the invoking user. Its header carries the revision marker POXVVENS.pls 115.2, dated 31-Oct-2003, indicating that the package predates the 12.1.1 and 12.2.2 releases and is carried forward for backward compatibility within the 12.2.x online patching architecture. The name reflects its lineage to the PO_VENDORS entity (the historical suppliers table, later renamed to POZ_SUPPLIERS in the Oracle Procure-to-Pay integration model). The package also defines an internal subtype, supplier_user_tbl_type, aliased to po_vendors_grp.external_user_tbl_type, which supplies the structured collection used to return supplier-side user information. A profile-driven debug constant reads FND_PROFILE.VALUE('AFLOG_ENABLED') to gate logging, consistent with Oracle's standard diagnostic pattern. The user search term "vpn full form for vendor management" is a naming coincidence; here "PVT" denotes the API classification "private," not a vendor-management acronym.

Key Procedures and Functions

• GET_SUPPLIER_USERLIST — The sole documented procedure in this package. It is the workhorse that assembles the list of supplier users associated with a given document. Based on the documented outputs, the procedure accepts a document identifier and document type, optionally constrained by an external contact identifier, and returns a status flag alongside a supplier-user collection, a rendered supplier-user list string, a variant list suitable for direct SQL embedding, the count of users, and the resolved vendor identifier. The x_supplier_userlist output supports display or messaging scenarios, while x_supplier_userlist_for_sql supports downstream query construction. Parameter lists are not reproduced here, as they are not part of the provided summary metadata.

Tables Accessed

The package resolves the following tables through APPS synonyms, which indicates the supplier-user derivation path and the document context it supports:

• FND_USER — the Oracle Applications user repository, providing the user identities behind the supplier contacts.
• AK_WEB_USER_SEC_ATTR_VALUES — the attribute-value store used by the Oracle Applications Framework security model, indicating that supplier-user visibility may be filtered by external web-user security attributes.
• PO_HEADERS, PO_HEADERS_ALL, PO_RELEASES — Purchasing document headers and releases, supplying the document context (requisition, purchase order, release, or negotiation) from which supplier users are gathered.
• PO_REQUISITION_LINES_ALL, PO_REQUISITION_SUPPLIERS — Requisition lines and their assigned suppliers, supporting the supplier-identification logic when the supplied document is a requisition.

Usage Notes

As a private API, PO_VENDORS_PVT is not exposed as a callable interface for customer extensions; it is referenced internally by exactly one other package within the EBS codebase, and Oracle does not guarantee its signature across upgrades. It is generally reached indirectly through supplier-facing or collaboration flows that need to enumerate the users belonging to a supplier in the context of a purchasing document. Because of the ubiquitous 115.2 header revision, the object is functionally identical in 12.1.1 and 12.2.2, with the only notable difference being that 12.2.x delivers it in the new online-patching file system layout and may resolve it through the ADOP-managed editioning views. Custom development should not invoke GET_SUPPLIER_USERLIST directly; equivalent business outcomes should be pursued through supported public APIs in the supplier and purchasing modules.