Results for “po_vendors_s”

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

Overview

APPS.AP_VENDORS_PKG is a server-side PL/SQL package body in the Oracle E-Business Suite APPS schema that encapsulates the core maintenance logic for supplier (vendor) records. In EBS terminology, a "vendor" in the Payables and Purchasing schemas is exposed to end users as a "supplier," and this package provides the centralized row-level insert, update, and locking operations against the underlying vendor and vendor site tables. It acts as a procedural layer that shields callers from the denormalized structure of the supplier data model, validates uniqueness and business constraints, and coordinates the maintenance of related history and invoice data. Because it is a body with no dependent database objects reported against it, it functions as an internal implementation unit consumed primarily by the Oracle Forms-based supplier maintenance UI and by other EBS packages rather than as a public API (that role belongs to AP_VENDOR_PUB_PKG, which this package references).

Key Procedures and Functions

The ETRM metadata documents twelve procedures and functions. The principal maintenance routines are:

• INSERT_ROW — Inserts a new vendor/supplier row, applying defaults and denormalized attribute handling.
• UPDATE_ROW — Applies changes to an existing supplier record.
• LOCK_ROW — Acquires a row lock to serialize concurrent edits and guard against lost updates.
• CHECK_UNIQUE_VENDOR_NAME — Verifies that the proposed supplier name does not duplicate an existing one.
• CHECK_DENORMALIZED_VENDOR_NAME — Validates the denormalized vendor name fields kept in sync across related tables.
• CHECK_UNIQUE_VENDOR_NUMBER — Enforces uniqueness of the supplier number (the alternate key used when supplier numbering is manual or automatic).
• CHECK_SELECTED_INVOICES — Determines whether invoices reference the supplier/site, producing a validation failure when changes are disallowed.
• CHECK_DUPLICATE_EMPLOYEE — Detects whether the supplier is associated with an existing employee record (relevant to employee-as-supplier and expense reimbursement scenarios).
• RESOLVE_EMPLOYEE — Resolves the employee linkage for a supplier.
• GET_MESSAGE_TEXT — Retrieves a formatted message string via the FND message dictionary.
• Two further documented procedures complete the set of twelve.

Validation failures are raised through APP_EXCEPTION and FND_MSG_PUB, consistent with the standard EBS error-stack pattern. No parameter signatures are asserted here, as the metadata does not expose them.

Tables Accessed

The package reads and writes the following documented tables, mostly through APPS synonyms:

• PO_VENDORS_S and PO_VENDORS — the supplier header and its translated/denormalized counterpart; the primary targets of INSERT_ROW and UPDATE_ROW.
• PO_VENDOR_SITES / AP_SUPPLIER_SITES_ALL — supplier site records maintained alongside the header.
• AP_SUPPLIERS — the Payables-facing supplier view/entity used for validation.
• AP_SELECTED_INVOICES — referenced by CHECK_SELECTED_INVOICES to prevent edits to suppliers with posted invoice activity.
• PO_HISTORY_VENDORS — purchasing history retained for the supplier.
• AP_PRODUCT_SETUP — supplies Payables options and defaults.
• Supporting objects HR_EMPLOYEES, IGI_CIS2007_UTIL_PKG, and DUAL underpin the employee checks and construction-related logic.

Usage Notes

AP_VENDORS_PKG is invoked indirectly. The most common caller is the Oracle Forms supplier maintenance form (the "Suppliers" window), whose block-level triggers call INSERT_ROW, UPDATE_ROW, and LOCK_ROW in response to user actions, with the CHECK_* procedures firing during validation. The CHECK_SELECTED_INVOICES and employee routines support cross-module validations surfaced as form errors. Custom integrations should generally use the public AP_VENDOR_PUB_PKG or the TCA-based supplier APIs rather than calling AP_VENDORS_PKG directly, since its interface is not guaranteed across releases. When troubleshooting supplier save, duplicate-name, or duplicate-number errors in 12.1.1 or 12.2.2, this package and its error stack are the appropriate starting point.