Search Results get_terms_dsp

Overview

The APPS.PO_VENDORS_SV package body is a server-side PL/SQL component within the Oracle E-Business Suite Purchasing (PO) module. It serves as a supplier (vendor) validation and derivation utility layer, providing reusable logic that the Purchasing forms, concurrent programs, and other dependent packages invoke when manipulating supplier records. The _SV suffix denotes a "server validation" package, a naming convention used across Oracle EBS for packages whose primary role is to enforce business rules, resolve derived values, and validate user input against database state before a record is committed. In Oracle EBS 12.1.1 and 12.2.2, this package remains classified as OTHER and status VALID, indicating it is a supported internal component rather than a formally published public API.

The package depends on a broad set of Purchasing, Payables, and Receiving objects, reflecting its role at the intersection of supplier, terms, freight, and shipment information. It is referenced by 19 other database objects, confirming that it functions as a shared foundational utility used throughout the procurement stack rather than an entry point invoked directly by end users.

Key Procedures and Functions

ETRM documents 18 procedures and functions for this package body. Among the named entries:

• NAME — a core routine associated with supplier name handling and validation within the package.
• GET_TERMS_CONDITIONS — retrieves the payment terms and conditions applicable to a supplier, driving the terms data used on purchasing documents.
• GET_TERMS_DSP — returns the display-formatted terms value, supporting user-interface presentation of terms information in the Purchasing forms.
• VAL_SHIPPING_CONTROL — validates the shipping control attribute associated with a supplier or supplier site, enforcing valid values against the relevant lookup or master data.
• TEST_GET_VENDOR — a diagnostic or test helper for exercising the vendor retrieval logic during development and troubleshooting.

The remaining documented procedures follow the same GET_* and VAL_* patterns, covering derivation of supplier attributes and validation of user-entered values. No parameter lists are published in the metadata; callers should reference the live package specification for exact signatures.

Tables Accessed

The package reads and uses several base tables and their APPS synonyms:

• AP_TERMS — the Payables terms table, consulted by the GET_TERMS_* routines to resolve payment terms and their descriptions.
• PO_HEADERS_ALL — the purchasing document headers table, used to support supplier-related validation in the context of existing purchase orders.
• ORG_FREIGHT — the freight carrier and freight terms setup, supporting shipping and freight validation logic such as VAL_SHIPPING_CONTROL.
• DBMS_SQL — the Oracle-supplied dynamic SQL package, indicating the package builds and executes SQL dynamically for flexible or metadata-driven lookups.

Additional dependencies documented include PO_VENDORS, PO_VENDORS_SV, PO_VENDOR_CONTACTS_SV, PO_VENDOR_SITES_SV, PO_TERMS_SV, PO_ORGS_SV, PO_LOCATIONS_S, PO_LOOKUP_CODES, PO_MESSAGE_S, PO_CORE_S, RCV_SHIPMENT_HEADER_SV, and RCV_SHIPMENT_OBJECT_SV, along with FND_LOG, FND_PROFILE, and ASN_DEBUG for logging, profile options, and debugging.

Usage Notes

PO_VENDORS_SV is not referenced by any database object outside the APPS schema and is not intended for direct invocation by external integrations. It is called internally by 19 dependent PL/SQL packages that collectively drive the Suppliers and Purchasing forms in Oracle EBS 12.1.1 and 12.2.2. Typical invocation occurs when a user enters or validates supplier, site, terms, or shipping information on a purchasing document, at which point the form triggers the appropriate validation routine. Because the package relies on FND_PROFILE, behavior can vary with the operating unit and profile configuration. Customizations should not modify this package directly; developers extending supplier validation logic should instead build wrappers or subscribe to the documented public APIs, reserving TEST_GET_VENDOR for controlled diagnostic use only.