Search Results project_status




Overview
Explore in AI Chat

Overview

APPS.ICX_EDM_PLANNER_PROJ_V is a reporting view that exposes project information as seen from the perspective of a materials planner. The suffix _V confirms that it is a view rather than a stored table, and the ICX_EDM prefix ties it to the Oracle iProcurement / e-Commerce Gateway "Employee Direct" and planner-oriented self-service flows, where planning and purchasing users need to see the projects against which demand and supply are associated. The view presents a de-normalized, report-friendly result set that joins project master data from Oracle Projects to the organizations, planners, and people that drive discrete manufacturing and purchasing activity.

Its primary role is to answer the question "which projects are my planners actually dealing with?" by correlating three demand/supply sources — purchase order distributions, purchase requisition lines/distributions, and work in process (WIP) discrete jobs — back to PA_PROJECTS_ALL. This makes it useful in Oracle EBS 12.1.1 and 12.2.2 reporting, particularly for OBIEE, Discoverer, and custom concurrent programs that need a consolidated project-plus-planner listing without writing the multi-table join themselves.

Underlying Base Objects

The documented base objects fall into three functional groups. First, the project hierarchy is supplied by PA_PROJECTS_ALL (the project master, providing the project number, name, and description) and PA_PROJECT_STATUSES, which supplies the human-readable status name. Second, the organizational and personnel context comes from HR_ORGANIZATION_UNITS (the carrying-out organization), PER_PEOPLE_F (the planner's person record), and the HR_PERSON_NAME package used to derive the planner's display name. Third, the transactional sources that drive the row set are the purchasing synonyms PO_DISTRIBUTIONS, PO_LINES, PO_REQUISITION_LINES, and PO_REQ_DISTRIBUTIONS, together with WIP_DISCRETE_JOBS, MTL_SYSTEM_ITEMS, and MTL_PLANNERS. The presence of MTL_PLANNERS and MTL_SYSTEM_ITEMS is significant: the view is anchored on planner codes defined on the item master, so it returns projects only where an active planner assignment exists.

Supporting package objects — HR_GENERAL, HR_SECURITY, and PJM_SEIBAN_NUMBERS — are referenced indirectly, typically for security and numbering logic inherited through the underlying synonyms.

Key Columns

Common Use Cases and Queries

Typical uses include planner-facing project listings, project demand reports for purchasing, and validation of project-to-planner assignment coverage. A simple query to list active, non-template projects with their planner and description is:

  • SELECT project_number, project_name, description, organization_name, project_status_name, full_name FROM apps.icx_edm_planner_proj_v WHERE project_status_name = 'Approved' ORDER BY project_number;
  • Filter by planner: SELECT project_number, description FROM apps.icx_edm_planner_proj_v WHERE full_name = :planner_name;
  • Filter by organization: SELECT project_number, project_name, description FROM apps.icx_edm_planner_proj_v WHERE organization_name = :org ORDER BY project_name;

Because the view performs DISTINCT across a multi-branch union, it is best used for reporting rather than high-volume transactional joins; the planner name column is populated via an outer join, so projects whose planner has no person record still appear with a null FULL_NAME.