Search Results icx_edm_key_member_task_v




Overview
Explore in AI Chat

Overview

ICX_EDM_KEY_MEMBER_TASK_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ICX (Oracle iProcurement) product family. Its documented description is "Task Information Summary View by Key Member," and it functions as a denormalized projection that combines project task attributes with the identity of key members assigned to those tasks. Rather than requiring callers to join PA_TASKS, PA_PROJECTS_ALL, PA_PROJECT_PLAYERS, and the HR people views independently, the view exposes a single flattened row per task-to-key-member combination, which is a common shape for iProcurement and self-service pages that must present task context to end users without exposing the underlying Oracle Projects schema.

The view carries a status of VALID and is present in both 12.1.1 and 12.2.2. Because it is a view rather than a table, it stores no data of its own; all values are resolved at query time from the referenced objects, and any change to those base objects propagates automatically. This makes it appropriate for ad hoc reporting, concurrent program extracts, and integration queries, but it also means query cost is driven entirely by the underlying joins.

Underlying Base Objects

The documented referenced base objects are: HR_GENERAL (package), HR_LOCATIONS (view), HR_ORGANIZATION_UNITS (view), HR_PERSON_NAME (package), HR_SECURITY (package), PA_PROJECTS_ALL (synonym), PA_PROJECT_PLAYERS (view), PA_TASKS (synonym), and PER_PEOPLE_F (view). The SELECT text joins PA_TASKS to PA_PROJECT_PLAYERS on PROJECT_ID, then to PA_PROJECTS_ALL on PROJECT_ID, and to the person record via PLAYER.PERSON_ID. The people side is joined twice against PER_PEOPLE_F — once aliased PEOP for the task manager and once aliased KMEM for the key member — with the task manager join expressed as an outer join (PEOP.PERSON_ID(+) = TASK.TASK_MANAGER_PERSON_ID). Task organization data is obtained from HR_ORGANIZATION_UNITS, and location details from HR_LOCATIONS through an outer join on ORG.LOCATION_ID. HR_PERSON_NAME and HR_GENERAL supply the formatted name logic, while HR_SECURITY participates in the security predicate.

The view text also embeds an operating unit predicate that reads the CLIENT_INFO value set by FND_GLOBAL and compares it to NVL(PROJ.ORG_ID, -99), restricting rows to the caller's current operating unit context. Queries executed outside a properly initialized EBS session — for example, from a plain SQL client without CLIENT_INFO set — will not return the expected rows.

Key Columns

The projected columns fall into four groups. Task identity and attributes are represented by TASK_ID, TASK_NUMBER, TASK_NAME, TASK_DESCRIPTION, TASK_MANAGER, TASK_START_DATE, and the column most frequently searched, TASK_END_DATE, which maps to PA_TASKS.COMPLETION_DATE and therefore reflects the planned or actual task completion date depending on how the task was defined. Project context is provided by PROJECT_ID, PROJECT_NUMBER (PROJ.SEGMENT1), PROJECT_NAME, and PROJECT_DESCRIPTION. Organizational context is supplied by TASK_ORGANIZATION, TASK_ORGANIZATION_ID (mapped from CARRYING_OUT_ORGANIZATION_ID), TASK_LOCATION, and TASK_LOCATION_DESCRIPTION. Finally, the key member dimension is exposed through KEY_MEMBER_ID (PLAYER.PERSON_ID) and KEY_MEMBER_NAME. Note that the view uses DISTINCT, so duplicate task-member pairings produced by the join are collapsed.

Common Use Cases and Queries

Typical uses include listing active tasks per key member, reconciling tasks nearing completion, and driving iProcurement approval or assignment logic. A representative query filters on the completion date:

  • SELECT task_number, task_name, key_member_name, task_start_date, task_end_date FROM apps.icx_edm_key_member_task_v WHERE task_end_date BETWEEN :p_from AND :p_to ORDER BY task_end_date;
  • SELECT key_member_id, key_member_name, COUNT(*) task_count FROM apps.icx_edm_key_member_task_v GROUP BY key_member_id, key_member_name;
  • SELECT p.project_number, v.task_name, v.task_manager, v.task_end_date FROM apps.icx_edm_key_member_task_v v, apps.pa_projects_all p WHERE v.project_id = p.project_id AND v.task_end_date < SYSDATE AND v.task_end_date IS NOT NULL;

Because TASK_END_DATE originates in PA_TASKS.COMPLETION_DATE, it is nullable; filters should account for NULL values explicitly. All queries should be run from within an initialized EBS session so that the CLIENT_INFO operating unit predicate resolves correctly.