Results for “program_application_id”

50+ results




Overview
Explore in AI Chat

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

Overview

APPS.ICX_PO_VENDOR_CONTACTS_V is a view in the Oracle E-Business Suite, owned by the APPS schema and associated with the ICX (Oracle iProcurement) product family. The view is documented with a status of VALID in the ETRM, but its description is explicitly marked as Obsolete. This designation indicates that the object is retained only for backward compatibility and is no longer the recommended interface for accessing vendor contact information in current 12.1.1 or 12.2.2 implementations.

The view presents vendor contact records — the individuals associated with a supplier site — in a flattened, denormalized form. Its principal role was to supply iProcurement and related purchasing flows with the name, title, and telephone details of supplier contacts so that requisition and purchase order processing could reference a named point of contact. Because the view simply projects columns from the underlying contact entity without joins, transformation, or filtering logic, it behaves as a lightweight pass-through interface suitable for reporting and integration reads rather than transactional writes.

Underlying Base Objects

The view is defined over a single referenced base object: PO_VENDOR_CONTACTS, which itself is documented as a view. The view text takes the form of a straight column projection with no WHERE clause, no aggregation, and no joins:

Because the view adds no logic, any row-count or column changes in PO_VENDOR_CONTACTS propagate directly. Consumers should therefore regard ICX_PO_VENDOR_CONTACTS_V as a stable naming alias rather than an independently governed data source, and should prefer the documented base object for new development.

Key Columns

  • VENDOR_CONTACT_ID — Primary identifier for the contact record; the join key to the base contact entity.
  • VENDOR_SITE_ID — Foreign key to the supplier site with which the contact is associated; the principal filter for site-specific lookups.
  • FIRST_NAME, MIDDLE_NAME, LAST_NAME, PREFIX — The name components of the contact. MIDDLE_NAME is a discrete column rather than part of a concatenated full name, which is significant for searches targeting that attribute.
  • TITLE, MAIL_STOP — Organizational role and internal delivery address for the contact.
  • AREA_CODE, PHONE — Telephone details, stored as separate components.
  • INACTIVE_DATE — Effective end date of the contact; a null value denotes an active contact.
  • LAST_UPDATE_DATE, CREATION_DATE, LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield storage for client-specific extensions.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program audit context.

Common Use Cases and Queries

Typical usage involves retrieving named contacts for a supplier site, particularly when searching on a name component such as the middle name, or when listing active contacts for procurement correspondence.

  • Retrieve active contacts for a site, exposing the middle name: SELECT vendor_contact_id, first_name, middle_name, last_name, title, phone FROM icx_po_vendor_contacts_v WHERE vendor_site_id = :site_id AND inactive_date IS NULL;
  • Search for contacts by middle name: SELECT vendor_contact_id, first_name, middle_name, last_name FROM icx_po_vendor_contacts_v WHERE UPPER(middle_name) = UPPER(:middle_name);
  • Extract contact details for integration with an external supplier portal, joining on vendor_contact_id and filtering on the audit columns.

Given the Obsolete designation, all such queries should be validated against the current supported interface before being embedded in new customizations or interfaces.