Search Results parent_entity_result_id




Overview
Explore in AI Chat

Overview

APPS.BEN_PLAN_DESIGN_HGRID_VW is a Web view in the Oracle E-Business Suite Advanced Benefits (BEN) module, documented with a VALID status and registered under the FND Design Data identifier BEN.BEN_PLAN_DESIGN_HGRID_VW. The view is classified as a "Web view designed to simplify access from Oracle Self-Service Web Applications," a category of database object that flattens and pre-joins base data so that Oracle Application Framework (OAF) pages and other self-service components can query it directly without embedding complex SQL. Its specific functional purpose is to display plan design information in a hierarchical format for the Plan Copy module. In practice, this means the view supplies the row-level data that drives the hierarchical grid of copyable plan design entities that an administrator sees when copying a benefit plan or plan design from one context to another. It therefore acts as a presentation-oriented reporting and integration surface rather than as a transactional table, and it is listed as referenced by the PUBLIC synonym BEN_PLAN_DESIGN_HGRID_VW.

Underlying Base Objects

The ETRM metadata documents exactly two referenced base objects: the synonym BEN_COPY_ENTITY_RESULTS and the view PQH_TABLE_ROUTE_VL. BEN_COPY_ENTITY_RESULTS is the transactional store of copy results produced by the Plan Copy engine; each row represents a copied or copyable entity, including its parent-child linkage and its association with a copy transaction. PQH_TABLE_ROUTE_VL is the validation/route view used to resolve table routing metadata, which supplies routing identifiers used by the copy process. BEN_PLAN_DESIGN_HGRID_VW joins these sources to present the copy result set in the hierarchy and ordering required by the Plan Copy user interface. Because the columns map almost one-to-one to BEN_COPY_ENTITY_RESULTS attributes, the view is best understood as a route-aware, hierarchical projection over the copy result table, enriched with the routing identifier drawn from PQH_TABLE_ROUTE_VL.

Key Columns

  • COPY_ENTITY_RESULT_ID (NUMBER) — Primary identifier of the copy entity result row; the primary key of the underlying result record.
  • COPY_ENTITY_TXN_ID (NUMBER, 15) — Identifies the copy transaction (batch) to which the result belongs, allowing all rows from a single copy operation to be grouped.
  • PARENT_ENTITY_RESULT_ID (NUMBER) — Self-referencing pointer to the parent result row; this column is what establishes the hierarchical tree rendered by the grid.
  • MIRROR_ENTITY_RESULT_ID (NUMBER) — Links a result to its mirrored counterpart, used where the copy process maintains parallel or shadowed entities.
  • NUMBER_OF_COPIES (NUMBER) — Quantity of copies requested or generated for the entity.
  • TABLE_ROUTE_ID (NUMBER, 15) — Routing identifier resolved through PQH_TABLE_ROUTE_VL that determines how the entity is processed.
  • NAME (VARCHAR2, 600) — Display name of the copyable entity, shown in the grid.
  • TYPE (VARCHAR2) — Classification of the entity within the plan design hierarchy.
  • SELECTION_DISABLED_FLAG (VARCHAR2) — Indicates entities that cannot be selected in the UI, typically because copying them is invalid or already handled.
  • CSS_STYLE (VARCHAR2, 16) — Presentation attribute used to style the grid row.
  • OBJECT_VERSION_NUMBER (NUMBER) — Optimistic locking column for concurrent update control.
  • INFORMATION8 (VARCHAR2, 30) — A generic descriptive attribute used by the Plan Copy UI.

Common Use Cases and Queries

The principal use case is retrieving the hierarchical list of entities for a given copy transaction so the Plan Copy page can render parent and child nodes. A typical query filters by transaction and orders within the tree:

SELECT copy_entity_result_id, parent_entity_result_id, name, type,
       number_of_copies, selection_disabled_flag
FROM   apps.ben_plan_design_hgrid_vw
WHERE  copy_entity_txn_id = :p_txn_id
ORDER BY parent_entity_result_id, name;

Because the view is a Web view with no DML capability, it should be used exclusively for query. A second common pattern is diagnostic: joining the view back to BEN_COPY_ENTITY_RESULTS or PQH_TABLE_ROUTE_VL to audit how table routes were resolved for a specific copy run, verifying that TABLE_ROUTE_ID values are consistent and that no entity was incorrectly flagged in SELECTION_DISABLED_FLAG. The COPY_ENTITY_RESULT_ID column is the reliable join key in both cases, and it is the identifier most frequently sought by users investigating Plan Copy results.