Search Results po_vendor_contacts




Overview
Explore in AI Chat

Overview

The PO_VENDOR_CONTACTS view is a critical data object within the Oracle E-Business Suite (EBS) Payables module, specifically for versions 12.1.1 and 12.2.2. It serves as a comprehensive, denormalized reporting layer that consolidates contact information for supplier sites from the underlying Trading Community Architecture (TCA) model. Its primary role is to provide a unified and easily queryable interface for vendor contact data, which is essential for procurement and payment communication processes. By joining key TCA party and contact point tables, this view abstracts the complexity of the HZ (TCA) schema, enabling standard reporting, integration, and data extraction for vendor management workflows without requiring direct joins to multiple foundational tables.

Key Information Stored

The view amalgamates columns from several core TCA entities. Key data points include the unique VENDOR_CONTACT_ID and VENDOR_SITE_ID for identification, alongside standard WHO columns (CREATED_BY, LAST_UPDATED_BY). The core contact details are extracted from the HZ_PARTIES table, including the contact's FIRST_NAME, MIDDLE_NAME, LAST_NAME, PREFIX, and TITLE. Communication details such as AREA_CODE, PHONE, EMAIL_ADDRESS, and URL are sourced from contact points. The view also provides phonetic name fields (CONTACT_NAME_ALT, FIRST_NAME_ALT, LAST_NAME_ALT) for alternative search and includes subqueries to fetch alternate phone numbers (ALT_AREA_CODE, ALT_PHONE). Notably, data is truncated (e.g., SUBSTR(HP.PERSON_FIRST_NAME, 1, 15)) to conform to legacy application field lengths.

Common Use Cases and Queries

This view is predominantly used for operational reporting and data feeds. Common scenarios include generating contact lists for vendor communications, populating contact information on printed purchase orders or payment advices, and supporting integration with external systems. A typical query to retrieve active contacts for a specific vendor site would be:

  • SELECT vendor_site_id, first_name, last_name, area_code, phone, email_address FROM apps.po_vendor_contacts WHERE vendor_site_id = :site_id;

For reporting purposes, it is often joined with PO_VENDORS and PO_VENDOR_SITES_ALL to create comprehensive supplier master lists. Developers also use this view as a source for custom forms or workflows requiring vendor contact details, avoiding complex direct TCA table joins.

Related Objects

PO_VENDOR_CONTACTS is intrinsically linked to the TCA foundation and Purchasing/Payables vendor tables. Primary related objects include:

  • HZ_PARTIES (HP): The source for the contact person's core name and demographic information.
  • HZ_PARTY_SITES (HPS): Provides the MAIL_STOP information for the contact's address.
  • HZ_CONTACT_POINTS (HCP): The underlying table for phone, email, and URL data, referenced directly in the view's subqueries for alternate phone numbers.
  • PO_VENDOR_SITES_ALL (PVS): The vendor site identifier from this table is a key join condition in the view's construction.
  • PO_VENDORS (PV): While not directly joined in the provided view snippet, it is a fundamental parent table for vendor sites and is commonly used in conjunction with this view for full vendor hierarchies.
  • 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 , 

  • Table: AP_SUP_SITE_CONTACT_INT 12.2.2

    owner:AP,  object_type:TABLE,  fnd_design_data:SQLAP.AP_SUP_SITE_CONTACT_INT,  object_name:AP_SUP_SITE_CONTACT_INT,  status:VALID,  product: AP - Payables ,  description: AP_SUP_SITE_CONTACT_INT holds Supplier contact data. The columns in the table map to corresponding columns in PO_VENDOR_CONTACTS table. The Oracle Payables application uses this information to create a new Supplier Contact record when th ,  implementation_dba_data: AP.AP_SUP_SITE_CONTACT_INT , 

  • Table: AP_SUP_SITE_CONTACT_INT 12.1.1

    owner:AP,  object_type:TABLE,  fnd_design_data:SQLAP.AP_SUP_SITE_CONTACT_INT,  object_name:AP_SUP_SITE_CONTACT_INT,  status:VALID,  product: AP - Payables ,  description: AP_SUP_SITE_CONTACT_INT holds Supplier contact data. The columns in the table map to corresponding columns in PO_VENDOR_CONTACTS table. The Oracle Payables application uses this information to create a new Supplier Contact record when th ,  implementation_dba_data: AP.AP_SUP_SITE_CONTACT_INT , 

  • View: FINANCIALS_PURGES_V 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:SQLAP.FINANCIALS_PURGES_V,  object_name:FINANCIALS_PURGES_V,  status:VALID,  product: AP - Payables ,  description: (Release 10SC Only) ,  implementation_dba_data: APPS.FINANCIALS_PURGES_V , 

  • View: FINANCIALS_PURGES_V 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:SQLAP.FINANCIALS_PURGES_V,  object_name:FINANCIALS_PURGES_V,  status:VALID,  product: AP - Payables ,  description: (Release 10SC Only) ,  implementation_dba_data: APPS.FINANCIALS_PURGES_V ,