Search Results primary_contact_last_name




Overview

The APPS.AST_SALESLEAD_UWQ_V view is a TeleSales (AST) reporting and integration object delivered in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes sales lead data in a denormalized, presentation-ready form that is consumed by the Universal Work Queue (UWQ) and related interaction-channel frameworks. The view joins lead header information from AS_SALES_LEADS to party, contact, phone, status, rank, and lookup data so that a single query returns a complete lead record suitable for display in a telesales agent's work queue or for downstream processing by modules that subscribe to the IEU (Interaction Event Utility) interface.

The URGENT_FLAG column, which the user searched for, is one of the lead-level attributes surfaced by this view. It is passed through directly from AS_SALES_LEADS and indicates whether a lead has been flagged as requiring priority handling. Because the view also exposes QUALIFIED_FLAG, ACCEPT_FLAG, KEEP_FLAG, IMPORT_FLAG, and DELETED_FLAG, it provides a consolidated picture of lead disposition and routing status.

Underlying Base Objects

The documented base objects for AST_SALESLEAD_UWQ_V are:

The view is therefore a read-mostly construct: it does not own data, and all writes must be directed to the underlying base tables. In 12.2.2 the synonyms resolve to the same APPS-owned tables, so behavior is consistent across both releases.

Key Columns

The column list is dominated by two groups. The first is IEU integration metadata: IEU_OBJECT_FUNCTION, IEU_OBJECT_PARAMETERS, IEU_MEDIA_TYPE_UUID, IEU_PARAM_PK_COL, and IEU_PARAM_PK_VALUE. These allow the view to be registered as an IEU object and invoked from the interaction framework. The second group is business data: SALES_LEAD_ID, LEAD_NUMBER, DESCRIPTION, PARTY_ID, PARTY_NAME, STATUS_CODE, STATUS_MEANING, ASSIGN_DATE, ASSIGN_SALES_GROUP_ID, BUDGET_AMOUNT, CURRENCY_CODE, CHANNEL_CODE, PARENT_PROJECT, DECISION_TIMEFRAME_CODE, TOTAL_SCORE, LEAD_RANK_ID, RANK_MEANING, and the various disposition flags including URGENT_FLAG. Contact columns include CONTACT_PARTY_ID, PRIMARY_CONTACT_FIRST_NAME, PRIMARY_CONTACT_LAST_NAME, and a concatenated phone number assembled from HZ_CONTACT_POINTS.

Common Use Cases and Queries

Typical uses include building agent work queues, extracting leads for CRM synchronization, and reporting on urgent or high-scoring leads. A simple query to retrieve urgent open leads is:

  • SELECT LEAD_NUMBER, PARTY_NAME, STATUS_MEANING, URGENT_FLAG, TOTAL_SCORE FROM APPS.AST_SALESLEAD_UWQ_V WHERE URGENT_FLAG = 'Y' AND STATUS_CODE NOT IN ('CLOSED','CONVERTED');
  • SELECT ASSIGN_TO_SALESFORCE_ID, COUNT(*) FROM APPS.AST_SALESLEAD_UWQ_V GROUP BY ASSIGN_TO_SALESFORCE_ID;
  • SELECT LEAD_NUMBER, PRIMARY_CONTACT_FIRST_NAME, PRIMARY_CONTACT_LAST_NAME, PHONE_ID FROM APPS.AST_SALESLEAD_UWQ_V WHERE PARTY_ID = :party_id;

Because the view performs multiple outer joins, queries should filter on indexed lead columns such as SALES_LEAD_ID or ASSIGN_DATE where possible to avoid full scans.