Search Results object_id2

Overview

PA_MASS_TXN_ASGMT_SUCCESS_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Projects (PA) module. It exposes the set of Oracle Workflow process records that have completed successfully for a defined family of mass transaction operations performed against project assignments. The view is classified as VALID in the ETRM repository (12.1.1 / 12.2.2) and functions as a filtered, presentation-ready projection of the PA_WF_PROCESS_DETAILS table. Rather than requiring callers to reconstruct workflow completion state and to resolve which identifier column holds the assignment identifier, the view centralizes both concerns, providing a normalized interface for downstream reporting and integration.

Its principal design characteristic is a DECODE expression that harmonizes two different identifier storage conventions used by the underlying workflow records, exposing a single, consistently named ASSIGNMENT_ID column regardless of the originating workflow type.

Underlying Base Objects

The view is defined exclusively over the synonym PA_WF_PROCESS_DETAILS, which in turn resolves to the corresponding APPS base table that stores Oracle Workflow process detail records for Projects mass transaction processing. No other base tables, views, or joins are referenced in the documented view text.

The definition applies two filters against that base object:

• Workflow type restriction — only rows whose WF_TYPE_CODE falls within the mass transaction family are included: MASS_ASGMT, MASS_UPDATE_ASGMT_BASIC_INFO, MASS_UPDATE_COMPETENCIES, MASS_UPDATE_FORECAST_ITEMS, MASS_SUBMIT_FOR_APPROVAL, and MASS_UPDATE_SCHEDULE.
• Status restriction — only rows with PROCESS_STATUS_CODE = 'S' are returned, meaning the workflow process completed successfully.

Because the view is a straight projection with no aggregation or grouping, it preserves the one-row-per-workflow-process granularity of the base object.

Key Columns

• ITEM_TYPE — the Workflow item type identifying the category of process record; retained directly from the base table and useful for grouping and filtering by process classification.
• ITEM_KEY — the Workflow item key, uniquely identifying the individual workflow process instance. This is the natural key for tracing a specific mass transaction run.
• WF_TYPE_CODE — the mass transaction workflow type code. This column distinguishes which of the six supported mass operations generated the record and is the pivot used by the view's DECODE logic.
• ASSIGNMENT_ID — the derived identifier of the affected assignment. The DECODE assigns OBJECT_ID2 when WF_TYPE_CODE equals 'MASS_ASGMT', and OBJECT_ID1 for all other supported workflow types. This column is the reason the view exists: it presents a single assignment identifier column without requiring the caller to know which underlying OBJECT_ID column is populated.

Common Use Cases and Queries

The view is typically used to report on successfully processed assignment mass transactions, to reconcile workflow outcomes against assignment records, and to feed integration or interface processes that need a clean list of completed assignment identifiers. Typical scenarios include auditing competency or forecast item updates that have completed, and identifying assignments processed by a mass submission for approval.

Retrieve all successful mass transactions for a given workflow type:

• SELECT item_key, wf_type_code, assignment_id FROM pa_mass_txn_asgmt_success_v WHERE wf_type_code = 'MASS_ASGMT';

Count successful processes per operation type:

• SELECT wf_type_code, COUNT(*) FROM pa_mass_txn_asgmt_success_v GROUP BY wf_type_code;

Locate the workflow process associated with a specific assignment identifier:

• SELECT item_type, item_key, wf_type_code FROM pa_mass_txn_asgmt_success_v WHERE assignment_id = :p_assignment_id;

Where the user search term object_id1 is relevant, note that OBJECT_ID1 is not exposed directly; it is consumed inside the DECODE and surfaces to callers as ASSIGNMENT_ID for every workflow type except 'MASS_ASGMT'. Queries seeking OBJECT_ID1 semantics should therefore filter on WF_TYPE_CODE NOT equal to 'MASS_ASGMT' and select ASSIGNMENT_ID.