Search Results pjm_project_parameters




Overview
Explore in AI Chat

Overview

The PJM_PROJECT_PARAMETERS table is a core configuration entity within Oracle E-Business Suite Project Manufacturing (PJM) module. It functions as the central repository for defining and controlling manufacturing execution and financial policies specific to a project within a given inventory organization. This table enables the integration of project-centric manufacturing processes, ensuring that material transactions, work order processing, and cost accounting adhere to the rules defined for a particular project. Its existence is fundamental to the PJM module's ability to manage production and costs by project, distinguishing it from standard manufacturing operations.

Key Information Stored

The table's primary key is a composite of PROJECT_ID and ORGANIZATION_ID, establishing a unique configuration per project-organization combination. Beyond these identifiers, the table stores critical control parameters. Key columns include various expenditure type codes (e.g., IPV_EXPENDITURE_TYPE, PPV_EXPENDITURE_TYPE, FREIGHT_EXPENDITURE_TYPE) that link project manufacturing costs to specific Oracle Projects expenditure categories for detailed cost tracking. It also holds accounting class codes (WIP_ACCT_CLASS_CODE, EAM_ACCT_CLASS_CODE) to determine the Work in Process accounting class used for project-related jobs. Additional columns manage settings for project-specific shop floor control, material backflushing, and other execution flags that dictate how manufacturing operations are processed for the project.

Common Use Cases and Queries

A primary use case is validating or reporting on the project manufacturing setup across an enterprise. Administrators often query this table to audit which projects have manufacturing enabled in which organizations and to review their associated accounting and costing rules. For integration or data migration scripts, it is crucial to reference this table to ensure project parameters are correctly established. A typical diagnostic query would join with PA_PROJECTS_ALL and ORG_ORGANIZATION_DEFINITIONS to produce a human-readable report.

Sample SQL Pattern:
SELECT ppa.segment1 project_number,
ood.organization_code,
ppp.*
FROM pjm_project_parameters ppp,
pa_projects_all ppa,
org_organization_definitions ood
WHERE ppp.project_id = ppa.project_id
AND ppp.organization_id = ood.organization_id
AND ood.organization_code = 'M1';

Related Objects

The PJM_PROJECT_PARAMETERS table maintains integral relationships with several key EBS tables, primarily through foreign key constraints. These relationships enforce data integrity and define its role in the application architecture.

  • PA_PROJECTS_ALL: Links to the core Projects table via PROJECT_ID to identify the master project definition.
  • PJM_ORG_PARAMETERS: Links via ORGANIZATION_ID to the organization-level Project Manufacturing settings.
  • WIP_ACCOUNTING_CLASSES: Linked twice via ORGANIZATION_ID and the respective class code columns (WIP_ACCT_CLASS_CODE, EAM_ACCT_CLASS_CODE) to define the accounting classes for work orders.
  • PA_EXPENDITURE_TYPES: Linked via multiple expenditure type columns (IPV_EXPENDITURE_TYPE, ERV_EXPENDITURE_TYPE, FREIGHT_EXPENDITURE_TYPE, TAX_EXPENDITURE_TYPE, MISC_EXPENDITURE_TYPE, PPV_EXPENDITURE_TYPE) for cost classification.
  • PJM_SEIBAN_NUMBERS: Related via PROJECT_ID for project-specific numbering (Seiban) control.
  • PJM_TASK_WIP_ACCT_CLASSES: Related via the composite key (PROJECT_ID, ORGANIZATION_ID) for more granular, task-level accounting class assignments.