Search Results pjm_default_tasks




Overview
Explore in AI Chat

Overview

The table PJM_DEFAULT_TASKS is a core data object within the Project Manufacturing (PJM) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as the repository for Task AutoAssignment Rules. These rules are a critical configuration component that automates the association of manufacturing tasks and project accounting details to various transactional entities. The primary role of this table is to enable the system to automatically default a specific project and task onto discrete jobs, work orders, and related material transactions based on pre-defined criteria such as item, category, or subinventory. This automation ensures accurate project cost collection and eliminates manual data entry, thereby enforcing project accounting integrity within a manufacturing context.

Key Information Stored

The table stores rule definitions that link transactional attributes to specific project accounting segments. Its key columns, as indicated by its foreign key relationships, define the rule's conditions and its target assignment. Important columns include ORGANIZATION_ID, which scopes the rule to a specific inventory organization. The rule's conditional criteria are defined by columns like INVENTORY_ITEM_ID, CATEGORY_ID, SUBINVENTORY_CODE, ASSEMBLY_ITEM_ID, DEPARTMENT_ID, and PO_HEADER_ID. The target of the assignment is specified by PROJECT_ID and TASK_ID. Additional control columns, typical in such rule tables, would include effective dates (START_DATE, END_DATE), a SEQUENCE_NUMBER for rule precedence, and CREATION_DATE/CREATED_BY audit fields, though these are not explicitly listed in the provided metadata.

Common Use Cases and Queries

The primary use case is the automatic derivation of project and task information during manufacturing execution. For instance, when a discrete job is created for a specific assembly item in a given department, the system queries PJM_DEFAULT_TASKS to find a matching rule and populates the job's project and task fields. Common reporting and maintenance queries include listing all active auto-assignment rules for an organization or identifying the rule that applied to a specific transaction. A sample SQL pattern to audit rules is:

  • SELECT rule.organization_id, rule.inventory_item_id, msib.segment1 item, rule.project_id, rule.task_id FROM pjm_default_tasks rule, mtl_system_items_b msib WHERE rule.organization_id = msib.organization_id AND rule.inventory_item_id = msib.inventory_item_id AND rule.organization_id = :p_org_id;

Administrators also query this table to troubleshoot missing project assignments or to analyze rule precedence and conflicts.

Related Objects

As evidenced by its foreign keys, PJM_DEFAULT_TASKS is centrally connected to several fundamental EBS tables. Its integrity and functionality are dependent on relationships with:

This table is typically accessed via PJM's internal application logic and APIs, rather than directly, to maintain business rule consistency.