Search Results zip_code

Overview

The view APPS.JTF_RS_SUPPLIERS_VL is a CRM Foundation (JTF) object that consolidates supplier contact information for parties that are either candidates for import as resources or are already registered as resources. In Oracle E-Business Suite 12.1.1 and 12.2.2, it presents a flattened, denormalized read model across Oracle Payables supplier data and Oracle HR operating units, exposing supplier, supplier site, address, and contact attributes in a single queryable structure. Its status is VALID in the APPS schema.

The view carries no procedural logic of its own; it is a pure relational projection. Because it joins purchasing and HR entities, it is typically consumed for reporting, data extraction, and integration scenarios involving the Resource Manager and CRM modules, rather than for transactional processing. The presence of the _VL suffix reflects the CRM Foundation naming convention applied to supplier-oriented views in the resource schema.

Underlying Base Objects

The documented referenced base objects are FND_GLOBAL (package), HR_OPERATING_UNITS (view), PO_VENDORS (view), PO_VENDOR_CONTACTS (view), and PO_VENDOR_SITES_ALL (view). The join structure is as follows:

PO_VENDOR_SITES_ALL.VENDOR_ID = PO_VENDORS.VENDOR_ID — links each site to its parent supplier.
PO_VENDOR_SITES_ALL.VENDOR_SITE_ID = PO_VENDOR_CONTACTS.VENDOR_SITE_ID — links contacts to the site they belong to.
HR_OPERATING_UNITS.ORGANIZATION_ID = PO_VENDOR_SITES_ALL.ORG_ID — resolves the operating unit name for the site.

All three purchasing objects are themselves views over the underlying PO base tables, so the effective data lineage runs through the Payables supplier model. FND_GLOBAL is listed as a referenced object and is commonly relied upon in this family of views to supply session context such as the current operating unit; note that it does not appear as an explicit join in the documented view text.

Key Columns

The view exposes supplier, site, address, and contact attributes. Notable columns include:

SUPPLIER_ID / SUPPLIER_NUMBER / SUPPLIER_NAME — sourced from PO_VENDORS.VENDOR_ID, SEGMENT1, and VENDOR_NAME.
SUPPLIER_SITE_ID / SUPPLIER_SITE_CODE / ORG_ID — the site identifier, site code, and operating unit identifier from PO_VENDOR_SITES_ALL.
ADDRESS_LINE1/2/3, CITY, ZIP_CODE, STATE, PROVINCE, COUNTY, COUNTRY — address attributes of the supplier site. The user-searched column ZIP_CODE is mapped directly from PO_VENDOR_SITES_ALL.ZIP.
SUPPLIER_CONTACT_ID, FIRST_NAME, LAST_NAME, AREA_CODE, PHONE — contact details from PO_VENDOR_CONTACTS.
EMAIL, FAX — documented as NULL literals; these are placeholders not populated by the view definition.
ORG_NAME — the operating unit name from HR_OPERATING_UNITS.NAME.

Common Use Cases and Queries

Typical scenarios include surfacing supplier contacts for resource import, resolving a supplier site's address by ZIP code, and reporting contacts by operating unit. A representative query filtering on ZIP code is:

SELECT supplier_name, supplier_site_code, city, zip_code, first_name, last_name
FROM apps.jtf_rs_suppliers_vl
WHERE zip_code = :p_zip_code
ORDER BY supplier_name, last_name;

Because EMAIL and FAX are NULL in the view definition, reports requiring those attributes must source them elsewhere. Query performance depends on the indexed join keys within the underlying PO views; filtering by ZIP_CODE is generally unindexed and should be applied after join resolution or combined with supplier or site predicates.

View: JTF_RS_SUPPLIERS_VL 12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:JTF.JTF_RS_SUPPLIERS_VL, object_name:JTF_RS_SUPPLIERS_VL, status:VALID, product: JTF - CRM Foundation , description: The details of supplier contacts that can be imported as resource or are already present as resource , implementation_dba_data: APPS.JTF_RS_SUPPLIERS_VL ,
View: JTF_RS_SUPPLIERS_VL 12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:JTF.JTF_RS_SUPPLIERS_VL, object_name:JTF_RS_SUPPLIERS_VL, status:VALID, product: JTF - CRM Foundation , description: The details of supplier contacts that can be imported as resource or are already present as resource , implementation_dba_data: APPS.JTF_RS_SUPPLIERS_VL ,
View: JTF_RS_PARTNERS_VL 12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:JTF.JTF_RS_PARTNERS_VL, object_name:JTF_RS_PARTNERS_VL, status:VALID, product: JTF - CRM Foundation , description: The details of parners that can be imported as resource or are already present as resource , implementation_dba_data: APPS.JTF_RS_PARTNERS_VL ,
View: JTF_RS_PARTNERS_VL 12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:JTF.JTF_RS_PARTNERS_VL, object_name:JTF_RS_PARTNERS_VL, status:VALID, product: JTF - CRM Foundation , description: The details of parners that can be imported as resource or are already present as resource , implementation_dba_data: APPS.JTF_RS_PARTNERS_VL ,