Results for “pjm_default_tasks_wipl_v”

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

Overview

PJM_DEFAULT_TASKS_WIPL_V is a PL/SQL view owned by the APPS schema and registered as VALID in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the PJM (Project Manufacturing) product family and functions as the Resource / Overhead Task AutoAssignment view. The view presents the rules that drive automatic assignment of project tasks to resources and overheads during work-in-process (WIP) transactions. Because Project Manufacturing requires every manufacturing transaction to be charged to a valid project and task, the default-task setup stored in PJM_DEFAULT_TASKS determines which task is applied when a shop-floor transaction is created without an explicit task entry.

The view enriches the underlying PJM_DEFAULT_TASKS table with human-readable descriptions drawn from reference tables such as PA_PROJECTS_ALL, PA_TASKS, BOM_DEPARTMENTS, BOM_STANDARD_OPERATIONS, MTL_PARAMETERS, and HR_ORGANIZATION_UNITS. Its role in EBS reporting and integration is to expose these autoassignment rules in a denormalized form suitable for inquiry, concurrent-program extracts, and downstream interfaces. The view is restricted to rows where ASSIGNMENT_TYPE = 'RESOURCE', so it covers resource-level assignment defaults; overhead assignment rules are filtered out by this predicate.

Underlying Base Objects

The documented base objects referenced by PJM_DEFAULT_TASKS_WIPL_V are:

• PJM_DEFAULT_TASKS (SYNONYM) — the primary driving table; alias PDT. Supplies assignment type, WIP entity pattern, task, project, department, organization, and the DFF task-attribute columns.
• PA_PROJECTS_ALL (SYNONYM) — supplies PROJECT_NUMBER (SEGMENT1) and PROJECT_NAME. Joined on PROJECT_ID (non-outer).
• PA_TASKS (SYNONYM) — supplies TASK_NUMBER and TASK_NAME. Joined on TASK_ID (non-outer).
• BOM_DEPARTMENTS (SYNONYM) — supplies DEPARTMENT_CODE. Outer-joined on DEPARTMENT_ID (+).
• BOM_STANDARD_OPERATIONS (SYNONYM) — supplies OPERATION_CODE. Outer-joined on STANDARD_OPERATION_ID (+).
• MTL_PARAMETERS (SYNONYM) — supplies ORGANIZATION_CODE. Joined on ORGANIZATION_ID (non-outer).
• HR_ORGANIZATION_UNITS (VIEW) — supplies ORGANIZATION_NAME. Joined on ORGANIZATION_ID (non-outer).
• HR_GENERAL (PACKAGE) and HR_SECURITY (PACKAGE) — supporting objects referenced through HR_ORGANIZATION_UNITS to enforce organization-level security and display formatting.

Because the joins to PA_PROJECTS_ALL, PA_TASKS, MTL_PARAMETERS, and HR_ORGANIZATION_UNITS are non-outer, a default-task row is only returned when a matching project, task, and organization master record exists.

Key Columns

• ROW_ID — the ROWID of the PJM_DEFAULT_TASKS row; used for direct DML against the base table.
• ASSIGNMENT_TYPE — the assignment category; always 'RESOURCE' in this view.
• WIP_ENTITY_PATTERN — the pattern that matches WIP entities (such as a work-order prefix or mask) to which the rule applies. This is the column most closely tied to the user search term.
• PROJECT_ID / PROJECT_NUMBER / PROJECT_NAME — the project to which the default task belongs.
• TASK_ID / TASK_NUMBER / TASK_NAME — the task returned by the autoassignment rule.
• STANDARD_OPERATION_ID / OPERATION_CODE — the optional standard operation scope for the rule.
• DEPARTMENT_ID / DEPARTMENT_CODE — the optional department scope.
• ORGANIZATION_ID / ORGANIZATION_CODE / ORGANIZATION_NAME — the manufacturing organization context.
• TASK_ATTRIBUTE_CATEGORY and TASK_ATTRIBUTE1 through TASK_ATTRIBUTE15 — descriptive flexfield context and segment values carried on the default-task setup.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
• COMMENTS — free-text notes recorded on the default-task definition.

Common Use Cases and Queries

The view is typically queried to audit autoassignment setups, to troubleshoot why an unexpected task was charged on a WIP transaction, or to feed extracts that reconcile Project Manufacturing defaults against project and task masters.

Listing all resource default-task rules for a given project:

SELECT project_number, project_name, task_number, task_name, wip_entity_pattern, operation_code, department_code, organization_code FROM apps.pjm_default_tasks_wipl_v WHERE project_number = 'PROJ-1001' ORDER BY wip_entity_pattern;

Searching on the WIP entity pattern (the user's original term):

SELECT wip_entity_pattern, project_number, task_number, organization_code, comments FROM apps.pjm_default_tasks_wipl_v WHERE wip_entity_pattern LIKE 'WO%' AND organization_code = 'M1';

Reviewing flexfield attributes stored against each rule:

SELECT task_number, task_attribute_category, task_attribute1, task_attribute2, last_update_date, last_updated_by FROM apps.pjm_default_tasks_wipl_v WHERE organization_id = 204;

Because the view exposes ROW_ID, it also serves as the query layer for form-based maintenance of the underlying PJM_DEFAULT_TASKS records. Organizations implementing Project Manufacturing should treat this view as read-only for reporting; changes to autoassignment behavior must be made through the originating PJM setup forms or by DML on PJM_DEFAULT_TASKS using ROW_ID.