Results for “fob_lookup_code”

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

Overview

APPS.PO_SUPPLIER_SITES_ALL_V is a Purchasing (PO) module view in Oracle E-Business Suite 12.1.1 and 12.2.2. Its ETRM description carries the notation "10SC ONLY - Retrofitted," indicating that the object originated as a custom retrofit for a specific 10SC environment and was subsequently promoted into the APPS schema as a supported view. The view presents supplier site address and shipping information in a single, conveniently joined result set, exposing vendor site identifiers alongside mailing address elements, telephone and fax numbers, and several purchasing control attributes. Because it consolidates these fields without requiring the caller to navigate the full PO_VENDOR_SITES entity, the view is frequently used as a lightweight reference source for supplier site lookups in reports, concurrent programs, and interface extracts.

Underlying Base Objects

The documented base objects for this view are PO_VENDOR_SITES (a view) and the FND_GLOBAL package. The view text selects directly from PO_VENDOR_SITES, deriving the exposed columns from that source. FND_GLOBAL is the standard EBS package supplying session context values such as ORG_ID and USER_ID; its presence in the dependency list reflects the multi-org and security-aware behavior inherited through the underlying supplier site definition rather than an explicit column in the outer SELECT. The view therefore adds no storage of its own: it is a pure projection over the vendor sites data, and any change to address, contact, or purchasing defaults in the base supplier site record is immediately visible through this view. Because PO_VENDOR_SITES is itself a view, the effective read path terminates in the underlying vendor site tables maintained by the Payables and Purchasing schemas.

Key Columns

• VENDOR_ID — Identifier of the supplier (vendor) to which the site belongs.
• VENDOR_SITE_ID — Unique identifier of the supplier site; the primary join key for downstream tables such as PO_HEADERS_ALL and PO_LINES_ALL.
• VENDOR_SITE_CODE — User-facing supplier site name.
• ADDRESS_LINE1 / ADDRESS_LINE2 / ADDRESS_LINE3, CITY, STATE, ZIP, COUNTRY — Mailing address components of the site.
• SHIP_TO_LOCATION_ID — Location used as the default ship-to for the site. In the view text this is mapped from VENDOR_ID, an important behavioral detail to verify before relying on it.
• BILL_TO_LOCATION_ID — Default bill-to location for the site.
• SHIP_VIA_LOOKUP_CODE — Default carrier/ship-via method.
• FOB_LOOKUP_CODE — Free-on-board terms code.
• FREIGHT_TERMS_LOOKUP_CODE — Freight terms code carried on the supplier site; this is the column most often targeted by users searching for freight terms at site level.
• TELEPHONE / FAX — Formatted contact numbers built by concatenating area code and number, e.g. '('||AREA_CODE||') '||PHONE.

Common Use Cases and Queries

Typical scenarios include validating the freight terms, FOB, or ship-via defaults assigned to a supplier site; producing address mailing labels or supplier directories; and supplying ship-to and bill-to defaults to purchasing interfaces. A representative query retrieves freight terms and contact detail for a given vendor:

• SELECT vendor_site_code, freight_terms_lookup_code, fob_lookup_code, ship_via_lookup_code FROM apps.po_supplier_sites_all_v WHERE vendor_id = :p_vendor_id;
• SELECT vendor_id, vendor_site_id, address_line1, city, state, zip, telephone FROM apps.po_supplier_sites_all_v WHERE vendor_site_id = :p_site_id;
• SELECT vs.vendor_site_code, vs.freight_terms_lookup_code FROM apps.po_supplier_sites_all_v vs, apps.po_headers_all ph WHERE ph.vendor_site_id = vs.vendor_site_id AND ph.segment1 = :p_po_number;

Because the view omits the standard _ALL multi-org structure and exposes location identifiers that may be derived rather than directly sourced, developers should confirm each column against PO_VENDOR_SITES before using it in production logic, and should not treat the view as a substitute for org-secured access to supplier sites. FREIGHT_TERMS_LOOKUP_CODE, the searched term, is stored as a lookup code resolvable through the FREIGHT_TERMS lookup type in the Oracle Purchasing application.