Search Results process_run_date

Overview

PA_MASS_UPDATE_BATCHES is a Multi-Org secured view in the Oracle Projects (PA) module, retrofitted for Oracle E-Business Suite releases 12.1.1 and 12.2.2. It presents mass update batch definitions and their processing outcomes, allowing project administrators and batch-processing programs to review the grouping criteria, status, and results of bulk attribute updates applied across multiple projects or project records. The view is documented as the Multi-Org wrapper for the underlying table PA_MASS_UPDATE_BATCHES_ALL, ensuring that only the rows belonging to the operating unit of the current session are visible to the querying user.

From a reporting and integration standpoint, PA_MASS_UPDATE_BATCHES is the read-only interface used by concurrent programs, forms, and custom extracts that need to inspect how a mass update was defined and whether it completed successfully. Because the view applies an operating-unit (ORG_ID) filter derived from the user's client information, it is the recommended access point rather than querying the _ALL table directly.

Underlying Base Objects

The view is defined over a single documented base table:

• PA_MASS_UPDATE_BATCHES_ALL — the base table storing mass update batch headers, including the batch identity, criteria, status, and audit columns.

The Multi-Org mechanism is implemented through the WHERE clause, which compares ORG_ID from the base table to the ORG_ID derived from USERENV('CLIENT_INFO'). The predicate is expressed as:

NVL(ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'), 1, 1), ' ', NULL, SUBSTRB(USERENV('CLIENT_INFO'), 1, 10))), -99)) equals the same expression evaluated on the session variable. Note that ETRM records "Not implemented in this database" for the implementation/DBA data section, meaning the view may not exist in every environment; where the business group or operating unit setup differs, the wrapper is created on demand. No additional referenced base objects are documented, so all other columns map directly to PA_MASS_UPDATE_BATCHES_ALL.

Key Columns

The view exposes the complete set of columns from the base table. The most significant include:

• BATCH_ID — Primary identifier for the mass update batch.
• BATCH_NAME — User-defined name identifying the batch.
• DESCRIPTION — Free-text description of the batch purpose.
• PROJECT_ATTRIBUTE — The project attribute targeted for update by the batch.
• BATCH_STATUS_CODE — Current processing state of the batch (for example, pending, processed, or rejected).
• PROCESS_RUN_DATE / PROCESS_RUN_BY — When the batch was processed and by which user.
• EFFECTIVE_DATE — The effective date applied to the mass update.
• REJECTION_CODE — Code indicating why a batch did not process successfully.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context identifying the request that created or processed the batch.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield segments for extensible, site-specific data.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard audit columns.

Common Use Cases and Queries

Typical scenarios include monitoring batch status before and after a mass maintenance run, diagnosing rejections, and feeding project-attribute audit reports. The following query lists recent batches with their processing outcome, with the ORG_ID predicate implicitly applied by the view:

SELECT batch_id, batch_name, batch_status_code, process_run_date, process_run_by, rejection_code FROM pa_mass_update_batches WHERE batch_status_code = 'REJECTED' ORDER BY process_run_date DESC;

A second common pattern joins concurrent request information to trace the program that generated the batch:

SELECT m.batch_name, m.batch_status_code, r.request_id, r.requested_start_date FROM pa_mass_update_batches m, fnd_concurrent_requests r WHERE m.request_id = r.request_id AND m.effective_date >= SYSDATE - 30;

Because the view enforces operating-unit security, users must ensure their session is initialized to the intended operating unit; otherwise the ORG_ID comparison falls back to the -99 sentinel and may return no rows. Direct access to PA_MASS_UPDATE_BATCHES_ALL should be avoided for reporting, as it bypasses this security filter.