Results for “opt_count”

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

Overview

BENBV_CWB_PL_DSGN_V is a business intelligence (BI) style view owned by the APPS schema in Oracle E-Business Suite, belonging to the BEN (Advanced Benefits) product family. Its purpose, as documented in the ETRM metadata, is to capture Plan Design for Compensation Workbench. In other words, it consolidates the configuration attributes that govern how a Compensation Workbench plan behaves during a compensation cycle — enrolment periods, rounding rules, unit-of-measure settings, approval modes, budget tolerances, and non-monetary configuration parameters.

The view is exposed to reporting and integration consumers so that plan-design metadata can be queried without navigating the normalized underlying compensation tables. Because it decodes many code columns into their meaningful lookup descriptions, it is particularly well suited for operational reports, data extracts, and downstream integration into planning or analytics platforms. It is not a transactional view; it describes the design of a plan rather than allocations, awards, or individual worker data.

Underlying Base Objects

The ETRM documentation lists the following referenced base objects for the view:

• BEN_CWB_PL_DSGN (SYNONYM) — the principal source of plan-design columns. It supplies the core attributes such as PL_UOM, APPROVAL_MODE, period dates, tolerance percentages, and the rounding code columns referenced in the view text.
• BEN_BIS_UTILS (PACKAGE) — a BIS utility package used within the view's SELECT text to resolve surrogate identifiers into descriptive names, for example GET_PL_NAME, GET_OIPL_NAME, GET_GROUP_PL_NAME, GET_GROUP_OIPL_NAME, and GET_OPT_NAME.
• HR_BIS (PACKAGE) — supplies the BIS_DECODE_LOOKUP function, which translates stored lookup codes into their display meanings.

The view therefore layers a naming/decoding transformation on top of a single primary plan-design source, with the two packages providing the decode and name-resolution logic at query time.

Key Columns

The view exposes a broad set of design attributes. Important columns include:

• Identification and dates: LF_EVT_OCRD_DT, EFFECTIVE_DATE, UPD_START_DT, UPD_END_DT, ENRT_PERD_START_DT, ENRT_PERD_END_DT, YR_PERD_START_DT, YR_PERD_END_DT, DATA_FREEZE_DATE.
• Plan identity: NAME, plus derived names via GET_PL_NAME and GET_OIPL_NAME.
• Rounding codes: WS_RNDG_CD, DIST_BDGT_RNDG_CD, WS_BDGT_RNDG_CD, RSRV_RNDG_CD, ELIG_SAL_RNDG_CD — each decoded against the BEN_RNDG lookup. The user's search term ws_bdgt_rndg_cd corresponds directly to the worksheet budget rounding code column.
• Units of measure: PL_UOM and the many *_NNMNTRY_UOM columns covering worksheet, distribution budget, reservation, eligibility salary, recurring, and total compensation measures.
• Tolerances: BDGT_OVER_BUDGET_TOLERANCE_PCT and WS_OVER_BUDGET_TOLERANCE_PCT.
• Operational settings: APPROVAL_MODE, PL_ORDR_NUM, OIPL_ORDR_NUM, OPT_COUNT.

Common Use Cases and Queries

Typical uses include auditing rounding configuration across plans, comparing budget tolerance settings, and extracting plan-design metadata for reporting. A representative query listing rounding codes and their decoded meanings is:

• SELECT name, effective_date, ws_rndg_cd, ws_bdgt_rndg_cd FROM apps.benbv_cwb_pl_dsgn_v;
• SELECT lf_evt_ocrd_dt, pl_uom, approval_mode, bdgt_over_budget_tolerance_pct FROM apps.benbv_cwb_pl_dsgn_v WHERE legislation_code = 'US';

Because decoding occurs through the BIS packages, consumers should expect the view to execute those functions per row, so querying it selectively and filtering on indexed driving columns is advisable in high-volume extracts.