Search Results ieu_lov_col2




Overview
Explore in AI Chat

Overview

AST_SALESREP_LOV_UWQ_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite TeleSales module (AST). It is documented as a VALID database object in ETRM releases 12.1.1 and 12.2.2. The view is designed to supply a filtered, pre-sorted list of sales representatives for use in List of Values (LOV) mechanisms and associated user-interface queries. Users and developers searching for sales_group_name will find that this column is explicitly projected by the view, making AST_SALESREP_LOV_UWQ_V a convenient access point for sales group information without requiring a direct query against more complex underlying sales representative entities.

The "UWQ" naming convention indicates that this object is associated with Oracle's Universal Work Queue framework, which drives many TeleSales and interaction-center agent screens. In that context, the view acts as a lightweight data source for populating LOV windows, enabling agents and application code to select a sales representative while displaying contextual attributes such as the sales group, full name, and contact details.

Underlying Base Objects

The documented metadata identifies a single referenced base object: AST_SALESREP_LOV_V, itself a view in the APPS schema. AST_SALESREP_LOV_UWQ_V is therefore a thin wrapper or projection layer. The view text selects a defined column list from AST_SALESREP_LOV_V, aliased as ASV, applies a trivial WHERE 1=1 predicate, and orders the results by IEU_LOV_COL2. This architecture implies that the substantive join logic and business rules — linking sales representatives to employees, salesforces, and sales groups — reside in AST_SALESREP_LOV_V rather than in the UWQ view itself. Any modification to the base view's definition (for example, changes in how sales group membership is derived) propagates automatically to this dependent view.

Key Columns

The view exposes thirteen columns:

  • IEU_LOV_COL1 through IEU_LOV_COL4 — Generic LOV display columns whose values are determined by the base view. These typically carry concatenated or formatted display strings used by the LOV widget.
  • SALES_GROUP_NAME — The descriptive name of the sales group to which a representative belongs; this is the column most relevant to searches on "sales_group_name."
  • SALES_GROUP_ID — The internal identifier of the sales group, suitable for programmatic filtering and joins.
  • SALESREP_FULL_NAME, SALESREP_LAST_NAME, SALESREP_FIRST_NAME — Name attributes of the sales representative.
  • EMPLOYEE_PERSON_ID — The HR person identifier linking the sales representative to the employee record.
  • SALESFORCE_ID — Identifier of the associated salesforce, supporting organizational filtering.
  • WORK_TELEPHONE and EMAIL_ADDRESS — Contact details useful for outbound TeleSales activities.

Common Use Cases and Queries

Typical usage involves restricting the LOV to a particular sales group or salesforce, or resolving a sales representative's display name for reporting. A representative query follows:

SELECT salesrep_full_name, sales_group_name, work_telephone, email_address
FROM apps.ast_salesrep_lov_uwq_v
WHERE sales_group_name = :p_sales_group
ORDER BY salesrep_last_name;

A second common pattern retrieves representatives belonging to a specific salesforce:

SELECT salesrep_full_name, sales_group_id, employee_person_id
FROM apps.ast_salesrep_lov_uwq_v
WHERE salesforce_id = :p_salesforce_id;

Because the view is already ordered by IEU_LOV_COL2, callers relying on the default LOV ordering need not add their own ORDER BY clause. Access should respect APPS schema security conventions, and, as with any wrapper view, performance is inherited directly from the base object AST_SALESREP_LOV_V.