Search Results pjm_projects_all_v




Overview
Explore in AI Chat

Overview

PJM_PROJECTS_ALL_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined in the Project Manufacturing (PJM) product. It exposes an "All Project / Seiban" listing by unioning standard project definitions from Oracle Projects with Seiban numbers maintained in Project Manufacturing. The view serves as a consolidated lookup for reports, forms, and integrations that must reference both ordinary projects and Seiban definitions through a single interface. In EBS 12.1.1 and 12.2.2, the object is documented as VALID and is referenced by PJM functionality that requires a unified list of project and Seiban identifiers.

Underlying Base Objects

The view definition performs a UNION ALL across two sources. The first branch selects from PA_PROJECTS_ALL_BASIC_V, the Oracle Projects basic projects view. The second branch selects from the PJM_SEIBAN_NUMBERS synonym, which resolves to the Seiban numbers table in the PJM schema. Documented referenced base objects also include server-side packages invoked indirectly for security and profile handling: FND_PROFILE, PA_CROSS_BUSINESS_GRP, PA_PROJECT_UTILS, and PA_SECURITY. PA_PROJECTS_ALL_BASIC_V is the same view used elsewhere in Oracle Projects to expose project header data subject to operational unit and security filtering; because the returned rows depend on PA_SECURITY and cross-business-group logic, both projects and Seiban numbers are effectively presented under Projects security constraints. The SEIBAN_NUMBER_FLAG literal distinguishes the two row sources: a value of 2 identifies standard projects and a value of 1 identifies Seiban numbers.

Key Columns

  • PROJECT_ID — Surrogate key carried through from PA_PROJECTS_ALL_BASIC_V for projects and from PJM_SEIBAN_NUMBERS for Seiban records.
  • PROJECT_NUMBER — Project number for the project branch; for Seiban rows this column carries the Seiban number value.
  • PROJECT_NAME — Project name for standard projects; for Seiban rows the Seiban name.
  • PROJECT_DESCRIPTION — Project description; for Seiban records the same name value is returned in both name and description positions.
  • PROJECT_NUMBER_SORT_ORDER — Sort key, taken from the project number for projects and from the Seiban number for Seiban records.
  • START_DATE and COMPLETION_DATE — Project dates for standard projects; both return TO_DATE(NULL) for Seiban entries, which carry no schedule data.
  • SEIBAN_NUMBER_FLAG — Discriminator column: 2 for projects, 1 for Seiban numbers.
  • OPERATING_UNIT — Carries ORG_ID for projects and OPERATING_UNIT for Seiban rows, providing the organization context used for security and reporting.

Common Use Cases and Queries

The view is commonly used in reports and validation queries where Project Manufacturing must present a combined list of projects and Seiban numbers. A typical listing query follows:

  • SELECT PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME, SEIBAN_NUMBER_FLAG FROM APPS.PJM_PROJECTS_ALL_V WHERE SEIBAN_NUMBER_FLAG = 1; — retrieves only Seiban entries.
  • SELECT PROJECT_NUMBER, PROJECT_NAME, START_DATE, COMPLETION_DATE FROM APPS.PJM_PROJECTS_ALL_V WHERE SEIBAN_NUMBER_FLAG = 2; — retrieves standard project rows with schedule data.
  • SELECT PROJECT_NUMBER, PROJECT_NAME FROM APPS.PJM_PROJECTS_ALL_V WHERE PROJECT_NUMBER_SORT_ORDER LIKE :search || '%' ORDER BY PROJECT_NUMBER_SORT_ORDER; — supports value-set style search of the combined list.

Because project rows are sourced through PA_PROJECTS_ALL_BASIC_V, results are subject to the security profiles and cross-business-group rules implemented by PA_SECURITY and related packages; Seiban rows are therefore exposed alongside projects but remain distinguishable through SEIBAN_NUMBER_FLAG. When querying from a reporting tool, the view may be joined to PJM_SEIBAN_NUMBERS on PROJECT_ID to recover Seiban-specific attributes, and to standard project tables for project rows.