Search Results benbv_pl_v




Overview
Explore in AI Chat

Overview

BENBV_PL_V is a business view owned by the APPS schema in Oracle E-Business Suite Advanced Benefits (BEN). It exposes the definition of a plan — a discrete and formally defined compensation offering that is categorized by exactly one plan type. In the BEN data model, the plan is the central configuration object: participation in a benefits program is expressed through plans, and eligibility, rates, coverage limits, enrollment rules, and COBRA provisions are all configured at the plan level.

The view is a reporting and integration façade over the plan definition. Rather than requiring external consumers to resolve Decode lookups, descriptive flexfields, group plan hierarchies, and date-tracked effective ranges manually, BENBV_PL_V presents a flattened, user-meaningful projection of the plan record. Because the view name carries the "BV" (business view) prefix rather than the transactional table name, it is intended for read-only consumption by reports, extracts, interfaces, and downstream integrations. The view status is VALID in ETRM 12.2.2, and the same definition applies to 12.1.1, as the underlying BEN_PL_F entity and the BEN_BIS_UTILS and HR_BIS packages are common to both releases.

Underlying Base Objects

The documented base objects referenced by the view are:

  • BEN_PL_F (SYNONYM) — the date-tracked plan definition entity from which the columns prefixed PLN. are sourced. This is the primary driving object of the view.
  • HR_BIS (PACKAGE) — supplies BIS_DECODE_LOOKUP, used to translate code columns into their display meanings.
  • BEN_BIS_UTILS (PACKAGE) — supplies GET_GROUP_PL_NAME, used to resolve the group plan name from GROUP_PL_ID.

Every row in the view corresponds to a plan version bounded by EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, consistent with the effective-dated design of BEN_PL_F.

Key Columns

Common Use Cases and Queries

Typical uses include plan catalog reports, eligibility-to-plan extracts, enrollment configuration audits, and integration payloads where plan codes must be resolved to display values.

List all currently effective plans with their decoded plan code:

  • SELECT name, short_name, pl_cd, order_num FROM apps.benbv_pl_v WHERE TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date ORDER BY order_num;

Retrieve a plan's coverage and enrollment constraints by name:

  • SELECT name, mn_cvg_alwd_amt, mx_cvg_alwd_amt, mn_opts_rqd_num, mx_opts_alwd_num, enrt_rl FROM apps.benbv_pl_v WHERE name = :p_plan_name AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;

Filter by group plan using the resolved name for reporting over a specific date:

  • SELECT name, group_pl_id, legislative_code FROM apps.benbv_pl_v WHERE TRUNC(:p_as_of_date) BETWEEN effective_start_date AND effective_end_date;

Because the view is a read-only projection, it should always be queried with an effective-date predicate to return exactly one row per plan version.