Search Results cnt_point

Overview

APPS.AST_MYTEAM_SALESLEAD_UWQ_V is a reporting and integration view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema. It presents sales lead information in a flattened, denormalized form intended primarily for consumption by Oracle Sales for Salesforce integration and Universal Work Queue (UWQ) processing. The view resolves the object-level attributes required by the JTF object framework, exposing IEU_OBJECT_FUNCTION, IEU_OBJECT_PARAMETERS, IEU_MEDIA_TYPE_UUID, IEU_PARAM_PK_COL, and IEU_PARAM_PK_VALUE so that each sales lead row can be treated as an addressable IEU object instance keyed on SALES_LEAD_ID.

The name indicates its functional scope: "MYTEAM" reflects the My Team resource hierarchy, "SALESLEAD" identifies the transactional entity, and "UWQ" denotes the Universal Work Queue. The view joins lead, party, contact, resource, and lookup data so that a single row carries every attribute needed to render or route a sales lead without additional lookups.

Underlying Base Objects

The documented base objects underlying this view are:

• AS_ACCESSES_ALL (VIEW) — provides sales-force access and resource assignment context.
• AS_LOOKUPS (VIEW) — supplies lookup meanings, notably VEHICLE_RESPONSE_CODE.
• AS_SALES_LEADS (SYNONYM) — the primary transactional table for sales lead records.
• AS_SALES_LEAD_RANKS_TL (SYNONYM) — the translated lead ranking table, joined for RANK.MEANING.
• AS_STATUSES_VL (VIEW) — resolves STATUS_CODE into STATUS_MEANING.
• HZ_CONTACT_POINTS (SYNONYM) — source for the contact point (phone) attributes aliased as CNT_POINT.
• HZ_LOCATIONS, HZ_ORG_CONTACTS, HZ_PARTIES, HZ_PARTY_SITES, HZ_RELATIONSHIPS (SYNONYMS) — the TCA foundation supplying party, contact, job title, and relationship data.
• JTF_OBJECTS_B (SYNONYM) — provides the IEU object framework attributes (OBJB.object_function, OBJB.object_parameters).
• JTF_RS_RESOURCE_EXTNS (SYNONYM) — resolves the Salesforce resource identifier.
• OE_LOOKUPS (VIEW) — additional lookup support.

The view therefore sits over both the CRM sales-lead data model and the TCA/HZ party model, with the JTF object registry used to expose it as an IEU-enabled object.

Key Columns

• SALES_LEAD_ID and LEAD_NUMBER — the primary key of the lead and its user-facing number.
• RESOURCE_ID, RESOURCE_TYPE — the owning Salesforce resource; type is hard-coded to RS_INDIVIDUAL.
• PARTY_ID, PARTY_NAME — the customer party associated with the lead.
• STATUS_CODE, STATUS_MEANING — lead status and its decoded meaning.
• BUDGET_AMOUNT, CURRENCY_CODE — budgeted value, with a concatenated amount-and-currency expression.
• CONTACT_PARTY_ID, PRIMARY_CONTACT_FIRST_NAME, PRIMARY_CONTACT_LAST_NAME, PRIMARY_CONTACT_MIDDLE_NAME — the primary contact person on the lead.
• PHONE_ID, CONTACT_JOB_TITLE — contact phone identifier derived from CNT_POINT.CONTACT_POINT_ID and the associated job title. The phone expression concatenates PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER, and PHONE_EXTENSION using DECODE to omit separators for null segments — this is the cnt_point reference the user searched for.
• URGENT_FLAG, QUALIFIED_FLAG, ACCEPT_FLAG, KEEP_FLAG, IMPORT_FLAG, DELETED_FLAG — lead state indicators.
• TOTAL_SCORE, LEAD_RANK_ID, RANK_MEANING — lead scoring and ranking.
• CREATION_DATE, UPDATED_BY, LAST_UPDATE_DATE — audit columns; creation date is sourced from the resource extension object.

Common Use Cases and Queries

Typical consumption is from Oracle Sales for Salesforce synchronization routines, Universal Work Queue listings, and ad hoc reporting on lead pipelines. A sample query retrieving leads with contact phone information follows:

SELECT sales_lead_id,
       lead_number,
       party_name,
       primary_contact_first_name,
       primary_contact_last_name,
       phone_id,
       status_meaning,
       budget_amount,
       currency_code,
       total_score
FROM   apps.ast_myteam_saleslead_uwq_v
WHERE  NVL(deleted_flag,'N') = 'N'
AND    status_code = 'OPEN';

To isolate leads by assigned resource and rank:

SELECT resource_id,
       lead_number,
       rank_meaning,
       urgent_flag,
       qualified_flag
FROM   apps.ast_myteam_saleslead_uwq_v
WHERE  resource_type = 'RS_INDIVIDUAL'
AND    NVL(qualified_flag,'N') = 'Y';

Because the view exposes IEU_PARAM_PK_COL and IEU_PARAM_PK_VALUE, it can be registered as a JTF object so that UWQ and IEU-driven interfaces resolve each lead as SALES_LEAD_ID-addressed entity. Reporting against cnt_point columns is most precise when filtering on phone_id rather than the concatenated phone string, since the string expression returns formatting separators that complicate matching.