Search Results pjm_org_projects_v




Overview
Explore in AI Chat

Overview

The view APPS.PJM_ORG_PROJECTS_V is a Project Manufacturing (PJM) reporting and integration object that exposes project and Seiban records which have been explicitly enabled for Project Manufacturing processing. It is owned by the APPS schema and holds VALID status in Oracle E-Business Suite releases 12.1.1 and 12.2.2. The view is documented in ETRM as the "Project Manufacturing enabled Project / Seiban view," and its primary function is to restrict the broader project master data set down to only those projects that carry an active Project Manufacturing configuration record.

The view therefore acts as the authoritative inventory of PM-enabled projects for module-level reporting, concurrent processing, and integration touchpoints. Because it derives its row set from a security-aware project view and applies an enablement filter, it serves as a convenient, pre-joined source for forms, reports, and downstream interfaces that must never surface a project not configured for Project Manufacturing.

Underlying Base Objects

The view text selects from PJM_PROJECTS_V P and applies an EXISTS predicate against PJM_PROJECT_PARAMETERS on matching PROJECT_ID. The documented referenced base objects are:

  • PJM_PROJECTS_V (VIEW) — the secure project source from which all columns are projected.
  • PJM_PROJECT_PARAMETERS (SYNONYM) — supplies the enablement rows; only projects with a parameter record are returned.
  • MRP_GET_PROJECT (PACKAGE) — invoked as MRP_GET_PROJECT.PLANNING_GROUP(P.PROJECT_ID) to derive the PLANNING_GROUP value.
  • FND_PROFILE (PACKAGE) — used for profile-option evaluation, including org and security context.
  • PA_CROSS_BUSINESS_GRP, PA_PROJECT_UTILS, PA_SECURITY (PACKAGES) — supply cross-business-group, project utility, and security logic inherited through PJM_PROJECTS_V.

Because the view is defined over PJM_PROJECTS_V, it inherits the operating-unit and security filtering enforced by the PA security packages. The EXISTS clause is correlated rather than joined, so the view returns exactly one row per enabled project regardless of how many parameter rows exist.

Key Columns

  • PROJECT_ID — the internal unique identifier of the project/Seiban; the join key to PJM and PA tables.
  • PROJECT_NUMBER — the user-facing project or Seiban number.
  • PROJECT_NAME — the descriptive project name.
  • PROJECT_DESCRIPTION — free-text description of the project.
  • START_DATE — the project start date.
  • COMPLETION_DATE — the planned completion date.
  • PROJECT_NUMBER_SORT_ORDER — a sortable representation of the project number, useful for ordered reporting.
  • PLANNING_GROUP — the planning group returned by MRP_GET_PROJECT.PLANNING_GROUP, used to group PM-enabled projects for planning purposes.

Common Use Cases and Queries

Typical uses include validating that a project may be referenced on Project Manufacturing transactions, driving LOVs in custom forms, and feeding planning extracts with the correct group assignment. A basic listing is:

  • SELECT project_id, project_number, project_name, planning_group FROM pjm_org_projects_v ORDER BY project_number_sort_order;
  • SELECT project_number, start_date, completion_date FROM pjm_org_projects_v WHERE completion_date IS NULL OR completion_date >= SYSDATE;
  • SELECT planning_group, COUNT(*) FROM pjm_org_projects_v GROUP BY planning_group;

The view supports reporting on active PM-enabled projects and is frequently joined to PJM and PA transaction tables on PROJECT_ID. Note that row visibility remains subject to the PA security and profile logic embedded in PJM_PROJECTS_V, so results are operating-unit dependent.