Search Results ieu_action_object_code




Overview
Explore in AI Chat

Overview

AST_MLIST_ALLSECURE_UWQ_V is a secure database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AST (TeleSales) product family. It exposes marketing list membership data drawn from the Oracle Marketing (AMS) tables, tightly coupled to call center schedules. In Release 12.1.1 and 12.2.2 the view serves as a Universal Work Queue (UWQ) integration point: it projects a standardized set of Interaction/E-Business Integration (IEU) attributes alongside detailed caller and list-entry context. This dual role makes it the bridge between TeleSales agent workflow and the underlying campaign list definitions.

The view is SQL-based, formed from a join across campaign schedules, list headers, list entries, activity lists, and source codes. Access is restricted to lists that are actively enabled, unresolved (no outcome recorded), and linked to a campaign schedule as a target audience. Because it filters on IEU_ACTION_OBJECT_CODE = 'PARTY', it is commonly located when developers search on that keyword while diagnosing telemarketing work queues or building custom integrations.

Underlying Base Objects

Per the documented metadata, the view references five base objects: AMS_ACT_LISTS (SYNONYM), AMS_CAMPAIGN_SCHEDULES_VL (VIEW), AMS_LIST_ENTRIES (SYNONYM), AMS_LIST_HEADERS_ALL (SYNONYM), and AMS_SOURCE_CODES (SYNONYM).

  • AMS_ACT_LISTS — maps activities to the lists they consume, constraining the join to LIST_USED_BY = 'CSCH' and LIST_ACT_TYPE = 'TARGET'.
  • AMS_CAMPAIGN_SCHEDULES_VL — provides schedule identity, name, status and source code.
  • AMS_LIST_HEADERS_ALL — supplies list name, header ID, source type and list type.
  • AMS_LIST_ENTRIES — the primary row source, providing party, name, address, phone, email and entry-level attributes, filtered by ENABLED_FLAG = 'Y' and OUTCOME_ID IS NULL.
  • AMS_SOURCE_CODES — joined on SOURCE_CODE and SOURCE_CODE_FOR_ID to resolve source attribution.

Key Columns

The view exposes both IEU routing columns and descriptive list-entry columns:

Common Use Cases and Queries

TeleSales administrators and integrators query this view to build UWQ work lists, validate list membership, or reconcile queue volumes against campaign schedules. Typical patterns include retrieving all party rows for a schedule or filtering active contacts by phone or email.

Sample query for a specific schedule:

  • SELECT list_name, full_name, phone, email_address, party_id, ieu_action_object_code FROM ast_mlist_allsecure_uwq_v WHERE schedule_id = :p_schedule_id ORDER BY last_name;

Sample query confirming routing metadata:

  • SELECT DISTINCT ieu_object_function, ieu_action_object_code, ieu_param_pk_col, ieu_param_pk_value FROM ast_mlist_allsecure_uwq_v WHERE list_header_id = :p_list_header_id;

Because rows are limited to enabled, unresolved entries linked as targets, the view naturally reflects only work still outstanding for the associated schedule, making it suitable for workload monitoring and outbound/dialer integrations.