Search Results source_email

Overview

The IEU_WP_TASK_OWNR_LOV_V view is a documented Oracle E-Business Suite database object owned by the APPS schema within the IEU (Universal Work Queue) product family. It is a reporting and integration-oriented view that supplies a resource list for task owners and assignees. In the Oracle EBS 12.1.1 and 12.2.2 environments, this view supports the Universal Work Queue Worklist functionality by presenting a unified list of valid resources that can be selected as a task owner or assignee through a List of Values (LOV) mechanism. The view consolidates employee resources and resource groups into a single, consistently formatted result set, allowing the Work Queue application tier and any downstream reporting or integration components to retrieve assignable resources in a normalized shape.

The naming convention reflects its purpose: IEU_LOV_COL1 through IEU_LOV_COL4 are LOV display columns expected by the Universal Work Queue UI components. This design is characteristic of EBS LOV views, which present a small, fixed column set that the framework can bind to selection dialogs.

Underlying Base Objects

According to the documented ETRM metadata, the view is defined over two referenced base objects, both of which are themselves views:

• JTF_RS_RESOURCE_EXTNS_VL — the resource extensions view, supplying employee resources where CATEGORY = 'EMPLOYEE'. It provides RESOURCE_ID, RESOURCE_NUMBER, RESOURCE_NAME, SOURCE_EMAIL, SOURCE_PHONE, and the active date range columns.
• JTF_RS_GROUPS_VL — the resource groups view, supplying group-based assignable resources. It provides GROUP_ID, GROUP_NUMBER, GROUP_NAME, EMAIL_ADDRESS, and the active date range columns. Phone is represented as NULL for groups.

These two sources are combined with a UNION ALL, and each branch is filtered by active-date logic: TRUNC(SYSDATE) >= NVL(START_DATE_ACTIVE, TRUNC(SYSDATE)) and TRUNC(SYSDATE) <= NVL(END_DATE_ACTIVE, TRUNC(SYSDATE)). This ensures only currently effective resources are returned. The final projection is ordered by RESOURCE_NAME, RESOURCE_TYPE.

Key Columns

• IEU_LOV_COL1 — the resource name, derived from RESOURCE_NAME. This is the primary display value in the LOV.
• IEU_LOV_COL2 — the resource name concatenated with the resource type in brackets, for example SMITH, JOHN [RS_EMPLOYEE] or SUPPORT TEAM [RS_GROUP]. This is the column most commonly referenced in the context of the search term ieu_lov_col2, since it disambiguates resources of the same name by type.
• IEU_LOV_COL3 — the resource identifier concatenated with the resource type, for example 1234[RS_EMPLOYEE]. This provides a composite key-style display.
• IEU_LOV_COL4 — the resource number concatenated with the resource type.

Internally the inline view also exposes RESOURCE_ID, RESOURCE_NUMBER, RESOURCE_TYPE (values RS_EMPLOYEE or RS_GROUP), EMAIL, START_DATE_ACTIVE, END_DATE_ACTIVE, and PHONE.

Common Use Cases and Queries

Typical uses include populating LOVs for task owner and assignee selection in Universal Work Queue, validating that a chosen resource is currently active, and driving reports that list available assignees. A representative query is:

SELECT ieu_lov_col1, ieu_lov_col2 FROM apps.ieu_wp_task_ownr_lov_v ORDER BY ieu_lov_col1;

To distinguish employee versus group resources, filter on the type embedded in column 2:

SELECT * FROM apps.ieu_wp_task_ownr_lov_v WHERE ieu_lov_col2 LIKE '%[RS_GROUP]%';