Search Results new_attribute_value_v

Overview

APPS.PA_MU_DETAILS_V is a supplementary Oracle E-Business Suite view owned by the APPS schema that supports the Project Resource Management mass update (MU) functionality. In the Oracle Projects architecture, mass updates allow project administrators to modify a defined set of project or task attributes across many records in a single batch. PA_MASS_UPDATE_DETAILS stores the individual line-level results of those batches, and PA_MU_DETAILS_V exposes that data in a reporting-friendly, denormalized form.

The view is classified by Oracle as a supplementary view intended to simplify Oracle Forms coding, and the standard Oracle restriction applies: direct querying or modification of this view is not recommended, as its definition may change substantially between minor or major releases. Despite that caveat, it remains useful for diagnostic, reconciliation, and reporting queries, provided consumers accept the stability risk. Its name and the presence of OLD_ATTRIBUTE_VALUE_V and NEW_ATTRIBUTE_VALUE_V, combined with the ALLOW_UPDATE column, indicate it was designed to feed a validation and review form where an end user inspects each mass-update line, sees the previous and proposed values, and decides whether the change may proceed.

Underlying Base Objects

The documented dependencies of PA_MU_DETAILS_V are APPS.PA_MASS_UPDATE_DETAILS (the driving base table for mass-update lines), APPS.PA_PROJECTS, APPS.PA_TASKS, HR_ORGANIZATION_UNITS, and the PL/SQL packages HR_GENERAL, HR_SECURITY, and PA_SECURITY. The base table objects PA_MASS_UPDATE_DETAILS, PA_PROJECTS, and PA_TASKS are referenced through APPS synonyms that resolve to the underlying PA tables.

The view joins mass-update detail rows to their project and task records to resolve PROJECT_NAME and TASK_NAME, and to HR_ORGANIZATION_UNITS to resolve PROJECT_ORGANIZATION_NAME. The security packages are invoked so that row-level access respects operating unit, project, and organization security profiles. HR_SECURITY and HR_GENERAL supply organization classification and security predicates. The view is not referenced by any other database object, confirming its role as a terminal presentation layer for user-facing forms rather than a building block for further logic.

Key Columns

• BATCH_ID, LINE_ID — Identify the mass-update batch and the individual line within it; the primary grouping keys for reporting.
• PROJECT_ID, TASK_ID — Foreign keys to the affected project and task.
• OLD_ATTRIBUTE_VALUE, NEW_ATTRIBUTE_VALUE (VARCHAR2 150) and OLD_ATTRIBUTE_VALUE_V, NEW_ATTRIBUTE_VALUE_V (VARCHAR2 240) — Stored and validated/display forms of the before-and-after attribute values. The "_V" columns are the returned or validated representations used for display.
• UPDATE_FLAG, RECALCULATE_FLAG, REJECTED_FLAG — Status indicators controlling whether the line applies an update, triggers recalculation, or was rejected during the mass-update run.
• REJECTION_REASON — Free-text explanation when a line fails validation.
• ALLOW_UPDATE — A large (4000-byte) column indicating whether the current user is permitted to apply the change; it typically carries a form-level allow/deny result.
• TASK_NAME, PROJECT_NAME, PROJECT_ORGANIZATION_ID, PROJECT_ORGANIZATION_NAME — Descriptive join results for reporting without additional lookups.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and ROW_ID (ROWID).

Common Use Cases and Queries

Typical uses include auditing which mass-update lines were rejected and why, comparing old versus proposed attribute values before committing a batch, and building reports of mass-update activity by project organization.

SELECT batch_id, line_id, project_name, task_name,
       old_attribute_value_v, new_attribute_value_v,
       rejected_flag, rejection_reason
FROM   apps.pa_mu_details_v
WHERE  batch_id = :p_batch_id
ORDER  BY line_id;

SELECT project_organization_name, COUNT(*)
FROM   apps.pa_mu_details_v
WHERE  rejected_flag = 'Y'
GROUP  BY project_organization_name;

Because the view enforces HR and PA security, results are automatically filtered to the organizations and projects the querying user may access. For high-volume or integration scenarios, Oracle's guidance to avoid this view should be respected and the base PA_MASS_UPDATE_DETAILS table queried instead.