Search Results pos_vendor_pub_pkg




Overview
Explore in AI Chat

Overview

APPS.POS_VENDOR_PUB_PKG is a public PL/SQL package in the Oracle E-Business Suite database, classified under the ETRM metadata as an OTHER API. It belongs to the Procurement/Supplier (POS) module and provides a programmatic interface for creating, updating, and validating supplier master data within Oracle Purchasing and Payables. Its role is to encapsulate the business logic required to maintain the vendor (supplier) registry — including supplier headers, supplier sites, and supplier contacts — so that calling programs do not interact directly with the underlying base tables. By exposing a stable public API, it insulates dependent components such as the supplier registration flow, supplier address maintenance, and profile management from schema-level changes. The package is documented as VALID in the APPS schema and is referenced both internally (by other POS packages) and externally, making it a central integration point for supplier data operations in both Oracle EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents fifteen procedures and functions in this package. The principal public entry points are:

  • CREATE_VENDOR — Establishes a new supplier record, applying validation rules and defaulting logic before persisting the supplier.
  • UPDATE_VENDOR — Modifies an existing supplier record, enforcing the same business rules as creation.
  • VALIDATE_VENDOR — Performs validation of supplier data, typically invoked before a create or update to confirm data integrity.
  • CREATE_VENDOR_SITE — Creates a new supplier site, including the associated site-level attributes and address references.
  • UPDATE_VENDOR_SITE — Updates an existing supplier site record.
  • VALIDATE_VENDOR_SITE — Validates supplier site data prior to persistence.
  • CREATE_VENDOR_CONTACT — Creates a contact associated with a supplier, leveraging the Trading Community Architecture (HZ) contact model.
  • PROCESS_USER_ATTRS_DATA — Handles processing of user-defined descriptive flexfield attributes for the supplier entity.
  • GET_USER_ATTRS_DATA — Retrieves user-defined attribute data for a supplier, supporting read operations on descriptive flexfield values.

These procedures collectively support the full lifecycle of supplier creation and maintenance, from header-level details through sites and contacts.

Tables Accessed

The package reads and writes via APPS synonyms to several core EBS tables:

  • AP_SUPPLIERS — The base supplier header table, holding the primary supplier record.
  • AP_SUPPLIER_SITES and AP_SUPPLIER_SITES_ALL — Store supplier site definitions, with the "_ALL" view/table providing multi-organization visibility.
  • AP_SYSTEM_PARAMETERS_ALL and FINANCIALS_SYSTEM_PARAMS_ALL — Provide system-level defaults and configuration settings applied during supplier processing.
  • FND_LANGUAGES — Supplies language information for multilingual supplier data.
  • HZ_CONTACT_POINTS and HZ_PARTIES — Support the Trading Community Architecture party and contact point model used for supplier contacts and address validation.
  • PO_SYSTEM_PARAMETERS_ALL — Supplies Purchasing system parameters relevant to supplier setup.
  • PLITBLM — The EBS standard PL/SQL character-based LOB table, typically used for temporary storage of large attribute data.

These tables are accessed to persist and validate supplier, site, and contact data in alignment with Payables and Purchasing configuration.

Usage Notes

POS_VENDOR_PUB_PKG is typically invoked by Oracle EBS forms and business flows rather than by end users directly. It is referenced by six other packages, including POS_PROFILE_PKG, POS_SUPPLIER_ADDRESS_PKG, POS_VENDOR_REG_PKG, and OKL_LLA_UTIL_PVT, indicating that supplier registration, address maintenance, profile management, and leasing-related flows depend on it. It also references AP_VENDOR_PUB_PKG, reflecting its relationship to the Payables supplier API layer. The package may be called from concurrent programs, supplier self-service registration processes, and custom extensions that need to create or update suppliers programmatically. Because it is a documented public API, developers integrating supplier data should call these procedures instead of performing direct DML on the underlying AP and HZ tables, to ensure all validation, defaulting, and flexfield handling are applied consistently across releases 12.1.1 and 12.2.2.