Search Results new_attribute_value_v

Overview

PA_MU_DETAILS_V is an APPS-owned reporting view in the Oracle Projects (PA) module, delivered in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to display detail information for a batch created by the Mass Update of a project or task attribute. The Mass Update process allows users to change a single attribute—most commonly the carrying-out organization—across many projects or tasks in one operation, and each such operation is tracked by a batch identifier. PA_MU_DETAILS_V exposes the processed lines of those batches, combining the raw update staging rows with descriptive project, task, and organization data so that the outcome of the batch can be reviewed and reconciled.

The view is read-only and is intended for inquiry, reporting, and integration rather than for the mass update transaction itself. It is described in the ETRM documentation as "Retrofitted," indicating that it was brought forward to remain available and valid in the documented 12.2.2 environment while continuing to serve 12.1.1 installations.

Underlying Base Objects

The view is defined over a join across several documented base objects. The driving table is PA_MASS_UPDATE_DETAILS (referenced through a synonym), which stores the individual line-level records for each batch, including old and new attribute values, update and recalculation flags, and any rejection reason. PA_PROJECTS and PA_TASKS supply the project and task context, with the task join expressed as an outer join so that lines applying only to a project are not lost.

Three instances of HR_ORGANIZATION_UNITS (aliased) are joined to translate stored organization identifiers into organization names: one for the old attribute value, one for the new attribute value, and one for the project's carrying-out organization. Note that these joins rely on TO_NUMBER conversions of OLD_ATTRIBUTE_VALUE and NEW_ATTRIBUTE_VALUE, which is a characteristic that affects query performance. The view also references the packages PA_SECURITY, HR_SECURITY, and HR_GENERAL. PA_SECURITY.ALLOW_UPDATE is invoked with the project identifier to determine whether the current user is permitted to update the project, and HR_SECURITY is referenced for organization-level security in the organization lookup context. Documented referenced base objects therefore include PA_MASS_UPDATE_DETAILS, PA_PROJECTS, PA_TASKS, HR_ORGANIZATION_UNITS, and the PA_SECURITY, HR_SECURITY, and HR_GENERAL packages.

Key Columns

• ROW_ID, BATCH_ID, LINE_ID — Identifiers for the detail row, the mass update batch, and the line within that batch.
• PROJECT_ID, TASK_ID, TASK_NAME — The project and task being updated, with the task name for readability.
• PROJECT_NAME, PROJECT_ORGANIZATION_ID, PROJECT_ORGANIZATION_NAME — Project description and its carrying-out organization.
• OLD_ATTRIBUTE_VALUE, NEW_ATTRIBUTE_VALUE — The prior and proposed values of the attribute being mass updated, typically organization identifiers.
• OLD_ATTRIBUTE_VALUE_V, NEW_ATTRIBUTE_VALUE_V — The resolved organization names corresponding to the old and new values.
• UPDATE_FLAG, RECALCULATE_FLAG — Control indicators showing whether the line was applied and whether related project data requires recalculation; these are the columns commonly sought when diagnosing batch behavior.
• REJECTION_REASON, REJECTED_FLAG — The reason a line was rejected and a decoded 'Y'/'N' indicator derived from REJECTION_REASON.
• ALLOW_UPDATE — The result of PA_SECURITY.ALLOW_UPDATE for the project, reflecting the current user's update authority.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include reviewing the results of a mass update batch, identifying rejected lines before committing changes, and auditing which projects had an attribute changed and when. The RECALCULATE_FLAG column is frequently filtered when investigating whether dependent project data was flagged for recalculation.

The following query lists the lines of a specific batch with their update outcome:

• SELECT batch_id, line_id, project_id, task_id, old_attribute_value_v, new_attribute_value_v, update_flag, recalculate_flag, rejected_flag, rejection_reason FROM pa_mu_details_v WHERE batch_id = :p_batch_id ORDER BY line_id;

To review all pending or errored lines where recalculation was requested:

• SELECT batch_id, project_name, task_name, recalculate_flag, rejection_reason FROM pa_mu_details_v WHERE recalculate_flag = 'Y' ORDER BY batch_id, line_id;

Because the view performs TO_NUMBER conversion joins and calls a security package, queries should generally filter by BATCH_ID or PROJECT_ID to keep execution efficient.