Search Results pjm_default_tasks_scp_v




Overview
Explore in AI Chat

Overview

PJM_DEFAULT_TASKS_SCP_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PJM (Project Manufacturing) product family. It is documented as the "Supply chain Task AutoAssignment view" and is designed to present the default task assignments that govern how supply chain transactions are automatically associated with project tasks during project manufacturing and project procurement flows.

The view consolidates task assignment records from PJM_DEFAULT_TASKS and enriches them with descriptive attributes drawn from projects, tasks, inventory organizations, and HR organization units. Because it resolves surrogate identifiers such as PROJECT_ID, TASK_ID, ORGANIZATION_ID, and TO_ORGANIZATION_ID into human-readable values like PROJECT_NUMBER, TASK_NAME, ORGANIZATION_CODE, ORGANIZATION_NAME, and TO_ORGANIZATION_NAME, the view is well suited for operational reporting, reconciliation, and integration extracts where business users or external systems require legible context rather than raw keys.

The view is restricted by definition to rows where ASSIGNMENT_TYPE equals 'SUPPLY CHAIN', so it exposes only the auto-assignment rules relevant to supply chain task defaults, not the full spectrum of Project Manufacturing default task assignment types. It is a query-only construct: no DML is performed directly against it.

Underlying Base Objects

The view is defined over the following documented base objects:

  • PJM_DEFAULT_TASKS (synonym) — the driving table supplying assignment rules, including ASSIGNMENT_TYPE, TASK_ID, PROJECT_ID, ORGANIZATION_ID, TO_ORGANIZATION_ID, INVENTORY_ITEM_ID, CATEGORY_ID, the fifteen TASK_ATTRIBUTE columns, COMMENTS, and standard WHO audit columns.
  • PA_PROJECTS_ALL (synonym) — supplies PROJECT_NUMBER (SEGMENT1) and PROJECT_NAME.
  • PA_TASKS (synonym) — supplies TASK_NUMBER and TASK_NAME.
  • MTL_PARAMETERS (synonym) — supplies ORGANIZATION_CODE.
  • HR_ORGANIZATION_UNITS (view) — joined twice, aliased HR and HRO, to supply ORGANIZATION_NAME and TO_ORGANIZATION_NAME respectively.
  • HR_GENERAL and HR_SECURITY (packages) — referenced as part of the HR organization resolution and row-level security behavior underlying HR_ORGANIZATION_UNITS.

All joins are equi-joins on the primary keys of the respective source objects: PROJECT_ID, TASK_ID, and ORGANIZATION_ID. Notably, the ORGANIZATION_NAME and TO_ORGANIZATION_NAME columns are both joined from HR_ORGANIZATION_UNITS on ORGANIZATION_ID in the documented view text, meaning the "to" organization label reflects the shipment destination context defined by the target organization identifier as resolved through the HR organization hierarchy.

Key Columns

  • ROW_ID — the ROWID of the underlying PJM_DEFAULT_TASKS row.
  • ASSIGNMENT_TYPE — always 'SUPPLY CHAIN' in this view's result set.
  • TASK_ID / TASK_NUMBER / TASK_NAME — the project task to which supply chain transactions default.
  • PROJECT_ID / PROJECT_NUMBER / PROJECT_NAME — the owning project.
  • ORGANIZATION_ID / ORGANIZATION_CODE / ORGANIZATION_NAME — the source inventory organization.
  • TO_ORGANIZATION_ID / TO_ORGANIZATION_NAME — the destination (receiving) organization. This is the column most commonly searched, as it identifies where a supply chain default task assignment is targeted.
  • INVENTORY_ITEM_ID, CATEGORY_ID — optional item/category scoping of the default assignment.
  • TASK_ATTRIBUTE_CATEGORY and TASK_ATTRIBUTE1–15 — descriptive flexfield context and segments.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit columns.
  • COMMENTS — free text annotation on the assignment.

Common Use Cases and Queries

Typical scenarios include auditing which supply chain default tasks are defined per destination organization, troubleshooting why a transaction defaulted to an unexpected task, and extracting assignment definitions for reconciliation or migration.

Sample query listing default supply chain tasks by destination organization:

SELECT project_number, task_number, organization_code, to_organization_name, creation_date FROM apps.pjm_default_tasks_scp_v WHERE to_organization_name = 'M1 – Seattle Manufacturing' ORDER BY project_number, task_number;

Sample query identifying all supply chain defaults for a specific project:

SELECT project_number, project_name, task_number, task_name, organization_code, to_organization_name FROM apps.pjm_default_tasks_scp_v WHERE project_number = 'PRJ-1001';

Because the view exposes only ASSIGNMENT_TYPE = 'SUPPLY CHAIN' rows, reports requiring other assignment types must query the underlying PJM_DEFAULT_TASKS table directly.