Search Results po_vendors_ap_pkg




Overview

PO_VENDORS_AP_PKG is a lightweight PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It serves as a supplier and supplier site inquiry utility, exposing helper functions that return counts of a supplier's active and inactive payment sites within a given operating unit (organization) context. The package bridges the Oracle Payables supplier model — the AP_SUPPLIERS and AP_SUPPLIER_SITES entities, backed by the Trading Community Architecture (TCA) party model via HZ_PARTY_SITES — and consuming forms or programs in the Purchasing and Payables flows that need to know how many usable payment sites a supplier currently has.

The package header carries the revision string $Header: povendrs.pls 120.2 ... noship $, indicating a small, stable, narrowly scoped utility rather than a broad public API. In ETRM 12.2.2 it is classified with an API classification of OTHER, meaning it is not an officially supported open interface or public API surface, but an internal helper invoked from within Oracle-owned code. Its naming (PO_VENDORS_AP_PKG) reflects its role at the intersection of the legacy PO_VENDORS supplier vocabulary and the AP (Payables) site model.

Key Procedures and Functions

The documented package exposes two public functions, both returning a NUMBER:

  • GET_NUM_ACTIVE_PAY_SITES — Returns the count of payment sites belonging to a specified supplier that are currently active, scoped to a specified operating unit / organization identifier. It accepts the supplier identifier and the organization identifier as inputs.
  • GET_NUM_INACTIVE_PAY_SITES — Returns the count of payment sites belonging to the same supplier that are inactive (end-dated or disabled) within the specified organization. It likewise accepts the supplier identifier and organization identifier as inputs.

Both functions are read-only inquiries; neither performs DML. Their mutual existence allows a caller to determine not only whether a supplier has any usable payment site, but also whether the supplier previously had sites that have since been inactivated — useful for validation messaging, deactivation warnings, and supplier maintenance screens.

Tables Accessed

The ETRM metadata records three tables referenced through APPS synonyms:

  • AP_SUPPLIERS — The supplier master, providing the supplier identity against which the site counts are correlated.
  • AP_SUPPLIER_SITES — The supplier site records holding the paying-site flag and the active/inactive (inactive_date / status) attributes that drive the two counts.
  • HZ_PARTY_SITES — The TCA party site layer that underpins supplier sites in Release 12, supplying the address/party-site context used to resolve and filter sites.

The functions are read-only against these tables; the package performs no writes.

Usage Notes

PO_VENDORS_AP_PKG is an internal utility, not a public API. It is referenced by one other package in the documented metadata, and it is typically invoked from Oracle-owned forms or PL/SQL logic that must display or validate supplier payment-site availability — for example, supplier query and maintenance screens where the user needs to see whether active pay sites exist before submitting a payment or purchase order. Because both functions require the supplier identifier and an organization identifier, callers must supply the correct operating unit context; results are organization-scoped and will not reflect sites outside that organization.

Custom code may call the package from APPS, but should treat it as unsupported for extension. The recommended approach for new integrations is to query AP_SUPPLIER_SITES directly with the appropriate org_id and pay_site_flag / inactive_date predicates, or to use the supported Payables supplier APIs, reserving PO_VENDORS_AP_PKG for compatibility with existing code paths.