Results for “pjm_project_parameters_u1”

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

Overview

PJM.PJM_PROJECT_PARAMETERS is the Project Manufacturing (PJM) configuration table in Oracle E-Business Suite, holding the Project Manufacturing parameters defined for a given project and inventory organization combination. It is the physical implementation of the Project Parameters window in the Project Manufacturing module, and it governs how a project behaves within a specific inventory organization with respect to planning groups, costing groups, WIP accounting classes, and the expenditure types used to absorb invoice-related variances. The table is owned by the PJM schema, is stored in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and is designated FND Design Data PJM.PJM_PROJECT_PARAMETERS. Its primary key, PJM_PROJECT_PARAMETERS_PK, is the composite of PROJECT_ID and ORGANIZATION_ID.

From a data modeling perspective, the mined relationship structure classifies this object as satellite-leaning. It extends the intersection of project and inventory organization with descriptive parameters such as planning group, costing group, and variance expenditure types, rather than acting as an independent hub or pure many-to-many link. Modelers should treat it as a satellite attached to the project/organization combination.

Key Information Stored

The table contains 37 documented columns. The most operationally significant are:

• PROJECT_ID — System-generated number uniquely identifying a project or seiban; part of the composite primary key and a business-key candidate in both unique indexes.
• ORGANIZATION_ID — Inventory organization unique identifier; the second component of the primary key and of both unique indexes.
• PLANNING_GROUP — The planning group assigned to the project within this inventory organization.
• COSTING_GROUP_ID — The cost group assigned to the project in this organization; also the driving column of the non-unique index PJM_PROJECT_PARAMETERS_N1 alongside ORGANIZATION_ID.
• WIP_ACCT_CLASS_CODE — Default standard discrete WIP accounting class for the project/organization, foreign-keyed to WIP_ACCOUNTING_CLASSES.
• EAM_ACCT_CLASS_CODE — Accounting class used for Enterprise Asset Management activity, also referencing WIP_ACCOUNTING_CLASSES.
• IPV_EXPENDITURE_TYPE — Expenditure type for invoice price variance.
• ERV_EXPENDITURE_TYPE — Expenditure type for exchange rate variance.
• FREIGHT_EXPENDITURE_TYPE, TAX_EXPENDITURE_TYPE, MISC_EXPENDITURE_TYPE, PPV_EXPENDITURE_TYPE — Expenditure types for freight, tax, miscellaneous, and purchase price variance charges respectively; each references PA_EXPENDITURE_TYPES.
• DIR_ITEM_EXPENDITURE_TYPE — Expenditure type for direct item charges.
• SEIBAN_NUMBER_FLAG — Flag indicating whether PROJECT_ID identifies a seiban rather than a standard project.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective date range for the parameter row.
• ATTRIBUTE1–ATTRIBUTE15 and ATTRIBUTE_CATEGORY — The standard DFF-enabled descriptive flexfield columns, plus the standard Who columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN).

Two unique indexes serve as business-key candidates: PJM_PROJECT_PARAMETERS_U1 on (PROJECT_ID, ORGANIZATION_ID) and PJM_PROJECT_PARAMETERS_U2 on (ORGANIZATION_ID, PROJECT_ID). The latter is the index users locate when searching for "pjm_project_parameters_u2."

Common Use Cases and Queries

The most frequent use case is determining the WIP accounting class and variance expenditure types for a project/organization pair before processing manufacturing or purchasing transactions:

• Retrieve parameters for a specific project and organization by joining on both key columns.
• Report all projects configured in a given organization, ordering by project, using the N1 index path on ORGANIZATION_ID and COSTING_GROUP_ID.
• Audit projects that share a costing group or planning group for cost rollup and planning analysis.
• Validate that variance expenditure types (IPV, ERV, PPV, freight, tax, misc) are populated before invoice matching, since nulls cause accounting failures.
• Identify seiban-configured rows using SEIBAN_NUMBER_FLAG.

A typical query joins PJM_PROJECT_PARAMETERS to PA_PROJECTS_ALL on PROJECT_ID and to HR_ALL_ORGANIZATION_UNITS (via ORGANIZATION_ID) to produce a readable parameter report:

SELECT p.project_number, p.name, pp.planning_group, pp.costing_group_id, pp.wip_acct_class_code, pp.ipv_expenditure_type FROM pjm.pjm_project_parameters pp, pa_projects_all p WHERE pp.project_id = p.project_id AND pp.organization_id = :org_id;

Related Objects

The table is tightly integrated with Project Manufacturing and Project Accounting objects through its foreign keys:

• PA_PROJECTS_ALL — Joined on PROJECT_ID; the master project definition.
• PJM_SEIBAN_NUMBERS — Alternate parent for PROJECT_ID when the row represents a seiban.
• PJM_ORG_PARAMETERS — Referenced by ORGANIZATION_ID; defines organization-level PJM defaults.
• WIP_ACCOUNTING_CLASSES — Referenced by WIP_ACCT_CLASS_CODE and EAM_ACCT_CLASS_CODE.
• PA_EXPENDITURE_TYPES — Referenced by IPV, ERV, FREIGHT, TAX, MISC, and PPV expenditure type columns.
• PJM_TASK_WIP_ACCT_CLASSES — Child table referencing PROJECT_ID, holding task-level WIP accounting class overrides.