Results for “eam_acct_class_code”

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

Overview

PJM.PJM_PROJECT_PARAMETERS is a Project Manufacturing (PJM) table that stores the control and execution options governing how a specific project is managed within a specific inventory organization. It defines the operational defaults applied to project-related transactions — manufacturing, purchasing, receiving, and costing — at the intersection of a project and an inventory organization. In Oracle EBS 12.1.1 and 12.2.2, this table is central to the Project Manufacturing module, which supports contract manufacturing, build-to-order, and other project-driven supply chain flows.

The table sits at the junction of two key dimensions: the project (PROJECT_ID from PA_PROJECTS_ALL) and the inventory organization (ORGANIZATION_ID from PJM_ORG_PARAMETERS). Because its columns are largely descriptive attributes of that pairing, ETRM's heuristic Data Vault classification treats it as satellite-leaning — that is, a descriptive satellite on the project/organization combination, as opposed to a pure hub or link table. This is a modeling suggestion only; the physical table is a standard EBS transactional control table.

Key Information Stored

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

• PROJECT_ID — foreign key to PA_PROJECTS_ALL; identifies the project.
• ORGANIZATION_ID — foreign key to PJM_ORG_PARAMETERS; identifies the inventory organization.
• PLANNING_GROUP — planning group assignment for the project/organization combination.
• COSTING_GROUP_ID — costing group used for cost collection.
• WIP_ACCT_CLASS_CODE — WIP accounting class (FK to WIP_ACCOUNTING_CLASSES).
• EAM_ACCT_CLASS_CODE — EAM accounting class (FK to WIP_ACCOUNTING_CLASSES).
• IPV_EXPENDITURE_TYPE — expenditure type for inter-project transfers.
• ERV_EXPENDITURE_TYPE — expenditure type for expense report/ERV flows.
• FREIGHT_EXPENDITURE_TYPE, TAX_EXPENDITURE_TYPE, MISC_EXPENDITURE_TYPE — expenditure types for landed-cost components.
• PPV_EXPENDITURE_TYPE — expenditure type for purchase price variance.
• DIR_ITEM_EXPENDITURE_TYPE — expenditure type for direct item charges.
• SEIBAN_NUMBER_FLAG — flag relating to Seiban number handling (linked to PJM_SEIBAN_NUMBERS).
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating for the parameter row.

Primary key: PJM_PROJECT_PARAMETERS_PK (PROJECT_ID, ORGANIZATION_ID). Two unique indexes — PJM_PROJECT_PARAMETERS_U1 (PROJECT_ID, ORGANIZATION_ID) and PJM_PROJECT_PARAMETERS_U2 (ORGANIZATION_ID, PROJECT_ID) — confirm this pairing as the business key. There is no single-column surrogate; the composite project/organization pair serves as the key.

Common Use Cases and Queries

A common reporting need is retrieving the manufacturing and accounting options for a given project in a given org:

• Joining to PA_PROJECTS_ALL to report WIP accounting classes and expenditure type assignments by project.
• Auditing which projects have Seiban handling enabled (SEIBAN_NUMBER_FLAG).
• Validating effective-dated parameter rows via START_DATE_ACTIVE/END_DATE_ACTIVE.

A representative query pattern is:

SELECT ppp.project_id, ppp.organization_id, ppp.wip_acct_class_code, ppp.ppv_expenditure_type FROM pjm_project_parameters ppp WHERE ppp.organization_id = :org AND ppp.project_id = :project;

Additional patterns join PJM_PROJECT_PARAMETERS to WIP_ACCOUNTING_CLASSES and PA_EXPENDITURE_TYPES to resolve descriptive names for reporting, and to PJM_TASK_WIP_ACCT_CLASSES for task-level class derivation.

Related Objects

• PA_PROJECTS_ALL — joined on PROJECT_ID; source of project definition.
• PJM_ORG_PARAMETERS — joined on ORGANIZATION_ID; organization-level PJM options.
• WIP_ACCOUNTING_CLASSES — joined via WIP_ACCT_CLASS_CODE and EAM_ACCT_CLASS_CODE.
• PA_EXPENDITURE_TYPES — joined via IPV_EXPENDITURE_TYPE, ERV_EXPENDITURE_TYPE, PPV_EXPENDITURE_TYPE, FREIGHT_EXPENDITURE_TYPE, TAX_EXPENDITURE_TYPE, MISC_EXPENDITURE_TYPE.
• PJM_SEIBAN_NUMBERS — joined on PROJECT_ID.
• PJM_TASK_WIP_ACCT_CLASSES — references this table via PROJECT_ID and ORGANIZATION_ID.

These relationships make PJM_PROJECT_PARAMETERS the governing configuration point for project manufacturing execution and costing across the PJM, WIP, and PA schemas.