Results for “pjm_default_tasks”

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

Overview

PJM_DEFAULT_TASKS is a table owned by the PJM schema within the Oracle E-Business Suite Project Manufacturing (PJM) module. Its documented description is "Task AutoAssignment Rules." The table stores the configurable rules that determine how material, procurement, and WIP transactions are automatically assigned to a project and task when they are processed under Project Manufacturing. Rather than requiring users to manually specify a task for every transaction, PJM consults these rules to derive the correct PA_TASKS reference based on criteria such as inventory item, category, subinventory, purchase order, WIP material transaction type, and assembly context. This makes the table central to Project Manufacturing costing and to the integrity of project/task references on downstream transactions.

From a Data Vault modeling perspective, the mined foreign-key structure suggests classifying PJM_DEFAULT_TASKS as a link entity. The table's heavy reliance on foreign keys to organization, project, task, item, category, subinventory, purchase order, department, and operation reference tables means it primarily records associations between business entities rather than serving as a hub of a single business key or a satellite of descriptive attributes.

Key Information Stored

The table contains 37 documented columns. The most significant of these include:

• ASSIGNMENT_TYPE — indicates the type of autoassignment rule being applied and forms part of the unique business key.
• PROJECT_ID and TASK_ID — identify the target project and task to which transactions are assigned; PROJECT_ID references PA_PROJECTS_ALL and TASK_ID references PA_TASKS.
• ORGANIZATION_ID — the manufacturing organization scope, referencing PJM_ORG_PARAMETERS (and MTL_SYSTEM_ITEMS_B).
• INVENTORY_ITEM_ID — the inventory item matched by the rule, referencing MTL_SYSTEM_ITEMS_B.
• CATEGORY_ID — the item category matched, referencing MTL_CATEGORIES_B.
• PO_HEADER_ID — the purchasing document context, referencing PO_HEADERS_ALL.
• SUBINVENTORY_CODE — the subinventory matched, referencing MTL_SECONDARY_INVENTORIES.
• WIP_ENTITY_PATTERN and WIP_MATL_TXN_TYPE — govern WIP entity and material transaction matching.
• ASSEMBLY_ITEM_ID — the assembly item context, referencing MTL_SYSTEM_ITEMS_B.
• DEPARTMENT_ID — the department context, referencing BOM_DEPARTMENTS.
• STANDARD_OPERATION_ID — the operation context, referencing WSM_OPERATION_DETAILS.
• PROCURE_FLAG and TO_ORGANIZATION_ID — procurement and destination organization attributes.
• TASK_ATTRIBUTE_CATEGORY and TASK_ATTRIBUTE1 through TASK_ATTRIBUTE15 — descriptive flexfield segments enabling user-defined rule attributes.

The documented unique index PJM_DEFAULT_TASKS_U1 spans PROJECT_ID, ORGANIZATION_ID, ASSIGNMENT_TYPE, INVENTORY_ITEM_ID, CATEGORY_ID, PO_HEADER_ID, SUBINVENTORY_CODE, WIP_ENTITY_PATTERN, WIP_MATL_TXN_TYPE, PROCURE_FLAG, STANDARD_OPERATION_ID, ASSEMBLY_ITEM_ID, DEPARTMENT_ID, and TO_ORGANIZATION_ID, establishing the business-key candidate for the rule definition. The surrogate primary key is implied by the standard EBS columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN, which support auditing.

Common Use Cases and Queries

Typical scenarios include reviewing configured autoassignment rules, diagnosing why a transaction landed against an unexpected task, and validating rule coverage before period close. A representative query joins the rule to its targets:

• Listing active rules for an organization: SELECT * FROM PJM.PJM_DEFAULT_TASKS WHERE ORGANIZATION_ID = :org_id;
• Resolving the target task for an item: SELECT PROJECT_ID, TASK_ID, ASSIGNMENT_TYPE FROM PJM.PJM_DEFAULT_TASKS WHERE ORGANIZATION_ID = :org_id AND INVENTORY_ITEM_ID = :item_id;
• Auditing rules referencing a specific project: SELECT d.* FROM PJM.PJM_DEFAULT_TASKS d, PA.PA_PROJECTS_ALL p WHERE d.PROJECT_ID = p.PROJECT_ID AND p.SEGMENT1 = :project_number;
• Reporting on unmatched configurations by comparing rule criteria against MTL_SYSTEM_ITEMS_B and MTL_CATEGORIES_B.

Related Objects

The most significant related objects, based on documented foreign keys, include:

• PJM_ORG_PARAMETERS — joined on ORGANIZATION_ID.
• PA_PROJECTS_ALL — joined on PROJECT_ID.
• PA_TASKS — joined on TASK_ID.
• MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID and ASSEMBLY_ITEM_ID (both with ORGANIZATION_ID).
• MTL_CATEGORIES_B — joined on CATEGORY_ID.
• MTL_SECONDARY_INVENTORIES — joined on SUBINVENTORY_CODE (with ORGANIZATION_ID).
• PO_HEADERS_ALL — joined on PO_HEADER_ID.
• BOM_DEPARTMENTS — joined on DEPARTMENT_ID.
• WSM_OPERATION_DETAILS — joined on STANDARD_OPERATION_ID.

These relationships confirm the table's role as a link connecting project, task, inventory, purchasing, and manufacturing references, supporting the autoassignment logic that underpins Project Manufacturing transaction processing.