Search Results party_contacts




Overview
Explore in AI Chat

Overview

APPS.AST_PLIST_REL_UWQ_V is a database view in Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 that exposes relationship-based contact data drawn from parties, party sites, relationships, and contact points, joined to Oracle Advanced Marketing (AMS) list membership. The view is part of the Oracle TeleSales / Sales resource and list infrastructure, presenting a denormalized "party contact" recordset suitable for list-generation, telemarketing campaigns, and structured reporting on contactable parties.

Its name reflects its construction: AST (the Oracle TeleSales / Advanced Sales application prefix), PLIST (party list), REL (relationship), and UWQ (universal work queue). The view supplies a stable, pre-joined projection where an AMS list header and list entry are enriched with the party's customer name, contact names, phone, email, title, and postal address. Because it pre-resolves the multiple joins between HZ_PARTIES, HZ_RELATIONSHIPS, HZ_ORG_CONTACTS, HZ_CONTACT_POINTS, HZ_LOCATIONS, and HZ_PARTY_SITES, it is commonly consumed by Oracle TeleSales list-management screens, outbound calling work queues, and custom concurrent programs that need a flat contactable-party dataset.

In the context of user searches for "party_contacts," this view is relevant because it surfaces person-level contact attributes (first name, last name, full name, title) alongside the organization party they relate to, providing the semantic equivalent of a party-contacts query without requiring the caller to write the underlying HZ schema joins.

Underlying Base Objects

The view is documented as being defined over the following base objects (all visible in APPS as synonyms):

  • AMS_LIST_HEADERS_ALL — the list header (list name, source type, source, enabled flag, list type, owner user).
  • AMS_LIST_ENTRIES — the individual list entries (entry id, creation/update dates, duplicate and control-group flags).
  • HZ_PARTIES — referenced twice: once as the contact party (aliased PARTY_CONTACTS) and once as the customer/organization party (aliased PARTY), with a third alias REL_PARTY used for the related party's email.
  • HZ_RELATIONSHIPS — links the contact party to the customer party.
  • HZ_ORG_CONTACTS — organization-contact attributes such as job title.
  • HZ_CONTACT_POINTS — phone contact points.
  • HZ_LOCATIONS — address components (address1, address2, city, state, postal code, country).
  • HZ_PARTY_SITES — party-to-site association.

The joins link list header to list entry, list entry to party, and then pivot through HZ_RELATIONSHIPS to obtain the contact person and their organization, with the DMT (TCA) contact tables supplying names, phones, and addresses. Note the presence of a DISTINCT keyword in the select, confirming the view de-duplicates the many-to-many fan-out that can occur across contact points and sites.

Key Columns

  • ieu_object_function / ieu_object_parameters — literal tokens ('AST_RC_ALL', 'PARTY_ID=345 ') used by the universal work queue to identify the object and its parameter binding.
  • ieu_action_object_code / ieu_param_pk_col / ieu_param_pk_value — 'PARTY', 'PARTY_ID', and the party id value driving the work queue action.
  • resource_type / resource_id — 'RS_INDIVIDUAL' and the list owner user id, identifying the sales resource assigned to the list.
  • list_header_id, list_name, list_type, list_source, list_source_type, enabled_flag — AMS list metadata.
  • list_entry_id, party_id (ale.col248), marked_as_duplicate_flag, part_of_control_group_flag — entry-level identity and disposition flags.
  • PERSON_FIRST_NAME, PERSON_LAST_NAME, FULL_NAME (first + middle + last), TITLE, JOB_TITLE — person contact attributes.
  • CUSTOMER_NAME (PARTY.PARTY_NAME) — the organization party name.
  • CITY, STATE, ZIPCODE, COUNTRY, LOCATION (concatenated address) — postal address components.
  • PHONE (country code + area code + number + extension) — formatted contact phone.
  • EMAIL_ADDRESS — related party email.
  • customer_id (rel.object_id), creation_date, last_update_date — audit and relationship keys.

Common Use Cases and Queries

The view is typically queried to obtain a contactable list of parties with phone and address details, or to inspect membership of an AMS list alongside the party-contact attributes.

SELECT list_name,
       full_name,
       customer_name,
       title,
       phone,
       email_address,
       location
FROM   apps.ast_plist_rel_uwq_v
WHERE  enabled_flag = 'Y'
ORDER  BY list_name, full_name;

To locate a specific contact on a list:

SELECT list_entry_id,
       list_name,
       full_name,
       customer_name,
       phone,
       email_address
FROM   apps.ast_plist_rel_uwq_v
WHERE  party_id = :p_party_id
AND    marked_as_duplicate_flag = 'N';

For work-queue integration, the IEU columns are used to resume the party context:

SELECT ieu_object_function,
       ieu_object_parameters,
       ieu_action_object_code,
       ieu_param_pk_value,
       customer_name,
       full_name
FROM   apps.ast_plist_rel_uwq_v
WHERE  resource_id = :p_user_id
AND    enabled_flag = 'Y';

Typical scenarios include telemarketing list generation, deduplication review (via marked_as_duplicate_flag), and exporting list entries with contact names, phones, and addresses for outbound campaigns. Because the view relies on TCA (HZ) tables and AMS lists, query performance benefits from indexed lookups on list_header_id, party_id, and resource_id, and callers should filter on enabled_flag to restrict to active lists.