Search Results ben_copy_entity_results

Overview

BEN.BEN_COPY_ENTITY_RESULTS is a transaction table within the Oracle E-Business Suite Advanced Benefits (BEN) module, explicitly documented as the "Copy Entity Results transaction table for plan design wizard." Its role is to capture the outcome of copy operations performed through the Plan Design Wizard, which allows administrators to replicate benefit plan configurations, eligibility rules, and related entities across plan years or organizational contexts. Each row represents a discrete result record produced when a copy entity transaction is executed, recording what was copied, how many copies were made, and how source and target entities relate hierarchically.

The object is owned by the BEN schema and is marked VALID in the ETRM 12.2.2 physical schema, containing 313 documented columns. In Oracle EBS 12.1.1 and 12.2.2, this table is internal to the Plan Design Wizard processing framework and is not typically exposed through a public API; it is primarily accessed by concurrent programs and diagnostic queries during plan design copy operations. The heuristic Data Vault classification mined from the foreign key structure is standalone, suggesting it can be modeled as an independent structure without hub, link, or satellite decomposition — a modeling suggestion rather than an enforced design.

Key Information Stored

The table's surrogate primary key is COPY_ENTITY_RESULT_ID, enforced via the unique index BEN_COPY_ENTITY_RESULTS_PK. Two additional system-generated indexes (SYS_IL0000323558C00293$$ and SYS_IL0000323558C00313$$) exist on LOB columns. The most significant columns include:

• COPY_ENTITY_TXN_ID – foreign key linking each result to its parent transaction in PQH_COPY_ENTITY_TXNS.
• TABLE_ROUTE_ID – foreign key to PQH_TABLE_ROUTE, identifying the routing definition governing the copy.
• SRC_COPY_ENTITY_RESULT_ID and MIRROR_ENTITY_RESULT_ID – self-referencing identifiers tracing source and mirrored result records.
• RESULT_TYPE_CD – classifies the nature of the copy result.
• NUMBER_OF_COPIES – quantifies how many entity instances were duplicated.
• PARENT_ENTITY_RESULT_ID, PD_PARENT_ENTITY_RESULT_ID, GS_PARENT_ENTITY_RESULT_ID – hierarchy pointers distinguishing plan design and general structure parentage.
• TABLE_NAME, TABLE_ALIAS, PARENT_TABLE_ALIAS – identify the physical tables affected by the copy.
• STATUS and DML_OPERATION – capture processing state and the DML verb applied.
• DATETRACK_MODE, INFORMATION_TYPE, INFORMATION_CATEGORY – metadata describing how dated information was handled.
• The INFORMATION1–INFORMATION325 generically named columns store entity-specific attribute values.
• Standard WHO columns: OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE.

Common Use Cases and Queries

Typical scenarios include auditing a completed plan design copy, tracing which tables were modified, and diagnosing partial or failed copies by inspecting STATUS and DML_OPERATION. A representative query joins results to their parent transaction:

• SELECT r.copy_entity_result_id, r.table_name, r.status, r.number_of_copies FROM ben.ben_copy_entity_results r WHERE r.copy_entity_txn_id = :txn_id;
• Hierarchy traversal: SELECT * FROM ben.ben_copy_entity_results START WITH copy_entity_result_id = :id CONNECT BY PRIOR copy_entity_result_id = parent_entity_result_id;
• Reconciliation: count results per transaction to confirm expected copy scope.

Related Objects

• PQH_COPY_ENTITY_TXNS – joined on COPY_ENTITY_TXN_ID; the parent transaction header.
• PQH_TABLE_ROUTE – joined on TABLE_ROUTE_ID; defines copy routing rules.
• BEN_COPY_ENTITY_RESULTS (self) – referenced through SRC_ and MIRROR_ENTITY_RESULT_ID and PARENT_ENTITY_RESULT_ID.
• BEN_PL_* plan design tables – the target entities whose copies these results describe.
• Plan Design Wizard concurrent programs in the BEN module that populate this table.