Results for “task_end_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ICX_EDM_PLANNER_TASK_V is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is part of the ICX product family, which covers Oracle iProcurement and related supplier-facing self-service modules. As its description indicates, the view presents a "Task Information Summary View by Planner," consolidating task-level information across purchasing, projects, inventory planning, and manufacturing execution into a single denormalized result set.

The view serves reporting and integration purposes in EBS. Because it joins task data from the Projects module (PA_TASKS, PA_PROJECTS_ALL) with procurement distributions (PO_DISTRIBUTIONS, PO_LINES), inventory planner assignments (MTL_PLANNERS, MTL_SYSTEM_ITEMS), and human resources records (PER_PEOPLE_F, HR_ORGANIZATION_UNITS, HR_LOCATIONS), it enables planners and procurement analysts to see which tasks are associated with purchased items or discrete jobs, who manages each task, and which organization and location are responsible for carrying it out. It is typically consumed through the EDM (Enterprise Data Management) planning flows that surface planner-centric task summaries.

Underlying Base Objects

The view is defined as a UNION of two SELECT statements. The first query drives off PO_DISTRIBUTIONS and PO_LINES (synonyms to the purchasing tables), joined to MTL_SYSTEM_ITEMS and MTL_PLANNERS through the planner code and organization ID, and to PA_TASKS and PA_PROJECTS_ALL through the project and task identifiers. The second query drives off WIP_DISCRETE_JOBS for manufacturing tasks, with the same MTL, PA, and HR joins.

Person and organization name resolution relies on PER_PEOPLE_F, exposed as TASK_MANAGER and via PLANEMP for the planner's full name. Supporting objects include HR_ORGANIZATION_UNITS and HR_LOCATIONS for organizational and location detail, and the HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages that handle name formatting and security predicates at runtime. The documented dependency list also references PO_REQUISITION_LINES and PO_REQ_DISTRIBUTIONS, which support related planning flows. As PER_PEOPLE_F is a date-tracked (effective-dated) view, joins against it should account for current effective rows.

Key Columns

• TASK_ID, TASK_NUMBER, TASK_NAME, DESCRIPTION — identity and descriptive attributes of the project task.
• TASK_MANAGER — full name of the person managing the task, resolved from PER_PEOPLE_F.
• START_DATE, COMPLETION_DATE — task scheduling dates.
• TASK_ORGANIZATION, TASK_ORGANIZATION_ID — carrying-out organization name and identifier.
• TASK_LOCATION, TASK_LOCATION_DESCRIPTION — location code and description for the responsible organization.
• PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME — the project to which the task belongs.
• PLANNER_EMPLOYEE_ID, PLANEMP.FULL_NAME — planner identity derived from MTL_PLANNERS and resolved to a person name.

Common Use Cases and Queries

Typical scenarios include planner workload reporting, task-to-purchase reconciliation, and cross-referencing manufacturing jobs with project tasks. A basic query filtered by planner name might read:

SELECT task_number, task_name, task_manager, project_number, task_organization
FROM apps.icx_edm_planner_task_v
WHERE full_name = :planner_name
ORDER BY project_number, task_number;

Analysts frequently filter on TASK_ORGANIZATION_ID or PROJECT_ID to isolate a business unit, and join the view to PER_PEOPLE_F or HR tables for additional person attributes. Because the view is a UNION, DISTINCT is applied to both branches, making it safe for set-based reporting but relatively costly on large datasets; restricting by planner, organization, or project is advisable.