Search Results po_lookup_codes




Overview
Explore in AI Chat

Overview

AP_VENDORS_V is a Payables (AP) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the supplier master record set held in the Payables module, combining core supplier attributes with descriptive decoded values drawn from Oracle Purchasing lookups and reference tables. The view is a principal read interface for supplier data used by Oracle Forms-based Payables and Purchasing windows, by concurrent programs, and by reports and integrations that need a denormalized supplier row rather than a join across many base tables.

The view is closely related to PO_VENDORS, which is itself a view in the Purchasing schema that projects much of the same supplier information. Because AP_VENDORS_V is built partly on PO_VENDORS, the two are frequently treated as interchangeable access paths, though AP_VENDORS_V additionally resolves lookup meanings such as vendor type, payment date basis, pay group, withholding status, organization type, minority group, and ship-to enforcement through PO_LOOKUP_CODES.

Underlying Base Objects

The documented ETRM 12.2.2 metadata lists the following referenced objects: AP_AWT_GROUPS (synonym), AP_INCOME_TAX_TYPES (synonym), AP_TERMS (synonym), FND_GLOBAL (package), PO_AGENTS (synonym), PO_LOOKUP_CODES (view), PO_VENDORS (view), and RCV_ROUTING_HEADERS (view).

  • PO_VENDORS supplies the primary supplier columns, including VENDOR_ID, VENDOR_NAME, SEGMENT1, enabled and summary flags, tax reporting attributes, tolerances, and hold attributes.
  • PO_LOOKUP_CODES is joined multiple times to decode lookup codes into their DISPLAYED_FIELD values, for example _TYPE, _FOB, _FREIGHT, _SHIP, _TERMS, _WH, _ORG, and _MIN.
  • PO_AGENTS resolves the buyer/agent association for the supplier record.
  • AP_TERMS provides the payment terms name keyed by TERMS_ID.
  • AP_AWT_GROUPS and AP_INCOME_TAX_TYPES support withholding and 1099/income tax reporting attributes.
  • RCV_ROUTING_HEADERS supports receiving routing configuration linked to the supplier site.
  • FND_GLOBAL provides session context such as organization and user identifiers used in the WHERE clause.

Key Columns

The view exposes supplier identity and control columns such as VENDOR_ID, VENDOR_NAME, SEGMENT1 (supplier number), SUMMARY_FLAG, ENABLED_FLAG, ONE_TIME_FLAG, PARENT_VENDOR_ID, and the parent supplier name and number aliased from PO_VENDORS. Audit columns include CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. Financial and payment columns include TERMS_ID, AT.NAME, INVOICE_CURRENCY_CODE, INVOICE_AMOUNT_LIMIT, ALWAYS_TAKE_DISC_FLAG, PAYMENT_PRIORITY, PAY_GROUP_LOOKUP_CODE, and decoded payment date basis and pay group values. Tax and reporting columns include NUM_1099, TYPE_1099 with its AP_INCOME_TAX_TYPES description, WITHHOLDING_STATUS_LOOKUP_CODE, WITHHOLDING_START_DATE, and ETAX-related attributes. Purchasing controls include QTY_RCV_TOLERANCE, DAYS_EARLY_RECEIPT_ALLOWED, DAYS_LATE_RECEIPT_ALLOWED, ENFORCE_SHIP_TO_LOCATION_CODE, INSPECTION_REQUIRED_FLAG, and RECEIPT_REQUIRED_FLAG. Hold columns include HOLD_ALL_PAYMENTS_FLAG, HOLD_FUTURE_PAYMENTS_FLAG, HOLD_FLAG, HOLD_BY, HOLD_DATE, and PURCHASING_HOLD_REASON.

Common Use Cases and Queries

Typical uses include supplier validation in import programs, populating LOVs, and reporting active suppliers with decoded lookup values. The following query returns enabled suppliers with decoded vendor type and payment terms:

  • SELECT vendor_id, vendor_name, segment1, vendor_type_lookup_code, displayed_field AS vendor_type, name AS terms_name FROM ap_vendors_v WHERE enabled_flag = 'Y' AND nvl(summary_flag,'N') = 'N';
  • SELECT vendor_id, vendor_name, segment1, num_1099, type_1099 FROM ap_vendors_v WHERE type_1099 IS NOT NULL;
  • SELECT vendor_id, vendor_name, withholding_status_lookup_code, displayed_field AS withholding_status FROM ap_vendors_v WHERE withholding_status_lookup_code IS NOT NULL;

Because AP_VENDORS_V resolves lookups at query time, callers searching for PO_LOOKUP_CODES behavior generally do not need to join that view directly; the decode is already embedded in AP_VENDORS_V. Performance is best when queries restrict on VENDOR_ID, SEGMENT1, or ENABLED_FLAG, since the underlying joins to PO_VENDORS, PO_LOOKUP_CODES, and AP_TERMS are resolved on each execution.