Search Results pjm_task_wip_acct_classes




Overview
Explore in AI Chat

Overview

The table PJM_TASK_WIP_ACCT_CLASSES is a configuration and reference table within Oracle E-Business Suite Project Manufacturing (PJM). Its core function is to establish and maintain the default Work in Process (WIP) accounting class associations for specific project tasks within each manufacturing organization. This table is fundamental to the integration between Oracle Projects, Manufacturing, and Financials, ensuring that manufacturing costs incurred for a project task are captured and posted to the correct WIP accounting class. By defining these defaults at the task-organization level, it streamulates shop floor transaction processing and enforces consistent cost accounting for project-related manufacturing activities across the enterprise.

Key Information Stored

The table's structure is defined by a composite primary key and several foreign key relationships. The primary key uniquely identifies a record through the combination of PROJECT_ID, ORGANIZATION_ID, and TASK_ID. This design enforces that a default accounting class is defined per task for each specific manufacturing organization where work is performed. The critical data columns include WIP_ACCT_CLASS_CODE, which holds the code for the standard WIP accounting class, and EAM_ACCT_CLASS_CODE, which holds the code for the Enterprise Asset Management (EAM) WIP accounting class. These columns reference valid codes in the WIP_ACCOUNTING_CLASSES table, ensuring referential integrity for the accounting setup.

Common Use Cases and Queries

A primary use case is the automatic defaulting of the WIP accounting class during the creation of discrete jobs or repetitive schedules for a project task. When a user initiates manufacturing for a project component, the system queries this table using the project, organization, and task identifiers to retrieve the pre-defined accounting class. Common queries involve validation and reporting. For instance, to list all configured task-accounting class associations for a specific project, one might use: SELECT TASK_ID, ORGANIZATION_ID, WIP_ACCT_CLASS_CODE FROM PJM_TASK_WIP_ACCT_CLASSES WHERE PROJECT_ID = &PROJECT_ID;. Another critical scenario is troubleshooting cost collection or accounting errors by verifying that a valid default exists for a given task and organization combination.

Related Objects

PJM_TASK_WIP_ACCT_CLASSES is centrally connected to several key EBS tables, as documented by its foreign key constraints. Its integrity depends on and enforces relationships with master data and parameter tables. The documented relationships are:

  • PJM_PROJECT_PARAMETERS: Links via PROJECT_ID and ORGANIZATION_ID to validate that project manufacturing is set up for the given project and organization.
  • PA_TASKS: Links via TASK_ID to ensure the task is a valid, defined task within Oracle Projects.
  • WIP_ACCOUNTING_CLASSES (two relationships): Links via WIP_ACCT_CLASS_CODE and ORGANIZATION_ID, and separately via EAM_ACCT_CLASS_CODE and ORGANIZATION_ID, to validate that the referenced accounting class codes are defined for the specific organization.
These relationships ensure that all default assignments are based on existing, approved setup data within the connected modules.