Search Results mass_update_forecast_items

Overview

APPS.PA_MASS_TXN_ASGMT_SUCCESS_V is a reporting view in Oracle E-Business Suite (12.1.1 and 12.2.2) that exposes successfully processed mass transaction records originating from the Oracle Project Resource Management mass update and mass assignment workflows. The view filters the Oracle Workflow process detail table to isolate only those workflow instances whose final process status is a success ("S"), providing a clean, business-facing list of transactions that completed without error. Because mass assignment and mass update operations execute as workflow-driven background processes, end users and administrators require a reliable mechanism to confirm which of the submitted transactions actually completed. This view serves that confirmatory role when the search term "mass_submit_for_approval" is used, since the MASS_SUBMIT_FOR_APPROVAL workflow type is one of the enumerated workflow types surfaced by the view.

The view belongs to the APPS schema and is documented in ETRM as a standard, supported object. It is typically consumed by concurrent program reports, OAF-based mass update pages, and custom integrations that need to reconcile the outcome of bulk workflow submissions against the originating transactions.

Underlying Base Objects

The view is defined solely over PA_WF_PROCESS_DETAILS (referenced in ETRM as a synonym). PA_WF_PROCESS_DETAILS is the Oracle Projects workflow process tracking table that records each workflow process instance generated by the mass transaction framework, including its workflow type, item identifiers, object identifiers, and process status. The view applies two restricting predicates against that table:

• WF_TYPE_CODE IN a fixed set of six values: MASS_ASGMT, MASS_UPDATE_ASGMT_BASIC_INFO, MASS_UPDATE_COMPETENCIES, MASS_UPDATE_FORECAST_ITEMS, MASS_SUBMIT_FOR_APPROVAL, and MASS_UPDATE_SCHEDULE.
• PROCESS_STATUS_CODE = 'S', restricting output to successful processes only.

Because the view is a thin projection over a single base object, no joins are required and query performance is governed entirely by the indexing of PA_WF_PROCESS_DETAILS on WF_TYPE_CODE and PROCESS_STATUS_CODE.

Key Columns

The view exposes four columns, one of them derived:

• ITEM_TYPE — the workflow item type identifying the process category.
• ITEM_KEY — the workflow item key, uniquely identifying the individual workflow instance associated with the mass transaction.
• WF_TYPE_CODE — the mass transaction workflow type, distinguishing mass assignment, competency updates, forecast item updates, schedule updates, and mass submit for approval.
• DECODE(WF_TYPE_CODE, 'MASS_ASGMT', OBJECT_ID2, OBJECT_ID1) — a conditional expression that returns OBJECT_ID2 when the workflow type is MASS_ASGMT and OBJECT_ID1 in all other cases. This normalization presents a single, consistent "object identifier" column regardless of which identifier slot the workflow type populates, simplifying downstream consumption.

Common Use Cases and Queries

The primary use case is confirming success of bulk-submitted workflow operations, particularly MASS_SUBMIT_FOR_APPROVAL, so that approvals routed to project managers can be reconciled against the items that were actually submitted. A representative query restricting to approval submissions is:

SELECT item_type, item_key, wf_type_code FROM apps.pa_mass_txn_asgmnt_success_v WHERE wf_type_code = 'MASS_SUBMIT_FOR_APPROVAL';

Another common pattern lists all successful mass transactions by type to produce an operational audit of completed background processing:

SELECT wf_type_code, COUNT(*) FROM apps.pa_mass_txn_asgmnt_success_v GROUP BY wf_type_code ORDER BY wf_type_code;

Because the view already excludes failed or in-progress processes, it is frequently joined to project, resource, or assignment tables via the item key to enrich reporting on which resources or assignments were successfully processed. It is also used to drive exception reporting by comparing submitted counts against successful counts returned here.