Results for “list_source”

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

Overview

AST_PLIST_REF_UWQ_V is a read-only database view owned by the APPS schema within the Oracle E-Business Suite environment. It is a component of the AST (TeleSales) product family and is documented against release 12.2.2, with structural continuity into 12.1.1 given the shared AMS data model. The view's name reflects its function: it exposes a filtered projection of partner list ("PLIST") reference data, with the "UWQ" suffix denoting the universal work queue context in which TeleSales and Telemarketing agents consume list entries.

The view joins list header definitions to their constituent list entries, producing one row per entry that remains unprocessed. Its primary reporting role is to feed agent-facing work queues and list assignment logic, surfacing only entries where the outcome has not yet been recorded. Because it is a view rather than a table, it carries no storage of its own and is always resolved against the live base tables at query time, ensuring consumers see current assignment and duplication state.

Underlying Base Objects

The view is defined over two documented base objects:

• AMS_LIST_HEADERS_ALL (SYNONYM) — the master table of list definitions, supplying the owning resource, list name, source type, list type, source, and enabled status.
• AMS_LIST_ENTRIES (SYNONYM) — the child table holding individual list members, supplying entry identifiers, audit dates, duplication and control-group flags, and the customer/lead references.

The two objects are joined on LIST_HEADER_ID, with the view text deliberately applying both an equijoin and the condition ALH.LIST_HEADER_ID +0 = ALE.LIST_HEADER_ID. The +0 notation suppresses the outer-join syntax and forces a standard inner join, preventing list headers without entries from being returned. The final predicate, ALE.OUTCOME_ID IS NULL, restricts output to entries that have not been worked to a disposition. A SELECT DISTINCT is applied across the full column list to eliminate duplicate rows arising from the join.

Key Columns

• RESOURCE_ID — sourced from ALH.OWNER_USER_ID; identifies the resource or agent to whom the list belongs.
• LIST_HEADER_ID — the foreign key linking each entry to its owning list definition.
• LIST_ENTRY_ID — the unique identifier of the individual list member.
• LIST_NAME, LIST_SOURCE_TYPE, LIST_TYPE, LIST_SOURCE — descriptive attributes that classify the list and its origin.
• ENABLED_FLAG — indicates whether the parent list is active and therefore eligible for work-queue consumption.
• MARKED_AS_DUPLICATE_FLAG — the column matching the user's search; flags entries identified as duplicates during list import or processing, allowing them to be excluded from agent presentation.
• PART_OF_CONTROL_GROUP_FLAG — indicates membership in a control group, used for comparative list testing and response measurement.
• CUSTOMER_ID — exposed from the DFF column ALE.COL250, carrying the customer party reference.
• LEAD_ID — the identifier of the associated lead record.
• CREATION_DATE and LAST_UPDATE_DATE — standard audit columns on the entry record.

Common Use Cases and Queries

Typical consumers use the view to populate TeleSales work queues, audit duplicate suppression, and reconcile list membership against lead and customer data.

• Retrieving active, non-duplicate entries for a resource:
  SELECT LIST_ENTRY_ID, LEAD_ID, CUSTOMER_ID FROM AST_PLIST_REF_UWQ_V WHERE ENABLED_FLAG = 'Y' AND MARKED_AS_DUPLICATE_FLAG = 'N' AND RESOURCE_ID = :p_resource;
• Quantifying duplicate suppression on a list:
  SELECT MARKED_AS_DUPLICATE_FLAG, COUNT(*) FROM AST_PLIST_REF_UWQ_V WHERE LIST_HEADER_ID = :p_header GROUP BY MARKED_AS_DUPLICATE_FLAG;
• Isolating control-group membership for analysis:
  SELECT COUNT(*) FROM AST_PLIST_REF_UWQ_V WHERE PART_OF_CONTROL_GROUP_FLAG = 'Y' AND LIST_HEADER_ID = :p_header;

Because the view already filters on OUTCOME_ID IS NULL, queries cannot retrieve completed entries; historical reporting must instead target AMS_LIST_ENTRIES directly.