Search Results allow_cross_proj_issues

Overview

PJM_ORG_PARAMETERS is the organization-level control table for Oracle Project Manufacturing (PJM) in Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the PJM schema and stores the setup options, defaults, and posting rules that govern how a given manufacturing organization interacts with Oracle Projects. Because Project Manufacturing is organization-scoped rather than ledger-scoped, this table effectively defines which inventory organizations behave as project manufacturing organizations and how transactions within them are costed, transferred, and accounted.

The table is keyed on ORGANIZATION_ID through the PJM_ORG_PARAMETERS_PK constraint, with a matching unique index PJM_ORG_PARAMETERS_U1 on the same column. This means exactly one parameter row exists per organization, making ORGANIZATION_ID both the primary key and the natural business key. Under the heuristic Data Vault classification supplied in the metadata, the table is characterized as satellite-leaning: it is a descriptive, attribute-bearing structure attached to an organizational hub (the organization itself) rather than a transactional junction. The physical schema documents 53 columns, the majority of which are configuration flags and expenditure type references rather than transactional data.

Key Information Stored

The columns divide into several functional groups:

• Organization identifier and audit columns — ORGANIZATION_ID (primary key), plus the standard EBS audit set: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.
• Project control options — PROJECT_REFERENCE_ENABLED controls whether project references are required on transactions, PROJECT_CONTROL_LEVEL defines the granularity at which project control is enforced, and COMMON_PROJECT_ID identifies a default project pointing to PA_PROJECTS_ALL.
• Cross-project and cross-unit rules — ALLOW_CROSS_PROJ_ISSUES and ALLOW_CROSS_UNITNUM_ISSUES determine whether material may be issued across project or unit number boundaries.
• Cost transfer flags and expenditure type defaults — TRANSFER_IPV, TRANSFER_ERV, TRANSFER_FREIGHT, TRANSFER_TAX, and TRANSFER_MISC act as switches, with the paired IPV_EXPENDITURE_TYPE, ERV_EXPENDITURE_TYPE, FREIGHT_EXPENDITURE_TYPE, TAX_EXPENDITURE_TYPE, and MISC_EXPENDITURE_TYPE columns supplying the destination expenditure types from PA_EXPENDITURE_TYPES.
• Variance expenditure type and payback accounts — PPV_EXPENDITURE_TYPE, MAT_VAR_EXPENDITURE_TYPE, MOH_VAR_EXPENDITURE_TYPE, RES_VAR_EXPENDITURE_TYPE, OSP_VAR_EXPENDITURE_TYPE, and OVH_VAR_EXPENDITURE_TYPE define variance capture, while the PAYBACK_MAT_VAR_ACCOUNT, PAYBACK_MOH_VAR_ACCOUNT, PAYBACK_RES_VAR_ACCOUNT, PAYBACK_OSP_VAR_ACCOUNT, and PAYBACK_OVH_VAR_ACCOUNT columns designate the accounts used to relieve variances.
• Accounting and integration controls — PA_POSTING_FLAG, PA_AUTOACCOUNTING_FLAG, WIP_AS_STRAIGHT_TIME_FLAG, PJM_CLEARING_ACCOUNT, and DIR_ITEM_EXPENDITURE_TYPE govern posting behavior and the clearing account used in Project Manufacturing accounting flows.
• Descriptive flexfield — ATTRIBUTE_CATEGORY through ATTRIBUTE15 provide the standard 15-column DFF for customer-specific extensions.

Common Use Cases and Queries

The most frequent reporting need is to determine the setup posture of each project manufacturing organization. A typical query joins this table to MTL_PARAMETERS to obtain the organization code alongside the parameters:

SELECT mp.organization_code,
       op.project_control_level,
       op.project_reference_enabled,
       op.allow_cross_proj_issues,
       op.pa_posting_flag
FROM   pjm_org_parameters op,
       mtl_parameters mp
WHERE  op.organization_id = mp.organization_id;

Other practical uses include auditing which expenditure types are assigned to each organization for cost transfer, verifying that payback accounts are configured before period close, and troubleshooting "no expenditure type found" errors during cost collection. Because ATTRIBUTE columns are available, implementations frequently expose a project manufacturing parameters report or a custom concurrent program driven by this table.

Related Objects

PJM_ORG_PARAMETERS references several parent tables and is itself referenced by dependent PJM setup tables:

• MTL_PARAMETERS — joined on ORGANIZATION_ID; supplies the organization definition and validation for inventory organizations.
• PJM_PROJECT_PARAMETERS — references PJM_ORG_PARAMETERS.ORGANIZATION_ID and stores project-specific overrides beneath the organization defaults.
• PJM_DEFAULT_TASKS — references PJM_ORG_PARAMETERS.ORGANIZATION_ID and defines default task assignments per organization.
• PA_PROJECTS_ALL — referenced via COMMON_PROJECT_ID for the organization's default common project.
• PA_EXPENDITURE_TYPES — referenced by nine expenditure type columns, including IPV, ERV, FREIGHT, TAX, MISC, PPV, and the MAT/MOH/RES/OSP/OVH variance columns.

Together these relationships place PJM_ORG_PARAMETERS at the center of Project Manufacturing organization setup, bridging Oracle Inventory organization definitions with Oracle Projects cost and accounting configuration.