Results for “marked_as_duplicate_flag”

16 results




Overview
Explore in AI Chat

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

Overview

The AST_PLIST_REF_OPP_UWQ_V view is a TeleSales (AST) reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name follows the EBS convention for a "UWQ" (Universal Work Queue) view combined with the "PLIST" (personal list) and "REF_OPP" (reference opportunity) tokens. The view consolidates personal list header and entry data from the Advanced Marketing/TeleSales list infrastructure and joins it to lead/opportunity records, exposing the result as a resource-scoped work queue of leads and opportunities that are candidates for telesales follow-up.

The defining characteristic of the view is its filter predicate ALE.OUTCOME_ID IS NULL, meaning only list entries that have not yet been dispositioned are returned. This makes the view a working queue rather than a historical log: each row represents an open, unworked lead or opportunity assigned to a resource through a personal list. The user's search term, PART_OF_CONTROL_GROUP_FLAG, is projected directly from AMS_LIST_ENTRIES into the view's column list and identifies entries that belong to a control group — a segment commonly excluded from reporting on treatment effectiveness.

Underlying Base Objects

The documented base objects are three synonyms over their respective base tables:

The text uses a SELECT DISTINCT and a join on ALH.LIST_HEADER_ID = ALE.LIST_HEADER_ID augmented by ALH.LIST_HEADER_ID + 0 = ALE.LIST_HEADER_ID. The +0 form nullifies the index on the header key, typically forcing the optimizer toward a different join order or plan — a common EBS workaround for cardinality misestimation.

Key Columns

  • RESOURCE_ID — the list owner (from ALH.OWNER_USER_ID), i.e. the resource whose queue this row belongs to.
  • LIST_HEADER_ID / LIST_NAME — the personal list identity, useful for grouping queue rows by source list.
  • LIST_TYPE, LIST_SOURCE_TYPE, LIST_SOURCE — metadata describing how the list was populated and what it is used for.
  • ENABLED_FLAG — whether the list header is active.
  • LIST_ENTRY_ID — the unique assignment row identifier, the natural primary key for the entry.
  • LEAD_ID — the lead/opportunity key joining to AS_LEADS_ALL.
  • CUSTOMER_ID — projected from ALE.COL250, a generic custom column repurposed here to carry the customer identifier.
  • MARKED_AS_DUPLICATE_FLAG — indicates the entry is a suspected duplicate; often filtered out of counts.
  • PART_OF_CONTROL_GROUP_FLAG — marks entries assigned to a control group, typically excluded when measuring treatment lift.
  • CREATION_DATE / LAST_UPDATE_DATE — entry-level audit timestamps.
  • ORG_ID — the operating unit of the underlying lead.

Common Use Cases and Queries

Typical applications include building resource work queues, analyzing list load and ageing, and separating control-group entries from treatment entries. A basic queue query by resource:

SELECT RESOURCE_ID, LIST_NAME, LEAD_ID, CUSTOMER_ID, CREATION_DATE
  FROM APPS.AST_PLIST_REF_OPP_UWQ_V
 WHERE RESOURCE_ID = :p_resource_id
   AND ENABLED_FLAG = 'Y'
  ORDER BY CREATION_DATE;

To exclude control-group and duplicate entries from performance reporting:

SELECT LIST_HEADER_ID, COUNT(*) open_entries
  FROM APPS.AST_PLIST_REF_OPP_UWQ_V
 WHERE NVL(PART_OF_CONTROL_GROUP_FLAG,'N') = 'N'
   AND NVL(MARKED_AS_DUPLICATE_FLAG,'N') = 'N'
 GROUP BY LIST_HEADER_ID;

Because the view already restricts to undispositioned entries, callers do not need to add an outcome predicate; doing so against the base tables is the usual alternative if additional entry columns are required.