Results for “icx_edm_project_v”

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

Overview

ICX_EDM_PROJECT_V is a validity-verified APPS-owned database view that presents a consolidated project information summary for Oracle iProcurement (product family ICX) in Oracle E-Business Suite 12.1.1 and 12.2.2. The view is defined in the APPS schema and its function is to expose project header attributes needed by iProcurement's external data management and project-charging flows, so that self-service purchasing, requisition entry, and shopping cart interfaces can validate or display the projects to which requisitions and purchase orders may be charged. It is a read-only reporting and integration object; no DML is supported against it, and integrity is delegated entirely to the underlying sources.

The column list includes a LAST_ACCUMULATED_PERIOD attribute. This name corresponds to the keyword "last_accumulated_period" for which the object was retrieved. LAST_ACCUMULATED_PERIOD is populated only from the second branch of the view, derived from PJM_SEIBAN_NUMBERS, and is returned as a NULL character value for all rows originating from PA_PROJECTS_ALL.

Underlying Base Objects

The documented metadata lists six referenced objects: HR_GENERAL (package), HR_ORGANIZATION_UNITS (view), HR_SECURITY (package), PA_PROJECTS_ALL (synonym), PA_PROJECT_STATUSES (synonym), and PJM_SEIBAN_NUMBERS (synonym). The view SQL is a UNION of two SELECT branches.

• First branch: Joins PA_PROJECTS_ALL (alias PROJ) to HR_ORGANIZATION_UNITS (alias ORG) and PA_PROJECT_STATUSES (alias PS). The join to ORG is an outer join on CARRYING_OUT_ORGANIZATION_ID; template projects are excluded via TEMPLATE_FLAG != 'Y'; the status join is on PROJECT_STATUS_CODE.
• Second branch: Sources PJM_SEIBAN_NUMBERS (alias SEIB) with an outer join to HR_ORGANIZATION_UNITS, exposing "SEIBAN" projects that do not reside in PA_PROJECTS_ALL.
• Security: HR_GENERAL and HR_SECURITY supply the organization security predicates used within HR_ORGANIZATION_UNITS, ensuring rows respect the operating unit and organization hierarchy of the querying user.

Key Columns

• PROJECT_ID — Project identifier; the primary key value from PA_PROJECTS_ALL or PJM_SEIBAN_NUMBERS.
• PROJECT_NUMBER — Project number (SEGMENT1 for PA projects; PROJECT_NUMBER for SEIBAN projects).
• NAME — Project name; for SEIBAN rows both NAME and DESCRIPTION are populated from PROJECT_NAME.
• DESCRIPTION — Project description.
• ORGANIZATION_ID / ORGANIZATION_NAME — Carrying-out organization (OPERATING_UNIT for SEIBAN) and its HR organization name.
• CATEGORY / TYPE — Category is returned NULL; TYPE exposes PROJECT_TYPE from PA_PROJECTS_ALL and NULL as TO_CHAR(NULL) for SEIBAN rows.
• STATUS / STATUS_DSP — Status code and its translated status name.
• START_DATE / END_DATE — Project start and completion dates; NULL for SEIBAN rows.
• LAST_ACCUMULATED_PERIOD — Populated only from PJM_SEIBAN_NUMBERS; NULL for PA-project rows.

Common Use Cases and Queries

Typical uses include populating project-charging lists in iProcurement, filtering active projects for requisition distribution, and joining project identifiers to purchasing or expenditure data. A basic lookup by project number:

• SELECT project_id, project_number, name, status_dsp, last_accumulated_period
• FROM icx_edm_project_v
• WHERE project_number = :p_number
• AND status = 'APPROVED';

To isolate projects with an accumulated period value:

• SELECT project_id, project_number, name, organization_name, last_accumulated_period
• FROM icx_edm_project_v
• WHERE last_accumulated_period IS NOT NULL;

The view should be queried rather than sourced for DML, and performance depends on the selectivity of PA_PROJECTS_ALL and PJM_SEIBAN_NUMBERS and on the organization security applied through HR_ORGANIZATION_UNITS.