Search Results pjm_projects_v




Overview
Explore in AI Chat

Overview

APPS.PJM_PROJECTS_V is a Project Manufacturing (PJM) view that presents a consolidated, "All Project / Seiban" list. It is defined as a UNION ALL of two logically distinct sets of records: standard Oracle Projects entries sourced from PA_PROJECTS_EXPEND_V, and Seiban numbers sourced from PJM_SEIBAN_NUMBERS. The view exists so that PJM and manufacturing-related forms, reports, and lookups can query a single row source that returns both project numbers and Seiban numbers in a consistent shape.

Because the source branches expose different native column sets, the view normalizes them by aliasing Seiban columns into project-oriented names. The literal 2 and 1 projected from the two branches populate the SEIBAN_NUMBER_FLAG column, distinguishing standard projects (2) from Seiban numbers (1). This design makes the view suitable for LOV (List of Values) definitions, concurrent program parameters, and reporting queries where the calling process does not need to know in advance whether a given identifier is a project or a Seiban.

Underlying Base Objects

The documented base objects referenced through the view's dependency chain include: PA_PROJECTS_EXPEND_V, PA_PROJECTS_ALL_BASIC_V, PA_PROJECTS_ALL, PA_IMPLEMENTATIONS_ALL, PA_BUDGETARY_CONTROL_OPTIONS, PA_CC_ORG_RELATIONSHIPS, PJM_SEIBAN_NUMBERS, HR_ORGANIZATION_INFORMATION, and the packages PA_SECURITY, PA_PROJECT_UTILS, PA_CROSS_BUSINESS_GRP, and FND_PROFILE.

The first UNION branch reads from PA_PROJECTS_EXPEND_V, an Oracle Projects view that enforces operating-unit and security filtering against PA_PROJECTS_ALL. The second branch reads PJM_SEIBAN_NUMBERS directly. The presence of PA_SECURITY, PA_IMPLEMENTATIONS_ALL, and FND_PROFILE in the dependency list indicates that the project branch inherits standard Projects security, multi-organization, and profile-driven filtering behavior.

Key Columns

  • PROJECT_ID — Surrogate key of the project or Seiban record; used for joins to PJM and Projects tables.
  • PROJECT_NUMBER — The project number for project rows, or the Seiban number for Seiban rows.
  • PROJECT_NAME — Project name, or the Seiban name (the Seiban branch maps PROJECT_NAME into both the name and description positions).
  • PROJECT_DESCRIPTION — Project description for project rows; for Seiban rows this carries the Seiban name.
  • PROJECT_NUMBER_SORT_ORDER — Sort key; Seiban rows use PROJECT_NUMBER here.
  • START_DATE / COMPLETION_DATE — Project dates; both are TO_DATE(NULL) for Seiban rows.
  • SEIBAN_NUMBER_FLAG — Discriminator: 2 for standard projects, 1 for Seiban numbers.
  • OPERATING_UNIT — Operating unit of the record; sourced from P.PROJECT_OU for projects and S.OPERATING_UNIT for Seiban rows.

Common Use Cases and Queries

Typical uses include Seiban-aware LOVs on manufacturing work orders, PJM project selection in discrete manufacturing setups, and reporting that must present projects and Seiban numbers together.

List all entries with type identification:

  • SELECT project_id, project_number, seiban_number_flag, operating_unit FROM apps.pjm_projects_v ORDER BY project_number;

Restrict to Seiban numbers only:

  • SELECT project_id, project_number, operating_unit FROM apps.pjm_projects_v WHERE seiban_number_flag = 1;

Restrict to standard projects within an operating unit:

  • SELECT project_number, project_name, start_date FROM apps.pjm_projects_v WHERE seiban_number_flag = 2 AND operating_unit = :p_org_id;

Because the project branch is security-filtered through PA_SECURITY, results returned depend on the responsibility's operating unit and Projects security profile. The Seiban branch is not equally filtered, so queries that must enforce Projects security should include the flag predicate and additional operating-unit criteria.

Note on the Searched Term

The user searched for pa_projects_expend_v. That object is the Oracle Projects branch of this view, not the view itself. Reference to PJM_PROJECTS_V is appropriate when the requirement is to retrieve both projects and Seiban numbers; if only Projects data is needed, querying PA_PROJECTS_EXPEND_V directly avoids the Seiban UNION overhead.