Results for “address_line2”

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

Overview

PO_SUPPLIER_PO_SITES_VAL_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema and registered in the Purchasing (PO) product module. ETRM metadata for both 12.1.1 and 12.2.2 identifies the object as VALID and describes it tersely as "10SC ONLY - Retrofitted," indicating that the definition originated as a customer-specific (10SC) customization that was subsequently retrofitted into the standard application. The view provides a validated, filtered list of supplier purchasing sites, exposing the key descriptive attributes required for site selection during purchasing transactions — including both secondary address lines, which is the column a user searching for "address_line2" would expect to find surfaced here.

Functionally, the view acts as a reporting and integration convenience layer over the underlying supplier site data. Rather than requiring consumers to re-implement the business validation filters for "active purchasing site" status, the view embeds those filters in its WHERE clause, guaranteeing consistent results across reports, interfaces, and third-party integrations. Because it exposes site-level identifiers such as VENDOR_SITE_ID, VENDOR_ID, SHIP_TO_LOCATION_ID, and BILL_TO_LOCATION_ID alongside descriptive address fields, it is well suited for both display-driven reports and data-extract programs that need to reconcile against purchasing documents.

Underlying Base Objects

Per the documented view text, PO_SUPPLIER_PO_SITES_VAL_V is defined over PO_VENDOR_SITES, which is itself listed in ETRM as a referenced base object (VIEW). The view also references FND_GLOBAL (PACKAGE), consistent with the ORG_ID column in the select list — multi-org views typically derive the operating unit context from FND_GLOBAL.ORG_ID rather than exposing it purely as a stored attribute.

The defining WHERE clause enforces three validation predicates against PO_VENDOR_SITES:

• PURCHASING_SITE_FLAG = 'Y' — the site must be enabled as a purchasing site.
• NVL(RFQ_ONLY_SITE_FLAG, 'N') != 'Y' — RFQ-only sites are excluded.
• SYSDATE < NVL(INACTIVE_DATE, SYSDATE + 1) — inactive sites whose INACTIVE_DATE has passed are suppressed, while sites with a NULL INACTIVE_DATE are retained.

The net effect is that the view returns only sites currently usable for purchasing, and the "VAL" suffix in the object name reflects this validation semantics. Because the WHERE clause is embedded in the view, any query against it inherits these filters automatically.

Key Columns

The view projects eighteen columns. The identifier columns — VENDOR_SITE_CODE, VENDOR_SITE_ID, VENDOR_ID, SHIP_TO_LOCATION_ID, and BILL_TO_LOCATION_ID — provide the primary keys and foreign keys needed to join to supplier, location, and purchasing document tables. Descriptive address columns include ADDRESS_LINE1, ADDRESS_LINE2, ADDRESS_LINE3, CITY, STATE, ZIP, and COUNTRY, supporting full address rendering where suppliers use multiple address lines.

Purchasing default columns — SHIP_VIA_LOOKUP_CODE, FOB_LOOKUP_CODE, and FREIGHT_TERMS_LOOKUP_CODE — carry the site-level shipping, FOB, and freight defaults propagated onto purchase orders and RFQs. TELEPHONE and FAX are derived expressions concatenating area codes with numbers: '('||AREA_CODE||') '||PHONE and '('||FAX_AREA_CODE||') '||FAX. Finally, ORG_ID supplies the operating unit context via FND_GLOBAL.

Common Use Cases and Queries

The most frequent use is validating or sourcing supplier purchasing sites for a given operating unit, including full street addresses with the second address line.

• List active purchasing sites with complete addresses for a supplier.
• Populate a value list or custom form LOV for site selection.
• Feed downstream extracts with validated site identifiers and shipping defaults.

Sample query:

SELECT vendor_site_code, vendor_site_id, vendor_id,
       address_line1, address_line2, address_line3,
       city, state, zip, country,
       ship_via_lookup_code, fob_lookup_code,
       freight_terms_lookup_code, telephone, fax, org_id
FROM   apps.po_supplier_po_sites_val_v
WHERE  vendor_id = :p_vendor_id
AND    org_id = fnd_global.org_id
ORDER BY vendor_site_code;

Because the view withholds RFQ-only and inactive sites, consumers should join to PO_VENDOR_SITES directly when those site categories must be included.