Search Results primary_phone_number
Overview
APPS.PO_VENDOR_CONTACTS is a VALID database view owned by the APPS schema and catalogued under the Payables (AP) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents supplier contact information in a denormalized, report-friendly form by joining supplier contact records to the corresponding supplier site, the underlying trading partner party, and the associated person or organization record. In EBS releases, supplier master data is split between the legacy AP_SUPPLIERS/AP_SUPPLIER_CONTACTS tables and the Oracle Trading Community Architecture (TCA) model (HZ_PARTIES, HZ_CONTACT_POINTS, HZ_RELATIONSHIPS). This view reconciles those models, exposing contact names, titles, phone numbers, e-mail addresses, and URLs from a single query surface.
The view's role is primarily reporting and integration: it is consumed by Oracle Purchasing and Payables inquiry screens, supplier-facing reports, and downstream extracts rather than being an end-user maintenance object. Because it flattens TCA relationship traversal, it spares report developers from manually resolving the REL_PARTY_ID linkage between a supplier contact and the party record that holds contact points.
Underlying Base Objects
The documented base objects referenced by the view are: AP_SUPPLIERS, AP_SUPPLIER_CONTACTS, AP_SUPPLIER_SITES_ALL, HZ_CONTACT_POINTS, HZ_ORG_CONTACTS, HZ_PARTIES, HZ_PARTY_SITES, and HZ_RELATIONSHIPS (all synonyms under APPS).
AP_SUPPLIER_CONTACTS(aliased PVC in the view text) is the driving table, supplyingVENDOR_CONTACT_ID,REL_PARTY_ID, audit columns, and the concurrent program request/program identifiers.AP_SUPPLIER_SITES_ALL(PVS) supplies theVENDOR_SITE_IDthat anchors a contact to a specific purchasing site.HZ_PARTIES(HP, HP2) supplies the first, middle, and last names, phonetic name variants, prefix/salutation, title, and the e-mail address and URL fallback values.HZ_CONTACT_POINTSis correlated by subquery againstOWNER_TABLE_NAME = 'HZ_PARTIES'to retrieve e-mail, phone, and alternate phone/area code values.HZ_ORG_CONTACTS(HOC) supplies the department attribute, whileHZ_PARTY_SITESandHZ_RELATIONSHIPSsupport the address and relationship resolution that binds contacts to parties.
Key Columns
VENDOR_CONTACT_ID— primary identifier of the contact record.VENDOR_SITE_ID— the supplier site to which the contact belongs.FIRST_NAME,MIDDLE_NAME,LAST_NAME— name components truncated viaSUBSTR(...,1,15), reflecting legacy column-width constraints.PREFIX—NVL(PERSON_PRE_NAME_ADJUNCT, SALUTATION).TITLE,MAIL_STOP,DEPARTMENT— organizational attributes.AREA_CODE/PHONEandALT_AREA_CODE— primary and alternate telephone data derived fromHZ_PARTIESandHZ_CONTACT_POINTS.EMAIL_ADDRESS,URL— electronic contact points, withNVLfallback logic.CONTACT_NAME_ALT,FIRST_NAME_ALT,LAST_NAME_ALT— phonetic/organization name variants.- Audit columns (
CREATION_DATE,CREATED_BY,LAST_UPDATE_DATE,LAST_UPDATED_BY,LAST_UPDATE_LOGIN) and concurrent columns (REQUEST_ID,PROGRAM_ID,PROGRAM_APPLICATION_ID,PROGRAM_UPDATE_DATE).
Common Use Cases and Queries
Typical scenarios include supplier contact listings for a purchasing site, e-mail extraction for notification workflows, and data validation ahead of a supplier data migration.
SELECT vendor_contact_id, vendor_site_id, first_name, last_name,
phone, email_address
FROM apps.po_vendor_contacts
WHERE vendor_site_id = :p_site_id
ORDER BY last_name, first_name;
An integration extract might select contacts by e-mail availability:
SELECT vendor_contact_id, last_name, email_address FROM apps.po_vendor_contacts WHERE email_address IS NOT NULL AND last_update_date >= :p_since;
Note the view's metadata and query strings must be handled carefully; concatenated input such as ')/**/AND/**/('bRqnsn'='bRQNsn'' reflects a suspected SQL-injection probe encountered in the source search, and such fragments should never be embedded directly into executed SQL. Always bind variables and validate input.
-
View: PO_VENDOR_CONTACTS
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.PO_VENDOR_CONTACTS, object_name:PO_VENDOR_CONTACTS, status:VALID, product: AP - Payables , implementation_dba_data: APPS.PO_VENDOR_CONTACTS ,
-
View: PO_VENDOR_CONTACTS
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.PO_VENDOR_CONTACTS, object_name:PO_VENDOR_CONTACTS, status:VALID, product: AP - Payables , implementation_dba_data: APPS.PO_VENDOR_CONTACTS ,