Search Results close_competitor_code




Overview
Explore in AI Chat

Overview

AST_PLIST_OPP_UWQ_V is a TeleSales (AST) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents opportunity and lead data structured for the Universal Work Queue (UWQ) and the interaction/object framework used by the TeleSales and iSupport agent interfaces. The view's internal naming (IEU_OBJECT_FUNCTION, IEU_MEDIA_TYPE_UUID, IEU_PARAM_PK_COL, IEU_PARAM_PK_VALUE) confirms its role as a provider of object-instance definitions back to the Interaction and Object framework; the fixed literal values 'OPPORTUNITY' OBJECT_CODE and 'LEAD_ID' IEU_PARAM_PK_COL identify each row as an opportunity keyed by LEAD_ID.

Rather than simply listing lead columns, the view pre-joins reference data — sales stages, statuses, win-probability meanings, sales channels, decision timeframes, currency, and the full set of contact and phone attributes — so that agents viewing a work-queue item obtain a denormalized, immediately displayable record. This makes the view both a reporting source and a runtime feeder for UWQ-driven screens.

The user's search term, close_competitor_code, targets a competitive-win/loss attribute commonly stored on the opportunity record. In this view the exposed opportunity attributes are drawn from OPP (AS_LEADS_ALL); competitive and close-reason fields are not documented as explicit projected columns in the supplied view text, though competitive data is normally recorded against the opportunity at close time in the base lead table. Analysts should therefore treat the view as a source for opportunity identity and status, and query the underlying AS_LEADS_ALL table directly when close-competitor detail is required.

Underlying Base Objects

The view is defined over a broad set of APPS synonyms and views, joined to enrich the core opportunity row:

Key Columns

Common Use Cases and Queries

Typical uses include UWQ queue population, agent opportunity dashboards, and pipeline extracts. A basic query:

  • SELECT lead_id, lead_number, party_name, sales_stage_name, status_meaning, win_probability, resource_id FROM apps.ast_plist_opp_uwq_v WHERE org_id = :org_id;
  • Filtering by owner for workload analysis: ... WHERE resource_id = :user_id ORDER BY decision_date;
  • Joining back to AS_LEADS_ALL on LEAD_ID to retrieve competitive or close-reason fields such as close_competitor_code when those columns are not projected by the view.