Results for “ast_mlist_uwq_v”
30 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AST_MLIST_UWQ_V is a read-only database view owned by the APPS schema within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments. It belongs to the AST (TeleSales) product family and functions as a consolidated, presentation-ready data source for marketing list entries that are eligible for telemarketing and outbound campaign processing. The view joins campaign schedule definitions, marketing list headers, list entries, campaign list assignments, and source code definitions into a single flat row set.
Its primary role is to expose the set of marketing list members that are associated with active campaign schedules and that have not yet been worked. This is expressed through the IEU_* columns, which are formatted for interaction with the Intelligence Enterprise Unified Work Queue (IEU) framework that drives agent-facing work queues in TeleSales. The view therefore acts as a bridge between the AMS (marketing) transactional tables and the AST agent desktop, and it is commonly consumed by concurrent programs, workflow activities, and custom reports that need a unified queue of callable prospects.
Underlying Base Objects
The view is defined over five documented base objects:
- AMS_CAMPAIGN_SCHEDULES_VL — supplies the schedule identifier, schedule name, status code, and source code for each campaign schedule.
- AMS_LIST_HEADERS_ALL — provides the marketing list header attributes, including LIST_NAME, LIST_HEADER_ID, LIST_SOURCE_TYPE, and LIST_TYPE.
- AMS_LIST_ENTRIES — the primary detail table, contributing names, addresses, contact points, phone, email, and the PARTY_ID linkage.
- AMS_ACT_LISTS — the association table linking schedules to list headers; the view filters on LIST_USED_BY = 'CSCH', LIST_ACT_TYPE = 'TARGET'.
- AMS_SOURCE_CODES — resolves the source code to its identifier through SOURCE_CODE and SOURCE_CODE_FOR_ID.
All AMS objects are referenced through APPS synonyms. The joins enforce strict filtering: only entries with a NULL OUTCOME_ID and an ENABLED_FLAG of 'Y' are returned, meaning that already-worked or disabled list members are excluded from the queue.
Key Columns
The view exposes several categories of columns:
- IEU integration columns — IEU_OBJECT_FUNCTION ('AST_RC_ALL'), IEU_OBJECT_PARAMETERS, IEU_ACTION_OBJECT_CODE ('PARTY'), IEU_PARAM_PK_COL ('PARTY_ID'), and IEU_PARAM_PK_VALUE, which together allow the work queue framework to launch the correct TeleSales action for the associated party.
- Schedule context — SCHEDULE_ID, SCHEDULE_NAME, STATUS_CODE, SOURCE_CODE, and RESOURCE_TYPE ('RS_INDIVIDUAL'), identifying the campaign context for the entry.
- List and entry identifiers — LIST_NAME, LIST_HEADER_ID, LIST_SOURCE_TYPE, LIST_TYPE, LIST_ENTRY_ID, and SUFFIX, which uniquely locate the record within the marketing hierarchy.
- Contact attributes — FIRST_NAME, LAST_NAME, FULL_NAME, CUSTOMER_NAME, TITLE, ADDRESS_LINE1/2, CITY, STATE, ZIPCODE, COUNTRY, PHONE, EMAIL_ADDRESS, LOCATION_ID, and CONTACT_POINT_ID.
- Audit and control flags — CREATION_DATE, LAST_UPDATE_DATE, MARKED_AS_DUPLICATE_FLAG, and PART_OF_CONTROL_GROUP_FLAG.
Common Use Cases and Queries
The most frequent use is building the agent work queue for a given schedule or list. A typical query returns the unworked, enabled entries for a schedule:
- SELECT LIST_ENTRY_ID, FULL_NAME, PHONE, EMAIL_ADDRESS FROM AST_MLIST_UWQ_V WHERE SCHEDULE_ID = :p_schedule_id;
- SELECT LIST_NAME, COUNT(*) FROM AST_MLIST_UWQ_V GROUP BY LIST_NAME;
- SELECT PARTY_ID, FULL_NAME, CITY, STATE FROM AST_MLIST_UWQ_V WHERE MARKED_AS_DUPLICATE_FLAG = 'N';
Because the view filters on OUTCOME_ID IS NULL, results represent only prospective contacts. Analysts frequently aggregate by SCHEDULE_NAME or LIST_SOURCE_TYPE to measure queue volume, and developers embed the view in custom PL/SQL to feed dialer integrations or CRM extracts. It should be noted that the view is not updatable; DML must target the underlying AMS_LIST_ENTRIES table.
-
View: AST_MLIST_UWQ_V 12.1.1
APPS.AST_MLIST_UWQ_V·↳ AMS_ACT_LISTS·↳ AMS_CAMPAIGN_SCHEDULES_VL·↳ AMS_LIST_ENTRIES·Explore AST module →
-
View: AST_MLIST_UWQ_V 12.2.2
APPS.AST_MLIST_UWQ_V·↳ AMS_ACT_LISTS·↳ AMS_CAMPAIGN_SCHEDULES_VL·↳ AMS_LIST_ENTRIES·Explore AST module →
-
VIEW: APPS.AST_MLIST_UWQ_V 12.1.1
-
VIEW: APPS.AST_MLIST_UWQ_V 12.2.2
-
SYNONYM: APPS.AMS_ACT_LISTS 12.2.2
-
SYNONYM: APPS.AMS_ACT_LISTS 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
eTRM - AST Tables and Views 12.2.2
All available web searches
-
eTRM - AST Tables and Views 12.1.1
All available web searches
-
12.2.2 DBA Data 12.2.2
-
eTRM - AMS Tables and Views 12.2.2
This table is used to store tracking data for web advertisement and offer type schedules
-
12.1.1 DBA Data 12.1.1
-
eTRM - AMS Tables and Views 12.1.1
This table is used to store tracking data for web advertisement and offer type schedules
-
eTRM - AST Tables and Views 12.1.1
All available web searches
-
eTRM - AST Tables and Views 12.2.2
All available web searches
-
eTRM - AMS Tables and Views 12.2.2
This table is used to store tracking data for web advertisement and offer type schedules
-
eTRM - AMS Tables and Views 12.1.1
This table is used to store tracking data for web advertisement and offer type schedules