Results for “project_start_date”

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

Overview

The APPS.ICX_EDM_KEY_MEMBER_PROJ_V view is a reporting object within the Oracle iProcurement (ICX) module of Oracle E-Business Suite. It presents a consolidated "Project Information Summary by Key Member," joining project master data with the persons designated as project players and the organizations that carry out the project. The view is part of the EDM (Enterprise Data Management) family of views used by iProcurement to surface descriptive and status information about projects during requisition entry, shopping, and related purchasing flows. It is documented as VALID and owned by the APPS schema in both EBS 12.1.1 and 12.2.2.

The view is primarily a descriptive lookup rather than a transactional object. It exposes project identity, organization, type, status, dates, and key member identity so that iProcurement screens and downstream integrations can render meaningful project context without querying the underlying PA and HR tables directly. Because project and member data change frequently, the view is queried at runtime rather than being materialized.

Underlying Base Objects

The view is defined over several base objects across the Projects (PA), Human Resources (HR), and PeopleSoft-derived (PER) schemas:

• PA_PROJECTS_ALL — the master project table, supplying project number, name, description, type, status code, carrying-out organization, and start/completion dates. The view filters out project templates (TEMPLATE_FLAG != 'Y').
• PA_PROJECT_PLAYERS — the association between projects and the persons assigned to them (players). This drives the "by Key Member" grain of the view.
• PER_PEOPLE_F — the date-effective person records providing KEY_MEMBER_NAME via FULL_NAME.
• HR_ORGANIZATION_UNITS — supplies the carrying-out organization name.
• PA_PROJECT_STATUSES — supplies the descriptive project status name.
• HR_GENERAL, HR_SECURITY, HR_PERSON_NAME — HR packages referenced for name formatting and security enforcement.

The join condition couples PROJ.PROJECT_ID to PLAYER.PROJECT_ID and PLAYER.PERSON_ID to KMEM.PERSON_ID, with DISTINCT applied to collapse duplicate player rows.

Key Columns

• PROJECT_ID — surrogate key identifying the project.
• PROJECT_NUMBER / PROJECT_NAME — human-readable project identifiers.
• PROJECT_STATUS / STATUS_DSP — the raw status code and its display status. The STATUS_DSP column is the user-facing status name (mapped from PA_PROJECT_STATUSES.PROJECT_STATUS_NAME) and is the column most relevant to searches for "status_dsp."
• PROJECT_ORGANIZATION_ID / PROJECT_ORGANIZATION — carrying-out organization identifier and name.
• PROJECT_TYPE — classification of the project.
• PROJECT_START_DATE / PROJECT_END_DATE — project timeline.
• KEY_MEMBER_ID / KEY_MEMBER_NAME — the person associated with the project as a player.

Several columns in the view SELECT list, such as PROJECT_CATEGORY and LAST_ACCUMULATED_PERIOD, are output as NULL placeholders, indicating they are reserved for display columns but not populated by the current join.

Common Use Cases and Queries

Typical usage centers on presenting project and status information to iProcurement users and to integrations that need project status and owner context. A representative query filtering on the display status is:

• SELECT project_number, project_name, key_member_name, status_dsp, project_start_date FROM apps.icx_edm_key_member_proj_v WHERE status_dsp = 'Approved';
• Restricting to a single key member: ... WHERE key_member_id = :person_id;
• Restricting to an organization: ... WHERE project_organization_id = :org_id;

Because the view already applies DISTINCT and filters template projects, callers do not need to repeat those predicates. It is most valuable where a concise, member-oriented project status lookup is required rather than full project accounting detail.