Search Results get_vendor_site_id

Overview

PO_VENDOR_SITES_SV is an Oracle E-Business Suite PL/SQL package owned by the APPS schema. Its role is to centralize supplier site validation and derivation logic for the Purchasing module — most notably, determining which supplier site is valid, default, or applicable to a given document such as a purchase order, release, or RFQ. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than the definer, which is consistent with its role as a shared, reusable validation utility inside the Oracle EBS environment (12.1.1 / 12.2.2).

The package name suffix _SV reflects its function as a validation (Server-side Validation) layer that forms, APIs, and concurrent programs call to enforce purchasing rules around supplier sites. The header line in the source ($Header: POXVDVSS.pls 120.3) confirms it has been shipped and iterated through multiple releases, with change history entries dating back to 1995.

Key Procedures and Functions

According to the ETRM metadata, the package exposes 13 documented procedures and functions. The most relevant ones include:

• GET_VENDOR_SITE_ID — the function whose name typically triggers the user's search. It accepts a PO header identifier and returns the vendor site identifier associated with that purchase order header (as reflected by its return type tied to PO_HEADERS_ALL.vendor_site_id). This is the canonical call for retrieving the supplier site attached to a PO.
• VAL_VENDOR_SITE_ID — a validation function that checks whether a given supplier site is currently active. For purchasing documents, it additionally verifies that the site is not flagged as "RFQ Only," returning a BOOLEAN indicating whether the site is valid for the supplied document type.
• GET_DEF_VENDOR_SITE — a procedure that, when a supplier has only one site, returns that site as the default site (both identifier and code) for the specified document type.
• GET_VENDOR_SITE_INFO — a procedure that returns supplier site information for a given context.
• GET_ORG_ID_FROM_VENDOR_SITE — derives the operating unit (org) associated with a supplier site; used in multi-org aware validations.
• GET_TRANSMISSION_DEFAULTS_EDI — returns EDI transmission defaults configured against a supplier site.
• GET_VENDOR_ID — resolves the supplier identifier associated with the site context.

Parameter lists are not enumerated here to avoid invention; the documented signatures pass PO header identifiers in and vendor site identifiers out, with document-type and org-id qualifiers on the validation routines.

Tables Accessed

The package reads (and in some cases writes) against the following documented objects, generally via APPS synonyms:

• PO_HEADERS_ALL — the primary source for retrieving the vendor site attached to a PO header; also supplies the default type for GET_VENDOR_SITE_ID's return.
• PO_HEADERS — the base purchasing header table used for document-level lookups.
• PO_RELEASES_ALL and PO_RELEASES — used when validating or resolving supplier sites against releases (not just blanket POs).
• ECE_TP_DETAILS — the EDI trading-partner detail table, consulted for GET_TRANSMISSION_DEFAULTS_EDI.
• DBMS_SQL — dynamic SQL is used, indicating the package builds some queries at runtime (for example, org-specific or document-type-specific filters).

Usage Notes

PO_VENDOR_SITES_SV is invoked primarily from Oracle Purchasing forms (such as the Purchase Order and AutoCreate windows) when validating or defaulting a supplier site on a document. It is also referenced by 23 other packages in the EBS codebase, which makes it a low-level dependency for supplier-site resolution. Custom extensions that need to determine which vendor site belongs to a PO, validate that a site is active and not RFQ-only, or default a site for single-site suppliers should call these APIs rather than querying the base tables directly, so that org-isolation and document-type rules are preserved. In multi-org environments, callers should supply the org_id context where the signature supports it, and honor the AUTHID CURRENT_USER behavior by ensuring the invoking session carries appropriate grants on PO_HEADERS_ALL, PO_RELEASES_ALL, and ECE_TP_DETAILS.