Results for “status_meaning”

50+ results




Overview
Explore in AI Chat

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

Overview

The AS_SALES_LEAD_UWQ_V view is an APPS-owned database view within the Oracle E-Business Suite Sales Foundation (AS) product family. As indicated by its name, the object is designed to serve the Universal Work Queue (UWQ), the framework that delivers prioritized, role-based work item lists to users across Oracle applications such as TeleSales, iStore, and Field Service. The view exposes sales lead records together with the associated resource assignment, party name, status description, and a derived resource-type code that classifies the assignee as either an employee or a channel partner.

In Oracle EBS 12.1.1 and 12.2.2, the view status is VALID and it is defined in the APPS schema. Because it presents denormalized lead information in a form ready for queue consumption, it is equally suitable for custom reporting and integration queries that need a compact, business-friendly projection of sales leads. The view is a read-only construct; no data manipulation is performed against it directly.

Underlying Base Objects

The ETRM metadata documents the following base objects referenced by the view, all accessed through APPS synonyms:

  • AS_SALES_LEADS — the primary lead entity, providing lead identity, description, customer, status, assignment, budget, and currency data.
  • AS_STATUSES_B — the base status definition table for Sales Foundation, supplying the status code used to join and translate lead statuses.
  • AS_STATUSES_TL — the translated status table, supplying the language-specific status meaning.
  • HZ_PARTIES — the Trading Community Architecture (TCA) party table, supplying the customer or prospect party name.
  • JTF_RS_RESOURCE_EXTNS — the resource extension table for the JTF Resource Manager, supplying the resource category used to derive the resource type.

Joins are established on SALES_LEAD_ID, STATUS_CODE, CUSTOMER_ID = PARTY_ID, and ASSIGN_TO_SALESFORCE_ID = RESOURCE_ID. Status translation is filtered by USERENV('LANG') so that the status meaning returned matches the session language.

Key Columns

  • LEAD_ID — the sales lead identifier (source column SALES_LEAD_ID).
  • DESCRIPTION — free-text description of the lead.
  • PARTY_ID — the customer or prospect party identifier.
  • PARTY_NAME — the party name resolved from HZ_PARTIES.
  • STATUS_CODE — the lead status code as stored on the lead record.
  • STATUS_MEANING — the translated status meaning from AS_STATUSES_TL.
  • RESOURCE_ID — the assigned sales resource identifier.
  • ASSIGN_SALES_GROUP_ID — the sales group to which the lead is assigned.
  • BUDGET_AMOUNT and CURRENCY_CODE — the estimated budget and its currency.
  • OBJECT_CODE — the literal value 'LEAD', used by UWQ to identify the object type of the work item.
  • RESOURCE_TYPE — a derived code produced by a DECODE on the resource category: RS_EMPLOYEE for employee resources and RS_PARTNER for partner resources, otherwise NULL.

Common Use Cases and Queries

The view supports work queue rendering, lead assignment reporting, and integration extracts. The following query retrieves all leads assigned to channel partners:

  • SELECT LEAD_ID, DESCRIPTION, PARTY_NAME, STATUS_MEANING, BUDGET_AMOUNT, CURRENCY_CODE FROM AS_SALES_LEAD_UWQ_V WHERE RESOURCE_TYPE = 'RS_PARTNER';

A second common pattern aggregates lead workload by assigned resource and status:

  • SELECT RESOURCE_ID, STATUS_MEANING, COUNT(*) LEAD_COUNT, SUM(BUDGET_AMOUNT) TOTAL_BUDGET FROM AS_SALES_LEAD_UWQ_V GROUP BY RESOURCE_ID, STATUS_MEANING ORDER BY RESOURCE_ID;

Because the object is a view over TCA and Sales Foundation tables, standard EBS security applies at the base object level; access to the view is governed by grants on the APPS synonym.