Results for “ast_mlist1_uwq_v”

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

Overview

AST_MLIST1_UWQ_V is a TeleSales (AST) view owned by the APPS schema in Oracle EBS 12.1.1 and 12.2.2. It exposes the set of active, currently valid campaign resources that should be presented to a TeleSales agent through the Universal Work Queue (UWQ). The view is a union of two population branches: one that returns individual resources directly assigned to a campaign, and one that returns group members expanded from resource groups associated with a campaign. Both branches share an identical projection, producing a uniform result set of campaign schedules and the resources eligible to work them.

The view name carries the "MLIST1" convention, indicating it is the base list definition whose SQL text is stored by TeleSales and invoked by the work queue framework. The columns prefixed IEU_ exist to satisfy the interaction/telephony layer expectations of the UWQ; in this view they are returned as literal empty strings or NULL because the routing context is not supplied at this level.

This is a strongly relevant object when users search for AMS_CAMPAIGN_SCHEDULES_VL, since that campaign schedule view is the driving object in both branches of this view's SQL text. Anyone analyzing campaign-driven TeleSales worklists will encounter AST_MLIST1_UWQ_V as the consumer of AMS_CAMPAIGN_SCHEDULES_VL.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over the following referenced objects, all resolved through synonyms in APPS:

• AMS_CAMPAIGN_SCHEDULES_VL — the campaign schedule view that supplies schedule identifier, name, status, source, activity, dates and marketing medium.
• AST_RS_CAMPAIGNS — maps campaigns to individual resources for the first union branch.
• AST_GRP_CAMPAIGNS — maps campaigns to resource groups for the second union branch.
• JTF_RS_GROUPS_DENORM — denormalized resource group hierarchy used to resolve parent/child group relationships.
• JTF_RS_GROUP_MEMBERS — expands group membership into individual resource IDs.
• AMS_LIST_HEADERS_ALL — provides list header context and the list source type.
• AMS_ACT_LISTS — links the schedule to its list header with a usage type of TARGET.

The first branch joins AMS_CAMPAIGN_SCHEDULES_VL to AST_RS_CAMPAIGNS on campaign ID and schedule ID. The second branch joins through AST_GRP_CAMPAIGNS, JTF_RS_GROUPS_DENORM and JTF_RS_GROUP_MEMBERS, using a LEADING(GRPMEM) hint to drive execution from the membership table.

Key Columns

• RESOURCE_TYPE — literal 'RS_INDIVIDUAL' in both branches, confirming each returned row represents one individual resource.
• SCHEDULE_ID — the campaign schedule identifier, derived from AMS_CAMPAIGN_SCHEDULES_VL.
• SCHEDULE_NAME — descriptive name of the campaign schedule.
• STATUS_CODE and SOURCE_CODE — status and origin of the schedule.
• ACTIVITY_ID and ACTIVITY_TYPE_CODE — activity context; the view filters on ACTIVITY_ID = 460.
• ARC_MARKETING_MEDIUM_FROM — marketing medium used for the campaign.
• CREATION_DATE and LAST_UPDATE_DATE — audit columns from the schedule.
• START_DATE_TIME and END_DATE_TIME — campaign schedule validity window.
• RESOURCE_ID — the individual resource, sourced either from AST_RS_CAMPAIGNS or from JTF_RS_GROUP_MEMBERS.
• LIST_SOURCE_TYPE — list source classification from AMS_LIST_HEADERS_ALL.
• IEU_OBJECT_FUNCTION, IEU_OBJECT_PARAMETERS, IEU_MEDIA_TYPE_UUID, IEU_PARAM_PK_COL, IEU_PARAM_PK_VALUE — placeholders populated as empty strings or NULL.

Common Use Cases and Queries

Typical uses include validating which resources a TeleSales agent should see for currently active campaigns, troubleshooting why a resource is missing from a worklist, and reconciling campaign schedules against their assigned resources. The view applies several effective filters: the schedule must be active, have status ACTIVE, point at activity 460, and fall within a date window defined by TRUNC(SYSDATE) between NVL(START_DATE_TIME-1, TRUNC(SYSDATE)) and NVL(END_DATE_TIME, TRUNC(SYSDATE)).

A sample query listing resources for active schedules:

• SELECT SCHEDULE_ID, SCHEDULE_NAME, RESOURCE_ID, LIST_SOURCE_TYPE FROM APPS.AST_MLIST1_UWQ_V ORDER BY SCHEDULE_ID, RESOURCE_ID;
• SELECT RESOURCE_ID, COUNT(*) FROM APPS.AST_MLIST1_UWQ_V GROUP BY RESOURCE_ID HAVING COUNT(*) > 1;
• SELECT SCHEDULE_ID, SCHEDULE_NAME, START_DATE_TIME, END_DATE_TIME FROM APPS.AST_MLIST1_UWQ_V WHERE TRUNC(SYSDATE) BETWEEN START_DATE_TIME AND END_DATE_TIME;

These queries support workload balancing, duplicate resource detection, and confirmation that the schedule validity window aligns with the current date, which is central to the view's expected output.