Results for “benbv_cwb_summary_v”

15 results




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

Overview

BENBV_CWB_SUMMARY_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, belonging to the Advanced Benefits (BEN) product family. Its stated purpose in the ETRM metadata is to capture the summary for Compensation Workbench, the component of Advanced Benefits used to distribute compensation allocations, budgets, and worksheet results across eligible populations. The view surfaces one row per Compensation Workbench summary record, exposing eligibility counts, employee receipt counts, salary values, worksheet and budget totals, recommendation minimums and maximums, and miscellaneous value buckets, each expressed in both "Direct" and "All" variants.

Because the view is defined with WITH READ ONLY over the BEN_CWB_SUMMARY synonym, it is intended strictly for query and reporting purposes rather than for transactional maintenance. It is typically consumed by Concurrent Manager reports, Oracle Business Intelligence Publisher (BI Publisher) data models, and custom extracts that need aggregated Compensation Workbench statistics without joining to the many underlying detail tables.

Underlying Base Objects

The documented view text is a flat SELECT from the base table BEN_CWB_SUMMARY (referenced through its APPS synonym), aliased as CWB. Two functional columns are derived at runtime through the BEN_BIS_UTILS package:

The remaining columns are direct projections of BEN_CWB_SUMMARY columns, including the WHO audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE) and the key identifier columns (SUMMARY_ID, GROUP_PER_IN_LER_ID, GROUP_PL_ID, GROUP_OIPL_ID, PERSON_ID). The reliance on the BEN_BIS_UTILS function calls means the view is not a simple rename projection; performance can be affected by function execution on each row, particularly in large summary sets.

Key Columns

The columns are organized into count, value, and identity groups:

  • STATUS — the status of the Compensation Workbench summary record.
  • ELIG_COUNT_DIRECT / ELIG_COUNT_ALL — number of eligible persons, direct versus all-inclusive (including indirect/rolled-up reporting lines).
  • EMP_RECV_COUNT_DIRECT / EMP_RECV_COUNT_ALL — number of employees who received a compensation award, direct versus all. This is the column a user searching "emp_recv_count_direct" is querying.
  • ELIG_SAL_VAL_DIRECT / ELIG_SAL_VAL_ALL — eligibility salary values, direct and all.
  • WS_VAL_*, WS_BDGT_VAL_*, WS_BDGT_ISS_VAL_* — worksheet value, worksheet budget value, and worksheet budget issued value, in direct and all variants.
  • BDGT_VAL_DIRECT / BDGT_ISS_VAL_DIRECT — budget value and budget issued value (direct only).
  • STAT_SAL_VAL_*, OTH_COMP_VAL_*, TOT_COMP_VAL_* — statutory salary, other compensation, and total compensation values in direct and all variants.
  • REC_VAL_*, REC_MN_VAL_*, REC_MX_VAL_* — recommended value, recommended minimum, and recommended maximum.
  • MISC1_VAL_* through MISC3_VAL_* — three configurable miscellaneous value buckets.
  • Identity columns — SUMMARY_ID, GROUP_PER_IN_LER_ID, GROUP_PL_ID, GROUP_OIPL_ID, PERSON_ID, and LF_EVT_OCRD_DT (the last effective event occurred date).

Common Use Cases and Queries

The view is commonly used to validate Compensation Workbench processing before or after running workbook reports, to reconcile recipient counts against eligibility counts, and to feed downstream analytics.

  • Confirming distribution of awards across a plan:
SELECT status,
       emp_recv_count_direct,
       emp_recv_count_all,
       elig_count_direct,
       elig_count_all
  FROM apps.benbv_cwb_summary_v
 WHERE group_pl_id = :p_group_pl_id;
  • Budget consumption analysis:
SELECT group_plan,
       ws_bdgt_val_direct,
       ws_bdgt_iss_val_direct,
       bdgt_val_direct,
       bdgt_iss_val_direct
  FROM apps.benbv_cwb_summary_v
 WHERE summary_id = :p_summary_id;
  • Auditing changes over time using the WHO columns:
SELECT group_plan, emp_recv_count_direct,
       last_update_date, last_updated_by
  FROM apps.benbv_cwb_summary_v
 WHERE last_update_date >= :p_since_date;

Because the view is read-only and calls BEN_BIS_UTILS functions, reports should filter aggressively on GROUP_PL_ID, GROUP_OIPL_ID, or SUMMARY_ID to limit row-level function evaluation.