Search Results ben_copy_entity_txns




Overview

BEN.BEN_COPY_ENTITY_RESULTS is a transactional table in the Oracle E-Business Suite Benefits (BEN) schema. It functions as the copy entity results transaction table for the Plan Design Wizard, which is the setup utility used to copy or clone plan configurations, eligibility structures, and related entities across plan years or business groups. Each row records the outcome of a single entity-level copy operation, including the source entity, the mirror or target entity, hierarchy relationships, and the disposition of the copy (whether a row was copied or skipped).

The object is owned by the BEN schema, resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and is designated VALID in both Oracle EBS 12.1.1 and 12.2.2. The documented physical schema for 12.2.2 lists 313 columns, reflecting the wide, denormalized INFORMATIONn pattern characteristic of setup copy staging tables.

Applying a heuristic Data Vault classification, this object most closely resembles a satellite rather than a hub or link. It carries descriptive and transactional attributes about a copy operation, keyed by a system-generated surrogate identifier, with no independent business key of its own. This classification is a modeling suggestion derived from the documented FK structure and should not be treated as a physical design statement about the EBS schema itself.

Key Information Stored

The table is anchored by the surrogate primary key COPY_ENTITY_RESULT_ID (NUMBER(15)), enforced through the unique index BEN_COPY_ENTITY_RESULTS_PK. The documented unique indexes also include two LOB indexes, SYS_IL0000323558C00293$$ and SYS_IL0000323558C00313$$, which are system-managed LOB segments rather than business-key candidates.

Common Use Cases and Queries

Typical usage centers on diagnosis of Plan Design Wizard copy runs. Support and implementation teams query this table to determine why a particular entity was skipped, to trace hierarchy construction in the generated export file, or to reconcile a target plan against its source.

To inspect all result rows for a given copy transaction:

  • SELECT COPY_ENTITY_RESULT_ID, TABLE_NAME, TABLE_ALIAS, DML_OPERATION, STATUS, NUMBER_OF_COPIES FROM BEN.BEN_COPY_ENTITY_RESULTS WHERE COPY_ENTITY_TXN_ID = :txn_id ORDER BY ORDER_IN_HIERARCHY;
  • SELECT * FROM BEN.BEN_COPY_ENTITY_RESULTS WHERE TABLE_ALIAS = :alias AND PARENT_ENTITY_RESULT_ID = :parent_id; — walks the parent-child hierarchy via the index BEN_COPY_ENTITY_RESULTS_FK3.
  • SELECT * FROM BEN.BEN_COPY_ENTITY_RESULTS WHERE MIRROR_ENTITY_RESULT_ID = :id; — resolves the mirror mapping using BEN_COPY_ENTITY_RESULTS_FK2.
  • Counting skipped versus copied rows per table provides a quick success summary for a wizard run.

Related Objects

The documented foreign keys and index columns tie this table to several significant objects in the copy framework:

  • PQH_COPY_ENTITY_TXNS — Parent transaction table, joined on COPY_ENTITY_TXN_ID; the primary grouping object for a copy run.
  • PQH_TABLE_ROUTE — Referenced via TABLE_ROUTE_ID; defines how each entity table is routed during the copy.
  • BEN_COPY_ENTITY_RESULTS_PK / _F7 / _FK2 through _FK6 / _N1 — The indexes themselves, notably BEN_COPY_ENTITY_RESULTS_FK4 (COPY_ENTITY_TXN_ID, TABLE_ALIAS) and BEN_COPY_ENTITY_RESULTS_N1 (COPY_ENTITY_TXN_ID, TABLE_ALIAS, DML_OPERATION, PARENT_ENTITY_RESULT_ID, INFORMATION162), which support the query patterns above.
  • BEN.BEN_COPY_ENTITY_* family — Sibling result and definition tables used together by the Plan Design Wizard to stage and validate each entity copy.