Results for “pobv_suppliers”

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

Overview

POBV_SUPPLIERS is a Purchasing (PO) module view owned by the APPS schema. ETRM metadata identifies its status as VALID and its description as "Retrofitted," indicating that the object was carried forward into the 12.1.1 and 12.2.2 code lines to preserve backward compatibility for Oracle Forms-based and HTML-based Purchasing inquiry pages. The view presents supplier (vendor) master information in a flat, denormalized format suitable for value-list queries, LOV lookups, and Purchasing application screens that must display or validate supplier data without joining multiple vendor tables directly.

The view is documented as being defined over a single base object, PO_VENDORS, which is itself a view. Consequently, POBV_SUPPLIERS acts as a presentation layer over the vendor data exposed by PO_VENDORS, which in turn resolves to the underlying supplier tables in the Oracle Payables and Purchasing schemas. Its primary role in Oracle EBS reporting and integration is to supply supplier identity, tax, payment, and classification attributes to Purchasing forms and concurrent programs that reference the BV (business view) naming convention.

Underlying Base Objects

The documented referenced base object for POBV_SUPPLIERS is PO_VENDORS (VIEW). All columns projected by POBV_SUPPLIERS are aliased from this single source using the prefix VE, which reflects the vendor entity underlying PO_VENDORS. Because PO_VENDORS is a view, the true physical tables (principally AP_SUPPLIERS and its associated AP_SUPPLIER_SITES_ALL and related lookup structures) sit further down the dependency chain. Practitioners tracing a data lineage issue should therefore expect a multi-level chain: APPS.POBV_SUPPLIERS to APPS.PO_VENDORS to the supplier base tables.

Key Columns

• VE.VENDOR_ID, VE.VENDOR_NAME, VE.VENDOR_NAME_ALT, VE.SEGMENT1 — supplier identifier, primary name, alternate name, and the supplier number used for external reference.
• VE.START_DATE_ACTIVE, VE.END_DATE_ACTIVE — effective dating for the supplier record.
• VE.VAT_REGISTRATION_NUM, VE.TAX_REPORTING_NAME, VE.TAX_VERIFICATION_DATE, VE.VALIDATION_NUMBER, VE.TYPE_1099, VE.NUM_1099 — tax and regulatory reporting attributes.
• VE.INVOICE_AMOUNT_LIMIT, VE.PAYMENT_PRIORITY, VE.HOLD_REASON — invoicing and payment control fields.
• VE.AUTO_TAX_CALC_FLAG, VE.AP_TAX_ROUNDING_RULE — tax calculation behavior.
• Numerous columns are exposed through lookup decorations using the "_LA:..." convention, for example VENDOR_TYPE_LOOKUP_CODE, MINORITY_GROUP_LOOKUP_CODE, PAY_GROUP_LOOKUP_CODE, PAYMENT_METHOD_LOOKUP_CODE, TERMS_DATE_BASIS, and various YES/NO flags such as ONE_TIME_FLAG, SMALL_BUSINESS_FLAG, WOMEN_OWNED_FLAG, and HOLD_ALL_PAYMENTS_FLAG. These decorations instruct the Forms runtime to render the coded value through PO_LOOKUP_CODES or AP_LOOKUP_CODES.

Common Use Cases and Queries

The view is typically queried by supplier LOVs, Purchasing inquiry forms, and ad hoc reporting that needs a compact supplier profile. A basic query retrieves active suppliers by name or number:

• SELECT vendor_id, vendor_name, segment1 FROM apps.pobv_suppliers WHERE vendor_name LIKE :p_name;
• SELECT vendor_id, vendor_name, vat_registration_num FROM apps.pobv_suppliers WHERE segment1 = :p_supplier_num;

Regarding the searched term "qty_received_tolerance," no such column exists in POBV_SUPPLIERS. Quantity received tolerance is a receiving control attribute found on purchasing option and receiving parameter setups (for example, the RCV parameters and PO system parameters), not on the supplier master view. Users searching for qty_received_tolerance should look to receiving setup tables and their corresponding views rather than to POBV_SUPPLIERS. Within POBV_SUPPLIERS, the tolerance-adjacent concepts available are invoice amount limit and payment hold flags, which govern financial rather than quantity tolerances.