Search Results salesrep_first_name




Overview
Explore in AI Chat

Overview

APPS.AST_SALESREP_LOV_UWQ_V is a VALID database view owned by the APPS schema in Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It is registered in FND Design Data under the identifier AST.AST_SALESREP_LOV_UWQ_V and is classified internally as an "Internal" view type. The name suffix "UWQ" identifies it as a Universal Work Queue (UWQ) list-of-values source, and the object is intended to supply sales representative selection lists to Oracle Sales Territory Management and related modules rather than to serve as a general-purpose reporting object.

The view presents a flat, denormalized result set combining salesrep identity attributes (full name, last name, first name), organizational sales group membership, employee person identifiers, salesforce identifiers, and contact information. Oracle's standard disclaimer applies: the object is designated Oracle Internal Use Only, and Oracle does not support direct access to application data through it except from standard Oracle Applications programs. The metadata carries the Oracle Proprietary, Confidential Information marking, so consumers should treat the view as an unsupported interface subject to change without notice between patch levels and releases.

Underlying Base Objects

The documented dependency chain is deliberately shallow. APPS.AST_SALESREP_LOV_UWQ_V references exactly one base object: the view APPS.AST_SALESREP_LOV_V. In turn, APPS.AST_SALESREP_LOV_UWQ_V is not referenced by any database object, confirming that it sits at the top of its dependency graph and is not embedded inside other packaged views or materialized objects. This single-level indirection means that the substantive join logic, filtering, and any security predicates are inherited from AST_SALESREP_LOV_V, and that changes to that parent view propagate directly to this one. The columns IEU_LOV_COL1 through IEU_LOV_COL4 are the standard IEU/LOV positional slots used by the Universal Work Queue and Interaction Center list-of-values framework, mapped here to salesrep-oriented display values rather than carrying independent business meaning.

Key Columns

  • SALESREP_FIRST_NAME (VARCHAR2 360) — the given name of the sales representative; this is the column most commonly targeted when users search for "salesrep_first_name".
  • SALESREP_LAST_NAME (VARCHAR2 360) — the representative's family name.
  • SALESREP_FULL_NAME (VARCHAR2 360) — the concatenated display name, typically the value rendered in LOV and picker interfaces.
  • SALES_GROUP_ID (NUMBER) and SALES_GROUP_NAME (VARCHAR2 60) — the sales group (territory or organization unit) to which the representative is assigned.
  • EMPLOYEE_PERSON_ID (NUMBER) — the HR person identifier linking the representative to the PER employee model.
  • SALESFORCE_ID (NUMBER) — the salesforce (resource group) identifier used by territory and quota logic.
  • WORK_TELEPHONE (VARCHAR2 2000) and EMAIL_ADDRESS (VARCHAR2 2000) — contact attributes for the representative.
  • IEU_LOV_COL1–IEU_LOV_COL4 — framework-defined display slots consumed by the UWQ LOV mechanism.

Common Use Cases and Queries

Typical usage is limited to diagnostics, data reconciliation, and controlled extensions that must mirror the values presented in the Universal Work Queue salesrep picker. Because the view enforces no additional predicates of its own, any filtering (active status, territory, organization) must be applied by the consumer or is already embedded in AST_SALESREP_LOV_V.

A representative query retrieving names and contact details:

  • SELECT SALESREP_FULL_NAME, SALESREP_FIRST_NAME, SALESREP_LAST_NAME, EMAIL_ADDRESS, WORK_TELEPHONE FROM APPS.AST_SALESREP_LOV_UWQ_V ORDER BY SALESREP_FULL_NAME;
  • SELECT SALES_GROUP_NAME, SALESREP_FIRST_NAME, SALESREP_LAST_NAME, EMPLOYEE_PERSON_ID FROM APPS.AST_SALESREP_LOV_UWQ_V WHERE SALES_GROUP_ID = :p_group_id;
  • SELECT SALESFORCE_ID, COUNT(*) FROM APPS.AST_SALESREP_LOV_UWQ_V GROUP BY SALESFORCE_ID;
  • SELECT * FROM APPS.AST_SALESREP_LOV_UWQ_V WHERE UPPER(SALESREP_FIRST_NAME) LIKE UPPER(:p_search || '%');

Because the object is unsupported for direct access, production integrations should use supported Oracle APIs or the parent AST_SALESREP_LOV_V contract where an equivalent supported interface exists, and should validate behavior after each application of patches or upgrades.