Search Results pjm_tasks_mxfr_v




Overview
Explore in AI Chat

Overview

PJM_TASKS_MXFR_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, defined within the Project Manufacturing (PJM) product family. Its purpose is to supply a task-selection list for the Project Manufacturing transfer and expenditure flows, presenting a union of real project/task rows and a synthetic "project level" row. The view is exposed as a valid database object in both 12.1.1 and 12.2.2, and its definition is documented in ETRM for release 12.2.2.

The view is not a base data store; it is a reporting and LOV (list of values) construct. Its design flattens two distinct sources into a single result set so that consuming forms, concurrent programs, and integrations can resolve a task identifier regardless of whether the underlying project controls work at the task level or at the project level. This makes it central to any process that must attach material, labor, or expense to a project and task combination.

The name suffix "_MXFR" is consistent with manufacturing transfer usage, while the "PJM" prefix places the object inside Project Manufacturing. Because it is a view rather than a table, it carries no storage of its own and inherits all security behavior from its underlying project and task views.

Underlying Base Objects

The documented base objects for this view are FND_MESSAGE_CACHE (package), FND_PROFILE (package), HR_ORGANIZATION_INFORMATION (synonym), PA_PROJECTS_ALL_EXPEND_V (view), PA_PROJECT_UTILS (package), PA_SECURITY (package), PA_TASKS_ALL_EXPEND_V (view), and PA_TASK_UTILS (package).

  • PA_TASKS_ALL_EXPEND_V — supplies the first branch of the UNION ALL: project_id, task_id, task_number, task_name, a concatenated displayed_field, and chargeable_flag.
  • PA_PROJECTS_ALL_EXPEND_V and PA_PROJECT_UTILS — provide the project-level context, including the project_id used in the second branch.
  • PJM_PROJECT_PARAMETERS and PJM_ORG_PARAMETERS — determine whether the synthetic project-level row is emitted, via project_control_level = 1.
  • FND_PROFILE — resolves the MFG_ORGANIZATION_ID profile option so the correct operating organization's parameters are evaluated.
  • FND_MESSAGE_CACHE — retrieves the localized "MXFR-PROJECT LEVEL" message text used as the display value for the synthetic row.
  • PA_SECURITY — enforces project security over the PA expenditure views referenced by the definition.

The second branch is emitted as literal values: project_id is taken from PJM_PROJECT_PARAMETERS, task_id is 0, and the displayed fields are the cached message string, with a hard-coded chargeable_flag of 'Y'.

Key Columns

  • PROJECT_ID — the project identifier; sourced from PA_TASKS_ALL_EXPEND_V for real tasks and from PJM_PROJECT_PARAMETERS for the synthetic row.
  • TASK_ID — the task identifier, or 0 when the row represents project-level activity.
  • TASK_NUMBER — the task number for real tasks; the localized project-level message for the synthetic row.
  • TASK_NAME — the descriptive task name; mirrors the message for the project-level row.
  • DISPLAYED_FIELD — a concatenation of task_number and task_name in the form "number (name)", providing a ready-to-render LOV label.
  • CHARGEABLE_FLAG — indicates whether the task may receive charges; the first branch carries the flag from PA_TASKS_EXPEND_V, while the project-level row is stamped 'Y'.
  • SELECTION — a literal 'N' in both branches, used as a selection indicator by the consuming form.

Users searching for chargeable_flag will find it defined on both branches, with the project-level row unconditionally chargeable.

Common Use Cases and Queries

Typical consumers include Project Manufacturing transfer entry forms, expenditure entry screens, and custom LOV implementations that need a uniform task picker. A common query retrieves all chargeable tasks for a project:

  • SELECT project_id, task_id, task_number, task_name, displayed_field FROM apps.pjm_tasks_mxfr_v WHERE project_id = :project_id AND chargeable_flag = 'Y';
  • SELECT * FROM apps.pjm_tasks_mxfr_v WHERE task_id = 0; — isolates the project-level synthetic row for organizations using project control level 1.
  • SELECT task_number, displayed_field FROM apps.pjm_tasks_mxfr_v WHERE project_id = :project_id ORDER BY task_number; — populates a standard LOV without applying a chargeability filter.

Because project security is inherited from PA_SECURITY and the PA expenditure views, results are automatically restricted to projects the querying responsibility is authorized to access.