Search Results primary_contact_first_name




Overview
Explore in AI Chat

Overview

The APPS.AST_MYTEAM_SALESLEAD_UWQ_V view is a TeleSales (AST) reporting and integration object that exposes sales leads assigned to a resource's team, structured specifically to support a Universal Work Queue (UWQ) or Salesforce-style external consumer. The suffix "UWQ" indicates its design intent: it flattens sales lead data, associated party information, primary contact details, and resource identifiers into a single queryable row set that a work queue or CRM integration layer can consume without issuing multiple joins.

The view is owned by the APPS schema and is documented as VALID in ETRM 12.2.2. Its column aliasing (prefixes such as IEU_ and RESOURCE_) and the inclusion of OBJECT_FUNCTION, OBJECT_PARAMETERS, and a primary-key parameter pair reveal a deliberate integration contract: each row carries the metadata required to locate, route, and deep-link a sales lead record in an external system. This makes the view relevant not only to in-EBS reporting but to any middleware or CRM synchronization process that ingests TeleSales leads.

Underlying Base Objects

Per the documented metadata, the view is defined over the following objects:

The view therefore joins three functional domains: TeleSales lead management (AS_*), JTF resource and object infrastructure, and TCA party/contact data (HZ_*).

Key Columns

Common Use Cases and Queries

The most frequent consumer pattern is retrieving qualified leads for a team or resource, which aligns directly with the qualified_flag search term:

SELECT sales_lead_id, lead_number, party_name,
       status_meaning, qualified_flag, urgent_flag,
       budget_amount, currency_code, resource_id
FROM   apps.ast_myteam_saleslead_uwq_v
WHERE  qualified_flag = 'Y'
AND    NVL(deleted_flag,'N') = 'N'
ORDER BY assign_date DESC;

UWQ integration typically selects the routing metadata alongside the payload:

SELECT ieu_object_function, ieu_object_parameters,
       ieu_param_pk_col, ieu_param_pk_value,
       resource_id, resource_type, lead_number
FROM   apps.ast_myteam_saleslead_uwq_v
WHERE  status_code = 'NEW';

Reporting queries often group qualified leads by resource and rank to measure pipeline distribution and scoring:

SELECT resource_id, rank_meaning, COUNT(*) lead_count,
       SUM(budget_amount) pipeline_value
FROM   apps.ast_myteam_saleslead_uwq_v
WHERE  qualified_flag = 'Y'
GROUP BY resource_id, rank_meaning;

Because the view joins large TCA and resource objects, queries against it should be filtered on indexed lead columns such as SALES_LEAD_ID, STATUS_CODE, or RESOURCE_ID wherever possible. Consumers should treat QUALIFIED_FLAG and the other single-character flags as Y/N indicators, applying NVL where nulls are possible.