Search Results pjm_org_parameters




Overview
Explore in AI Chat

Overview

The PJM_ORG_PARAMETERS table is a central control table within the Oracle E-Business Suite Project Manufacturing (PJM) module. It functions as the primary repository for organization-level configuration options and default values that govern how manufacturing and cost transactions are processed for project-related activities. Each record corresponds to a specific manufacturing organization, as defined in the Inventory module (MTL_PARAMETERS), enabling tailored project manufacturing policies per operational unit. Its role is critical for integrating manufacturing execution with project accounting, ensuring costs are correctly captured, classified, and reported against designated projects and tasks.

Key Information Stored

The table's primary key is ORGANIZATION_ID, which uniquely identifies the manufacturing organization. Beyond this identifier, the table stores numerous parameters that act as defaults and control switches. A significant portion of its columns are foreign keys to the PA_EXPENDITURE_TYPES table, defining the specific expenditure types used for various cost variances and charges in project accounting. These include, but are not limited to, Invoice Price Variance (IPV_EXPENDITURE_TYPE), Purchase Price Variance (PPV_EXPENDITURE_TYPE), and variances for Material (MAT_VAR_EXPENDITURE_TYPE), Overhead (OVH_VAR_EXPENDITURE_TYPE), and Resources (RES_VAR_EXPENDITURE_TYPE). Another key column is COMMON_PROJECT_ID, which links to PA_PROJECTS_ALL to designate a default project for unassigned transactions or common inventory.

Common Use Cases and Queries

This table is primarily referenced during transaction processing (e.g., WIP completions, cost updates) to determine the correct project accounting defaults. Common operational and reporting queries involve joining with inventory and project tables to validate or audit organization setup. A typical query retrieves all parameters for a given organization to review its project accounting linkages:

  • SELECT pop.*, mp.organization_code FROM pjm_org_parameters pop, mtl_parameters mp WHERE pop.organization_id = mp.organization_id AND mp.organization_code = 'M1';

Another frequent use case is identifying organizations configured to use a specific default project or expenditure type, which is essential for troubleshooting cost collection errors or performing impact analysis before modifying master data.

Related Objects

The PJM_ORG_PARAMETERS table maintains integral relationships with several core EBS tables, primarily through foreign key constraints. Its central relationship is with MTL_PARAMETERS via the ORGANIZATION_ID column, anchoring it to the inventory organization. It is heavily linked to the Project Accounting module through foreign keys to PA_EXPENDITURE_TYPES for various cost types and to PA_PROJECTS_ALL for the common project. Furthermore, it is referenced as a parent table by other PJM control tables, including PJM_DEFAULT_TASKS and PJM_PROJECT_PARAMETERS, which store more granular task-level and project-level defaults, respectively, for the organization.