Search Results ast_salesopp_code_uwq_v




Overview
Explore in AI Chat

Overview

AST_SALESOPP_CODE_UWQ_V is an APPS-owned, valid database view in the Oracle E-Business Suite TeleSales (AST) module. The "UWQ" naming convention identifies it as a Universal Work Queue (UWQ) integration view. Its purpose is to expose sales opportunity and lead records in a normalized, flattened form that the Universal Work Queue and Interaction Center (IEU) infrastructure can consume for agent task routing, inbound/outbound telesales workflows, and opportunity search.

The view is particularly relevant to the search term sales_methodology_name. While the view text is dominated by opportunity, lead, party, contact, and resource columns, the documented referenced base objects include AS_SALES_METHODOLOGY_TL — the translation table for sales methodologies. This means the view participates in the sales methodology data model and can be joined to that table (or to a companion view) to surface the methodology name. For that reason, the object is frequently examined by implementers searching for sales_methodology_name in the TeleSales schema.

Because the view is a reporting/integration construct rather than a base table, it presents query-ready, descriptive values — status meanings, channel meanings, probability meanings, and formatted contact data — rather than raw lookup codes alone.

Underlying Base Objects

The view is defined over a broad set of foundation tables and synonyms. The primary driving object is AS_LEADS_ALL, aliased as OPP in the view text, which supplies the opportunity/lead record and most numeric and date values. Supporting objects include AS_SALES_STAGES_ALL_TL (stage names), AS_STATUSES_TL (status meanings), AS_FORECAST_PROB_ALL_TL (probability meanings), AS_LOOKUPS, OE_LOOKUPS, and AMS_SOURCE_CODES.

Party and contact data is sourced from HZ_PARTIES, HZ_RELATIONSHIPS, HZ_ORG_CONTACTS, HZ_CONTACT_POINTS, HZ_LOCATIONS, HZ_PARTY_SITES, AS_LEAD_CONTACTS_ALL, and AS_ACCESSES_ALL. Resource and ownership information comes from FND_USER and JTF_RS_RESOURCE_EXTNS. The UWQ plumbing columns are derived from JTF_OBJECTS_B, and AS_SALES_CREDITS and AS_SALES_METHODOLOGY_TL are documented as referenced objects. The view is built with the /*+ FIRST_ROWS */ hint, reflecting its design for interactive, first-page-fast retrieval.

Key Columns

Common Use Cases and Queries

Typical usage includes populating Universal Work Queue nodes, rendering opportunity lists inside TeleSales and Interaction Center agent dashboards, and driving inbound lead qualification screens. To surface methodology names, developers join the view to AS_SALES_METHODOLOGY_TL.

SELECT LEAD_ID, LEAD_NUMBER, DESCRIPTION, SALES_STAGE_NAME, PROBABILITY_MEANING, PARTY_NAME FROM APPS.AST_SALESOPP_CODE_UWQ_V WHERE ORG_ID = :p_org_id ORDER BY LAST_UPDATE_DATE DESC;

SELECT V.LEAD_ID, V.LEAD_NUMBER, V.TOTAL_AMOUNT, M.METHODOLOGY_NAME FROM APPS.AST_SALESOPP_CODE_UWQ_V V, AS_SALES_METHODOLOGY_TL M WHERE V.ORG_ID = :p_org_id;

Because the view applies FIRST_ROWS, ad-hoc queries should filter aggressively on LEAD_ID, RESOURCE_ID, or ORG_ID to avoid full scans of the underlying leads and HZ party tables.