Results for “fax_area_code”

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

Overview

POBV_SUPPLIER_CONTACTS is a read-only reporting view owned by the APPS schema within the Oracle E-Business Suite Purchasing (PO) module. It is documented in ETRM for both release 12.1.1 and 12.2.2 and carries a status of VALID. The view presents supplier contact information — names, telephone numbers, fax numbers, email addresses, and related attributes — in a denormalized, business-facing form suitable for inquiry, reporting, and integration. The "BV" naming convention is consistent with Oracle's business views, which typically rename legacy columns to conform to newer naming standards and impose a WITH READ ONLY constraint to prevent DML against derived data.

Because the view is defined with WITH READ ONLY, it cannot be used as a target for INSERT, UPDATE, or DELETE statements. Its primary role is to support concurrent programs, Oracle Reports, BI Publisher data models, and downstream interfaces that need supplier contact details without navigating the underlying base object directly.

Underlying Base Objects

According to the ETRM metadata, POBV_SUPPLIER_CONTACTS is a retrofit view defined over a single referenced base object: PO_VENDOR_CONTACTS (itself exposed as a view). The view text selects a defined column list from that source and applies the WITH READ ONLY clause. Each row in POBV_SUPPLIER_CONTACTS corresponds to one row in PO_VENDOR_CONTACTS, so cardinality is preserved one-to-one. The view performs no joins, aggregation, or filtering; it is a projection and column-renaming layer.

Key Columns

• SUPPLIER_CONTACT_ID — Surrogate primary key of the contact record, mapped from VENDOR_CONTACT_ID. Used to uniquely identify a supplier contact.
• SUPPLIER_SITE_ID — Foreign key to the supplier site with which the contact is associated, mapped from VENDOR_SITE_ID.
• LAST_NAME, FIRST_NAME, MIDDLE_NAME, PREFIX, TITLE — Name and salutation attributes of the contact.
• AREA_CODE, PHONE — Primary telephone number, stored as separate area code and number components.
• ALT_AREA_CODE, ALT_PHONE — Alternate telephone number, the target of the "alt_phone" search. These columns expose the secondary contact number held on the supplier contact record.
• FAX_AREA_CODE, FAX — Facsimile number components.
• CONTACT_NAME_ALT, FIRST_NAME_ALT, LAST_NAME_ALT — Alternate-language forms of the contact name fields.
• EMAIL_ADDRESS, URL — Electronic contact points for the supplier representative.
• DEPARTMENT, MAIL_STOP — Internal routing attributes.
• INACTIVE_DATE — Date the contact became inactive; a null value indicates an active contact.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard Oracle Who columns. Note the view renames these to CREATED_DATE and LAST_UPDATED_DATE in its exposed column list.

Common Use Cases and Queries

Typical use cases include supplier contact listings, telephone and fax directories, data quality validation of phone and alternate phone fields, and extracts feeding external CRM or procurement systems. Because the view is read-only and lightweight, it is safe for high-volume read access.

To locate contacts by alternate phone number:

SELECT supplier_contact_id, first_name, last_name, alt_area_code, alt_phone
FROM apps.pobv_supplier_contacts
WHERE alt_phone LIKE '&alt_phone%';

To list active contacts for a supplier site:

SELECT sc.supplier_contact_id, sc.first_name, sc.last_name, sc.phone, sc.email_address
FROM apps.pobv_supplier_contacts sc
WHERE sc.supplier_site_id = :site_id
AND sc.inactive_date IS NULL;

Because the view maps directly to PO_VENDOR_CONTACTS, any query pattern valid against the base object applies here with the renamed column conventions (for example, VENDOR_CONTACT_ID becomes SUPPLIER_CONTACT_ID and VENDOR_SITE_ID becomes SUPPLIER_SITE_ID).