Search Results icx_edm_planner_proj_v




Overview
Explore in AI Chat

Overview

ICX_EDM_PLANNER_PROJ_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the ICX product family, Oracle iProcurement, and is described in the ETRM repository as a "Project Information Summary View by Planner." The view consolidates project attributes alongside the materials planner responsible for the items consumed against those projects, producing a planner-centric projection of project activity.

The object derives its importance from its role in Oracle iProcurement and procurement-related reporting, where planners require visibility across purchase order distributions and discrete manufacturing jobs in order to reconcile demand with project execution. Rather than querying PA_PROJECTS_ALL, PO_DISTRIBUTIONS, and WIP_DISCRETE_JOBS independently, consumers of this view obtain a unified result set that joins project identifiers, organization context, project status, and planner identity in a single access path.

Because the view is defined with UNION and UNION ALL semantics across two distinct sources of project activity, it serves as a reporting bridge between the purchasing and manufacturing domains. This makes it useful for dashboards, custom concurrent programs, and ad hoc SQL used by planning and procurement analysts.

Underlying Base Objects

The view is defined over a documented set of base objects recorded in the ETRM 12.2.2 metadata. These include:

  • PO_DISTRIBUTIONS and PO_LINES — supply the purchasing-side project linkage and item identifiers.
  • WIP_DISCRETE_JOBS — supplies the manufacturing-side project linkage.
  • MTL_SYSTEM_ITEMS and MTL_PLANNERS — associate inventory items with their assigned planner, including planner code and organization.
  • PA_PROJECTS_ALL — provides project number, name, description, type, status, and start/completion dates.
  • PA_PROJECT_STATUSES — resolves the project status code to a user-facing status name.
  • HR_ORGANIZATION_UNITS — supplies the carrying-out organization name.
  • PER_PEOPLE_F, HR_PERSON_NAME, HR_GENERAL, HR_SECURITY — resolve the planner employee's full name and enforce HR security.

Additional referenced objects include PO_REQUISITION_LINES, PO_REQ_DISTRIBUTIONS, and PJM_SEIBAN_NUMBERS, reflecting the broader requisition and project-numbering context that ETRM documents for this view.

Key Columns

Common Use Cases and Queries

Typical uses include identifying which planner owns items tied to a project, reviewing project status and completion dates, and cross-checking PO versus WIP activity for the same project. A representative query filtering on the project end date is:

  • SELECT project_id, project_number, project_name, organization_name, project_status_name, planner_employee_id, full_name FROM apps.icx_edm_planner_proj_v WHERE completion_date >= SYSDATE ORDER BY completion_date;
  • Planner-specific filtering via WHERE employee_id = :planner_id.
  • Status-driven reporting via WHERE project_status_code = 'APPROVED'.

Because the view applies HR security packages, results may be constrained by the responsibility's security profile for the planner's person record.