Search Results repeat_exclude_type




Overview
Explore in AI Chat

Overview

AST_PLIST_NAMES_UWQ_V is a TeleSales (AST) application view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the personal list headers maintained by the Advanced Sales and TeleSales (AMS) module in a form adapted to the Universal Work Queue (UWQ) integration model used by the Interaction Center and TeleSales agent interfaces. The view projects the core list-header attributes alongside a set of synthetic UWQ routing columns (IEU_OBJECT_FUNCTION, IEU_OBJECT_PARAMETERS, IEU_MEDIA_TYPE_UUID, IEU_PARAM_PK_COL, IEU_PARAM_PK_VALUE, RESOURCE_TYPE, RESOURCE_ID) that allow the Universal Work Queue infrastructure to treat each personal list as a routable work item assigned to an individual resource. Because it is a view rather than a table, no data is stored in it; all content is derived at query time from the underlying base objects, guaranteeing that list status and forecasting information remains consistent with the AMS transactional tables.

Underlying Base Objects

The documented base object for this view is AMS_LIST_HEADERS_VL, itself a translatable view over the AMS_LIST_HEADERS_B and AMS_LIST_HEADERS_TL tables. The view text confirms a direct, non-joined projection: every column in AST_PLIST_NAMES_UWQ_V is selected from AMS_LIST_HEADERS_VL, with the leading UWQ columns supplied as literal NULLs and the RESOURCE_TYPE column hard-coded to the literal 'RS_INDIVIDUAL'. RESOURCE_ID is aliased from OWNER_USER_ID, so each row is attributed to the owning user rather than to a group or organization resource. This design gives the view a one-to-one cardinality with the personal list header rows and makes it a lightweight, filter-friendly interface for UWQ consumers.

Key Columns

Common Use Cases and Queries

Typical usage includes TeleSales agent dashboards, UWQ work-item routing, and reporting on upcoming or overdue list generation. A frequent query filters on the forecasted start date, for example:

  • SELECT list_header_id, list_name, forecasted_start_date, forecasted_end_date, status_code FROM ast_plist_names_uwq_v WHERE forecasted_start_date BETWEEN :start AND :end AND org_id = :org_id;
  • SELECT resource_id, COUNT(*) FROM ast_plist_names_uwq_v WHERE enabled_flag = 'Y' GROUP BY resource_id;
  • SELECT list_name, no_of_rows_in_list, no_of_rows_duplicates FROM ast_plist_names_uwq_v WHERE last_generation_success_flag = 'N';

Because the view is defined over AMS_LIST_HEADERS_VL, report and integration developers should remember that forecasted dates reflect the planned schedule recorded on the list header, not the list's runtime execution history, and that only individual-owned lists (RESOURCE_TYPE = 'RS_INDIVIDUAL') are represented.