Results for “result_type_cd”

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

Overview

PER_MASS_UPDATE_ASSIGNMENT_V is an APPS-owned database view within the PER (Human Resources) product family of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. Its documented purpose is to support the Mass Assignment Update user interface, the concurrent process flow through which HR administrators apply bulk changes to assignments for a selected population of employees. The view is marked VALID in the ETRM metadata, confirming that its underlying definition resolves successfully against the referenced base objects in the target environment.

Operationally, the view exposes the intermediate and final state of mass assignment processing. When a mass update is submitted, EBS stages each assignment change as a copy entity result row, keyed by COPY_ENTITY_RESULT_ID and COPY_ENTITY_TXN_ID. The view presents these rows together with a large block of positional attributes (INFORMATION1 through INFORMATION95) and a status and result type, giving the UI and concurrent programs a single flattened projection over the staging data. This makes it a reporting surface for tracking which assignment updates succeeded, which failed, and which parent result generated them.

Underlying Base Objects

The view is defined over the synonym PQH_COPY_ENTITY_RESULTS, which resolves to the underlying copy entity results table holding the staged assignment records for mass update transactions. It also references the FND_DATE package, used for canonical date conversion and formatting within the view definition.

Two date derivations are performed in the projection: INFORMATION65 transforms INFORMATION62 by converting the canonical value to a date and then to character format, treating the sentinel value '4712/12/31 00:00:00' as NULL. INFORMATION66 and INFORMATION67 similarly convert INFORMATION61 and INFORMATION58 to character-formatted dates. The remaining INFORMATION columns are exposed as-is, preserving the positional attribute model used by the mass update engine. Because the view sits directly on the documented synonym and package, it inherits no additional joins in the metadata, and its row granularity matches the copy entity results table.

Key Columns

• COPY_ENTITY_RESULT_ID — Primary identifier for a staged mass update result row.
• COPY_ENTITY_TXN_ID — Identifier of the parent mass update transaction to which the result belongs.
• SRC_COPY_ENTITY_RESULT_ID — Source result identifier, linking a result back to the originating record; this is the column referenced by the search term "src_copy_entity_result_id" and is central to lineage tracing.
• RESULT_TYPE_CD — Classifies the outcome/type of the staged result.
• STATUS — Processing status of the individual assignment update.
• INFORMATION_CATEGORY — Categorises the information payload held in the INFORMATION columns.
• INFORMATION1–INFORMATION95 — Positional attribute payload carrying the assignment data; INFORMATION58, INFORMATION61 and INFORMATION62 have derived date counterparts in INFORMATION65–67.

Common Use Cases and Queries

The view is principally queried to diagnose mass assignment update outcomes, reconcile which assignments were touched by a given transaction, and trace lineage via SRC_COPY_ENTITY_RESULT_ID. A typical query lists results for a transaction:

• SELECT copy_entity_result_id, copy_entity_txn_id, result_type_cd, status FROM per_mass_update_assignment_v WHERE copy_entity_txn_id = :txn_id;
• SELECT status, COUNT(*) FROM per_mass_update_assignment_v WHERE copy_entity_txn_id = :txn_id GROUP BY status;
• SELECT copy_entity_result_id, src_copy_entity_result_id FROM per_mass_update_assignment_v WHERE src_copy_entity_result_id IS NOT NULL;

These patterns are useful for confirming that a bulk assignment load completed, identifying failed rows that require reprocessing, and mapping derived results to their source records.