Search Results pjm_org_parameters_v




Overview
Explore in AI Chat

Overview

PJM_ORG_PARAMETERS_V is an APPS-owned view in the Oracle E-Business Suite Project Manufacturing (PJM) module. It exposes organization-level Project Manufacturing parameters stored in the PJM_ORG_PARAMETERS table, joined to the common project definition in PA_PROJECTS_ALL. In 12.1.1 and 12.2.2 the view remains a read-only, reporting-oriented presentation layer over these configuration settings, allowing users and integrators to query the manufacturing parameters that govern how Project Manufacturing organizations handle project references, project control, cost transfers, and variance accounting.

The view plays a central role in reporting and integration because it consolidates both the parameter record itself and the derived common project number. This makes it convenient for responsibility-level inquiries, concurrent-program validation, and external system extracts where the numeric COMMON_PROJECT_ID alone would require a further join. Because the view is a simple projection with an outer join to PA_PROJECTS_ALL, it is stable, low-overhead, and suitable for embedded subqueries in larger reporting SQL.

Underlying Base Objects

The documented base objects are PJM_ORG_PARAMETERS (a synonym) and PA_PROJECTS_ALL (a synonym). The view is defined with an outer join, expressed as P.PROJECT_ID (+) = POP.COMMON_PROJECT_ID, so every row in PJM_ORG_PARAMETERS is returned even when no common project is defined. The view selects POP.ROWID as ROW_ID along with audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), the organization identifier, all parameter flags and expenditure-type mappings, descriptive flexfield columns ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY, and P.SEGMENT1 projected as COMMON_PROJECT_NUMBER from PA_PROJECTS_ALL.

Because the outer table PJM_ORG_PARAMETERS is keyed by ORGANIZATION_ID, the view yields at most one parameter row per inventory organization, with the optional common project attributes appended. PA_PROJECTS_ALL supplies the project number used when a common project is configured.

Key Columns

Common Use Cases and Queries

Typical usages include validating that a Project Manufacturing organization has been configured with the required expenditure types before running cost collection, auditing variance account setup, and extracting parameters for a data warehouse. The following query lists the purchase price variance expenditure type and related variance configuration for a given organization:

  • SELECT organization_id, ppv_expenditure_type, mat_var_expenditure_type, moh_var_expenditure_type, res_var_expenditure_type FROM pjm_org_parameters_v WHERE organization_id = :org_id;
  • SELECT organization_id, common_project_number, project_control_level, allow_cross_proj_issues FROM pjm_org_parameters_v ORDER BY organization_id;
  • SELECT organization_id, transfer_ipv, ipv_expenditure_type, transfer_erv, erv_expenditure_type FROM pjm_org_parameters_v WHERE project_reference_enabled = 'Y';

Because the view is defined over synonyms and is documented as VALID in 12.2.2, it may be queried directly in SQL*Plus, BI Publisher data models, or custom concurrent programs without additional grants beyond those already held on the APPS schema objects.