Search Results project_status

Overview

PJM_PROJECT_PROJ_V is a consolidated inquiry view owned by the APPS schema within the Project Manufacturing (PJM) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to combine project and seiban information for the Project Manufacturing Web Inquiry, presenting a single result set that spans standard Oracle Projects records and PJM seiban numbers. The view is an operational reporting and integration artifact rather than a transactional entity; it is queried by the Web Inquiry user interface and can be reused by custom reports, concurrent programs, and interface extracts that require a unified project/seiban listing.

The view's relevance to the search term "project_organization_name" is direct: the column PROJECT_ORGANIZATION_NAME is exposed by this view and resolves the organization identifier associated with each project or seiban to its translated organization name. In practice this is the field users locate when they need to identify the carrying-out organization of a project or the operating unit of a seiban in a readable form.

Underlying Base Objects

The documented ETRM metadata for release 12.2.2 lists the referenced base objects as HR_ALL_ORGANIZATION_UNITS_TL (synonym), PA_PROJECT_PLAYERS (view), PA_PROJECT_STATUSES (synonym), PER_ALL_PEOPLE_F (synonym), and PJM_PROJECTS_ALL_OU_V (view). The view text archived in the documentation shows a UNION ALL construction joining PA_PROJECTS_ALL_BASIC_V, HR_ALL_ORGANIZATION_UNITS_TL, and PA_PROJECT_STATUSES in the first branch, and PJM_SEIBAN_NUMBERS with HR_ALL_ORGANIZATION_UNITS_TL in the second branch.

• The project branch draws project identifiers, number, name, description, dates, status code, type, and the carrying-out organization identifier from the project view, joins status names from PA_PROJECT_STATUSES, and resolves the organization name from HR_ALL_ORGANIZATION_UNITS_TL.
• The seiban branch draws project identifier, number, and name from PJM_SEIBAN_NUMBERS, supplies NULL literals for the project-only date/status/type attributes, and takes the operating unit as the organization identifier, again resolving the name through HR_ALL_ORGANIZATION_UNITS_TL.
• Organization joins are outer joins keyed on organization identifier with a language restriction against USERENV('LANG'), which ensures the translated organization name is returned in the session's language.

The presence of PA_PROJECT_PLAYERS, PER_ALL_PEOPLE_F, and PJM_PROJECTS_ALL_OU_V in the documented reference list indicates that the deployed view definition in 12.2.2 is broader than the historical excerpt, likely reflecting project-manager or organization-unit derivation used by the Web Inquiry.

Key Columns

• PROJECT_ID — Internal identifier of the project, or the seiban project identifier for seiban rows; the primary join key back to Oracle Projects.
• PROJECT_NUMBER — User-facing project or seiban number.
• PROJECT_NAME — Project name; the seiban branch supplies the seiban name here as well.
• PROJECT_DESCRIPTION — Description in the project branch; the seiban branch substitutes the seiban name.
• START_DATE / COMPLETION_DATE — Project schedule dates; NULL for seiban rows.
• PROJECT_STATUS — Translated project status name from PA_PROJECT_STATUSES; NULL for seiban rows.
• PROJECT_TYPE — Project type classification; NULL for seiban rows.
• PROJECT_ORGANIZATION_ID — Carrying-out organization for projects, operating unit for seibans.
• PROJECT_ORGANIZATION_NAME — Translated organization name from HR_ALL_ORGANIZATION_UNITS_TL; the attribute most commonly searched by users.

Common Use Cases and Queries

Typical uses include Web Inquiry display, listing projects and seibans with their responsible organization, filtering by organization name for responsibility-level reporting, and feeding downstream extracts that require a normalized project/seiban key set. The following sample returns the core attributes for projects handled by a specific organization:

• SELECT project_id, project_number, project_name, project_status, project_organization_name FROM apps.pjm_project_proj_v WHERE project_organization_name = :org_name ORDER BY project_number;
• SELECT project_number, project_name, project_organization_id FROM apps.pjm_project_proj_v WHERE project_id = :project_id;
• SELECT p.project_number, p.project_organization_name FROM apps.pjm_project_proj_v p WHERE p.project_status = 'APPROVED' AND p.start_date >= :from_date;

Because the view is a UNION ALL of two heterogeneous sources, consumers should treat NULL status, type, and date values as indicators of seiban rows rather than missing project data, and should apply organization-name filters with awareness of the session language dependency introduced by the USERENV('LANG') predicate.