Results for “pjm_projects_org_ou_v”

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

Overview

APPS.PJM_PROJECTS_ORG_OU_V is a Project Manufacturing (PJM) reporting view that consolidates project definitions with the inventory organization and operating unit context required by Project Manufacturing transactions. It exposes project master attributes alongside the PJM project parameters — costing group and planning group — that drive manufacturing and costing behavior for project-referenced discrete jobs, schedules, and flow schedules. The view is documented as VALID in the APPS schema for release 12.2.2 and inherits the same read-only, reporting-oriented character in 12.1.1, where it is likewise deployed as a seeded APPS view rather than a table maintaining independent data.

Its primary architectural role is to supply a single denormalized row per project per inventory organization, combining the project identity from the expenditure view with HR organization unit naming. Because it joins PJM_PROJECT_PARAMETERS, it is the natural source for reports and concurrent programs that must determine the costing group and planning group assigned to a project within a specific manufacturing organization.

Underlying Base Objects

The documented base objects are PJM_PROJECT_PARAMETERS (synonym), PA_PROJECTS_ALL_EXPEND_V (view), PJM_SEIBAN_NUMBERS (synonym), HR_ALL_ORGANIZATION_UNITS_TL (synonym), and the FND_PROFILE, PA_PROJECT_UTILS, and PA_SECURITY packages. The engine of the view is an inline UNION ALL over two branches. The first branch reads PA_PROJECTS_ALL_EXPEND_V, carrying a hard-coded SEIBAN_NUMBER_FLAG of 2, and supplies ORG_ID and EXPENDITURE_ORG_ID from the projects expenditure view. The second branch reads PJM_SEIBAN_NUMBERS, flagging those rows with a value of 1 and mapping OPERATING_UNIT into ORG_ID, with START_DATE, COMPLETION_DATE, and EXPENDITURE_ORG_ID nulled. The union result is joined to PJM_PROJECT_PARAMETERS on PROJECT_ID to obtain ORGANIZATION_ID, COSTING_GROUP_ID, and PLANNING_GROUP, and is outer-joined to HR_ALL_ORGANIZATION_UNITS_TL on ORG_ID with the user's language, so that the operating unit name resolves without eliminating rows when no translation exists.

Key Columns

• INVENTORY_ORGANIZATION_ID — The PJM organization identifier from PJM_PROJECT_PARAMETERS, establishing which manufacturing organization the project parameters apply to.
• ORG_ID — The operating unit derived from the projects expenditure view (SEIBAN flag 2) or from OPERATING_UNIT in PJM_SEIBAN_NUMBERS (SEIBAN flag 1).
• PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME, PROJECT_DESCRIPTION — Core project identification attributes.
• PROJECT_NUMBER_SORT_ORDER — Sort key for project listings; for Seiban rows the project name is substituted and the project number is used as the sort order.
• PROJECT_OPERATING_UNIT — The organization unit name from HR_ALL_ORGANIZATION_UNITS_TL, resolved in the session language.
• START_DATE, COMPLETION_DATE — Project date range, null for Seiban-sourced rows.
• COST_GROUP_ID, PLANNING_GROUP — PJM costing and planning group assignments used by manufacturing costing and planning logic.

Common Use Cases and Queries

The view is typically queried to present project-to-organization mappings for PJM setup validation, to drive LOVs and reports requiring costing and planning group context, and to reconcile Seiban-numbered projects with standard project definitions. A representative query listing project parameters per organization is:

• SELECT project_number, project_name, inventory_organization_id, cost_group_id, planning_group FROM apps.pjm_projects_org_ou_v WHERE org_id = :p_org_id ORDER BY project_number_sort_order;
• SELECT v.project_number, v.project_operating_unit, v.start_date, v.completion_date FROM apps.pjm_projects_org_ou_v v WHERE v.project_id = :p_project_id;
• SELECT inventory_organization_id, COUNT(*) FROM apps.pjm_projects_org_ou_v GROUP BY inventory_organization_id;

Because PA_SECURITY and FND_PROFILE are referenced, row visibility in downstream project inquiries is governed by the standard project security profile; direct queries against the view should therefore be restricted to reporting and should not be used to infer security-filtered results without applying the same profile logic.