Search Results benbv_actl_prem_v




Overview
Explore in AI Chat

Overview

BENBV_ACTL_PREM_V is a concurrent-program-style database view owned by the APPS schema within the Oracle Advanced Benefits (BEN) module. In Oracle EBS 12.1.1 and 12.2.2, it serves as the presentation layer for actual premium records, exposing the descriptive and code columns of the underlying premium flexfield table in a form suitable for reporting, Oracle Business Intelligence (BIS) extractions, and integration with external payroll or carrier systems. The view is registered as VALID in the EBS Technical Reference Manual (ETRM), indicating it is a supported, active object in the standard product rather than a customization artifact.

The view's primary function is to join the raw premium definition stored in BEN_ACTL_PREM_F with human-readable lookup descriptions and derived object identifiers, so that report consumers receive decoded values rather than opaque codes. It also surfaces descriptive flexfield context information, enabling Tools and reporting layers to render the DFF segments attached to the BEN_ACTL_PREM_F entity.

Underlying Base Objects

The ETRM metadata for 12.2.2 documents three referenced base objects:

  • BEN_ACTL_PREM_F (referenced through a synonym) — the core table holding actual premium definitions, including effective dates, calculation rules, rates, limits, and code columns.
  • BEN_BIS_UTILS (PL/presumably PL/SQL package) — provides the GET_PL_NAME and GET_OIPL_NAME functions used to resolve the benefit plan or option-in-plan name for the premium's owning compensation object.
  • HR_BIS (package) — supplies BIS_DECODE_LOOKUP, used to translate each stored code into its meaning via the corresponding lookup type.

The view therefore does not create new data; it is a decoding and enrichment layer over BEN_ACTL_PREM_F. Because BEN_ACTL_PREM_F is referenced via a synonym, the effective data source remains the APPS-owned base table, and the view inherits its date-tracked (effective-dated) character directly from the driving table columns EFFECTIVE_START_DATE and EFFECTIVE_END_DATE.

Key Columns

The view exposes several categories of columns:

Common Use Cases and Queries

Typical scenarios include auditing premium configuration for a benefit plan, reconciling actual premium rates before payroll processing, and exporting premium definitions to carriers or benefits administration platforms. Because the view already decodes lookup values and resolves compensation object names, reports can avoid re-implementing lookup joins.

A representative query retrieves active premium definitions for a given plan and business group:

  • SELECT ACTL_PREM_ID, NAME, COMP_OBJECT, VAL, UOM, RT_TYP_CD, CR_LKBK_VAL
  • FROM APPS.BENBV_ACTL_PREM_V
  • WHERE BUSINESS_GROUP_ID = :p_bg_id
  • AND TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE;

Reporting layers should always filter on the effective date range, since the view exposes the full effective-dated history of BEN_ACTL_PREM_F. Joins back to BEN_ACTL_PREM_F on ACTL_PREM_ID remain valid when additional columns not exposed by the view are required.