Results for “pa_mass_update_details”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_MASS_UPDATE_DETAILS is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores line-level detail for batches created during the mass update of project and task attributes. Where the parent batch record establishes the intent and scope of a mass maintenance run, this table captures each individual project or task targeted by that run, together with the attribute values before and after the change and the outcome of processing.

From a Data Vault modeling perspective, the FK topology suggests this object is best classified as a link table. It sits at the intersection of a batch, a project, and a task, resolving the many-to-many relationship between mass update batches and the project/task hierarchies they affect. A link classification is consistent with the presence of three foreign keys pointing to unrelated parent entities.

Key Information Stored

The table contains 14 documented columns. The most significant are listed below.

• BATCH_ID — Foreign key to PA_MASS_UPDATE_BATCHES_ALL identifying the parent mass update batch.
• LINE_ID — Line identifier within a batch; together with BATCH_ID it forms the unique index PA_MASS_UPDATE_DETAILS_U1.
• PROJECT_ID — Foreign key to PA_PROJECTS_ALL identifying the project affected.
• TASK_ID — Foreign key to PA_TASKS identifying the task affected.
• OLD_ATTRIBUTE_VALUE — The attribute value prior to the mass update.
• NEW_ATTRIBUTE_VALUE — The attribute value applied by the mass update.
• UPDATE_FLAG — Indicates whether the line is to be updated.
• RECALCULATE_FLAG — Indicates whether dependent calculations should be re-run.
• REJECTION_REASON — Reason a line was rejected during processing.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard audit columns.

Two unique indexes act as business-key candidates: PA_MASS_UPDATE_DETAILS_U1 (BATCH_ID, LINE_ID) and PA_MASS_UPDATE_DETAILS_U2 (BATCH_ID, PROJECT_ID, TASK_ID). The latter guarantees that a given project/task combination appears only once per batch.

Common Use Cases and Queries

Typical scenarios include auditing attribute changes applied via mass update, diagnosing rejected lines, and reporting on batch scope. A common query retrieves all detail lines for a batch:

• SELECT line_id, project_id, task_id, old_attribute_value, new_attribute_value, update_flag, rejection_reason FROM pa_mass_update_details WHERE batch_id = :batch_id ORDER BY line_id;
• Join to PA_PROJECTS_ALL and PA_TASKS to resolve project and task names for user-facing reports.
• Filter on rejection_reason IS NOT NULL to isolate failed lines for remediation.

Related Objects

• PA_MASS_UPDATE_BATCHES_ALL — Parent batch table; joined on BATCH_ID.
• PA_PROJECTS_ALL — Project master; joined on PROJECT_ID.
• PA_TASKS — Task master; joined on TASK_ID.
• PA_PROJECTS_VL / PA_TASKS_VL — Multilingual views supplying translated names.
• Mass update concurrent programs in the PA module consume this table as their processing worklist.