Results for “pa_mass_update_batches_s”

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

Overview

PA_MU_BATCHES_V_PKG is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that supports the Mass Update (MU) feature in Oracle Projects. Mass Update provides a mechanism for applying bulk changes to large numbers of project, task, and project element records without opening each record individually. The _V_ naming convention indicates that this package is associated with a database view (PA_MU_BATCHES_V) exposed through the Oracle Forms interface for the Mass Update Batches window; the package encapsulates the DML logic and the row-level locking and processing behaviour required by that form and by the underlying concurrent processing framework.

The package operates on mass update batch headers, their language-related shadow table, and the mass update detail lines, and it additionally validates the project, task, and project element references that a batch is expected to affect. In ETRM 12.2.2 metadata it is classified as API classification OTHER and is recorded as VALID in the APPS schema.

Key Procedures and Functions

The documented package exposes six procedures, split between form-support DML routines and batch-processing routines.

• INSERT_ROW — Creates a new mass update batch header record, together with the corresponding row in the language shadow table PA_MASS_UPDATE_BATCHES_S, so the batch is retrievable through the view.
• UPDATE_ROW — Modifies the attributes of an existing mass update batch header, keeping the base table and its shadow table consistent.
• LOCK_ROW — Implements the Forms-compatible row-locking interface. It acquires and releases the cursor-level lock required so that the Oracle Forms block can enforce optimistic and pessimistic locking semantics during interactive editing.
• DELETE_ROW — Removes a mass update batch and its associated shadow-table row, respecting referential integrity with the batch detail records.
• PROC_CONC — Implements the concurrent-program hook, registering and invoking the package logic as a background process. This is the routine associated with submission of mass update batch processing from the concurrent manager.
• PROCESS — Performs the actual mass update execution: iterating over the batch detail lines in PA_MASS_UPDATE_DETAILS, resolving the affected project, task, or element, and applying the change using the adjustment and project utilities.

The metadata does not document parameter lists for these routines, and parameter signatures should be confirmed by inspecting the package specification in the target instance.

Tables Accessed

• PA_MASS_UPDATE_BATCHES — the base table of mass update batch headers, read and written by INSERT_ROW, UPDATE_ROW, and DELETE_ROW and processed by PROCESS.
• PA_MASS_UPDATE_BATCHES_S — the language shadow table for batch headers, maintained in step with the base table.
• PA_MASS_UPDATE_DETAILS — the batch detail lines that define the individual mass update actions applied during PROCESS.
• PA_PROJECTS_ALL — the project master, used to resolve and validate the projects targeted by a batch.
• PA_TASKS — task validation and resolution where a batch targets task-level data.
• PA_PROJ_ELEMENTS — project element validation for batches that act on elements.
• DUAL and PLITBLM — utility references used for PL/SQL constructs and Forms list handling.

The package additionally depends on PA_ADJUSTMENTS, PA_MOAC_UTILS, PA_PROJECT_UTILS2, PA_PROJECT_STUS_UTILS, PA_SECURITY, PA_UTILS, APP_EXCEPTION, FND_FUNCTION, FND_GLOBAL, FND_MESSAGE, and FND_MSG_PUB for the actual change application, security checking, and message handling.

Usage Notes

The DML procedures (INSERT_ROW, UPDATE_ROW, LOCK_ROW, DELETE_ROW) are invoked through the Oracle Forms Mass Update Batches window, where they back the block-level triggers and locking behaviour of the view-based block. PROC_CONC and PROCESS are invoked by the Mass Update concurrent program: the user defines a batch in the form, then submits it, and the concurrent request executes PROCESS to apply the changes. Because the package is not referenced by any other database object, it should be treated as a form- and concurrent-program-support package rather than a reusable public API. Customisations should avoid calling it directly; instead, custom logic should consume the documented public APIs for project adjustments and mass updates, or operate on the underlying tables in a controlled manner. Any direct dependency on this package risks breakage across 12.1.1 and 12.2.2 upgrades, since its interface is internal to the Mass Update feature.