Search Results project_category




Overview
Explore in AI Chat

Overview

APPS.ICX_EDM_KEY_MEMBER_PROJ_V is an Oracle E-Business Suite reporting view that exposes the relationship between projects and their designated key members. In the EBS 12.1.1 and 12.2.2 releases, this view belongs to the ICX (Oracle iSupport / Interaction Center) and EDM (Enterprise Data Management) functional area, and it is designed to flatten project header attributes with the person-level records held in the Oracle Projects module. It presents the combination of a project, its key member person, the carrying-out organization, and the project status in a single denormalized result set suitable for direct reporting or integration consumption.

The view is a read-only, DISTINCT-based query, which means downstream consumers can rely on it to return one row per unique project and key member combination without having to write the join logic themselves. Because it is owned by APPS, it is accessible to any responsibility or concurrent program that connects with the APPS schema, which is typical for Oracle EBS reporting views of this type.

Underlying Base Objects

The documented base objects referenced by this view are:

  • PA_PROJECT_PLAYERS (VIEW) — provides the player and key member relationship to the project.
  • PA_PROJECTS_ALL (SYNONYM) — the project master, supplying number, name, description, type, status code, start date, and completion date.
  • PER_PEOPLE_F (VIEW) — the effective-dated person record, used to resolve the key member full name and person ID.
  • HR_ORGANIZATION_UNITS (VIEW) — resolves the carrying-out organization name.
  • PA_PROJECT_STATUSES (SYNONYM) — provides the descriptive project status name.
  • HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY (PACKAGE) — supporting HR infrastructure, typically used for name formatting and security-based row filtering.

The joins are driven from PA_PROJECT_PLAYERS to PA_PROJECTS_ALL on PROJECT_ID, to PER_PEOPLE_F on PERSON_ID, to HR_ORGANIZATION_UNITS on CARRYING_OUT_ORGANIZATION_ID, and to PA_PROJECT_STATUSES on PROJECT_STATUS_CODE. Template projects are excluded through the predicate PROJ.TEMPLATE_FLAG != 'Y'.

Key Columns

Two columns are explicitly defined as NULL in the view text; these are placeholders reserved for downstream EDM consumption and carry no value in the base definition.

Common Use Cases and Queries

Typical scenarios include project key-member rosters, organizational project reporting, and data extraction into external systems. A representative query follows:

  • SELECT PROJECT_NUMBER, PROJECT_NAME, PROJECT_STATUS_NAME, KEY_MEMBER_NAME, ORGANIZATION_NAME FROM APPS.ICX_EDM_KEY_MEMBER_PROJ_V WHERE PROJECT_ID = :p_project_id;
  • SELECT ORGANIZATION_NAME, COUNT(DISTINCT PROJECT_ID) FROM APPS.ICX_EDM_KEY_MEMBER_PROJ_V GROUP BY ORGANIZATION_NAME;
  • SELECT KEY_MEMBER_NAME, PROJECT_NUMBER FROM APPS.ICX_EDM_KEY_MEMBER_PROJ_V WHERE PROJECT_STATUS_NAME = 'Approved';

Because the view relies on HR_SECURITY, row visibility can be constrained by the HR security profile in force at runtime.