Search Results task_attribute10




Overview
Explore in AI Chat

Overview

The view APPS.PJM_DEFAULT_TASKS_INV_V is a material task auto-assignment view delivered as part of the Oracle Project Manufacturing (PJM) module. Its stated purpose, per the ETRM documentation, is to expose the rules configured in the PJM Default Tasks setup against inventory-related transactions, so that the application can derive the correct project and task references when material movements are processed. The view is a read-only, denormalized projection of the PJM_DEFAULT_TASKS base table, restricted by the predicate ASSIGNMENT_TYPE = 'MATERIAL', and enriched with descriptive attributes resolved from inventory, purchasing, project, task, and HR organization tables.

Because it is a view rather than a table, it carries no independent storage and no concurrency or locking behavior of its own. It is primarily consumed by Oracle Projects and Project Manufacturing workflows, and it is frequently queried by technical consultants, report developers, and integration specialists who need to validate or extract the material task assignment configuration. The presence of the sixteen TASK_ATTRIBUTE columns and a TASK_ATTRIBUTE_CATEGORY column makes it a common target for user searching on task_attribute1, since that column frequently stores a client-specific descriptive flexfield segment used to qualify assignment rules.

Underlying Base Objects

The view is defined over six referenced objects. The driving table is PJM_DEFAULT_TASKS (aliased PDT), which supplies all assignment and attribute columns. The remaining objects supply descriptive context:

The documented metadata also lists dependency on the packages HR_GENERAL and HR_SECURITY, indicating that organization-level security is enforced when the view is queried, and that organization name resolution may depend on HR security profiles.

Key Columns

The view exposes the full attribute set of the default task assignment record alongside descriptive columns from the joined tables.

  • ROW_ID — the ROWID of the underlying PJM_DEFAULT_TASKS row, useful for correlated updates in maintenance scripts.
  • ASSIGNMENT_TYPE — always 'MATERIAL' in this view, since the WHERE clause filters on that value.
  • INVENTORY_ITEM_ID, CATEGORY_ID, SUBINVENTORY_CODE — the item, category, and subinventory criteria that scope the assignment rule.
  • ORGANIZATION_ID, ORGANIZATION_CODE, ORGANIZATION_NAME — inventory organization identifiers and descriptions.
  • PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME, TASK_ID, TASK_NUMBER, TASK_NAME — the project and task to which material transactions will default.
  • PO_HEADER_ID, ORDER_NUMBER — optional purchase order reference.
  • PROCURE_FLAG — indicates whether the assignment drives procurement-related behavior.
  • TASK_ATTRIBUTE_CATEGORY and TASK_ATTRIBUTE1 through TASK_ATTRIBUTE15 — the descriptive flexfield context and segments associated with the task assignment. TASK_ATTRIBUTE1 is the most frequently queried of these, typically holding a client-defined classification value.
  • COMMENTS, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit and descriptive columns.

Common Use Cases and Queries

Typical scenarios include confirming that a default task assignment exists for a given organization and item before a material transaction is processed, exporting the configured assignment matrix for audit, and diagnosing why an inventory transaction failed to auto-assign a project or task. A representative query isolating assignments by flexfield value is shown below.

SELECT organization_code,
       inventory_item_id,
       subinventory_code,
       project_number,
       task_number,
       task_attribute_category,
       task_attribute1
  FROM apps.pjm_default_tasks_inv_v
 WHERE organization_id = :p_org_id
   AND task_attribute1 = :p_attribute1;

A second common pattern joins the view to MTL_SYSTEM_ITEMS_VL or MTL_CATEGORIES_B to render readable descriptions for the item and category criteria:

SELECT v.organization_code,
       msi.segment1  item_number,
       v.category_id,
       v.project_number,
       v.task_number
  FROM apps.pjm_default_tasks_inv_v v,
       apps.mtl_system_items_b msi
 WHERE msi.inventory_item_id = v.inventory_item_id
   AND msi.organization_id   = v.organization_id;

Because the view is subject to HR security through HR_SECURITY, queries should be executed in a session whose security profile permits access to the target organizations; otherwise the ORGANIZATION_NAME and related rows may not be returned as expected.