Search Results benbv_per_cm_prvdd_v




Overview
Explore in AI Chat

Overview

The BENBV_PER_CM_PRVDD_V view is a business-facing database object in the Oracle E-Business Suite Advanced Benefits (BEN) module. Owned by the APPS schema and documented as VALID, it exposes a secured, read-only projection of communications activity for persons who have a life event in progress. Specifically, the view identifies two categories of correspondence: communications that must be provided to a participant with an active life event, and communications that have been requested by that participant.

In the Oracle EBS 12.1.1 and 12.2.2 release streams, BENBV_* views serve as the reporting and integration surface over the BEN tables and their _F (date-tracked) counterparts. This view is therefore typically consumed by concurrent reports, OAF-based self-service pages, XML Publisher extracts, and custom integrations that need to reconcile which life-event communications were triggered, dispatched, or requested. Because it is defined WITH READ ONLY, it is intended exclusively for retrieval rather than DML.

Underlying Base Objects

The view text reveals that BENBV_PER_CM_PRVDD_V is defined over two documented referenced objects: the synonym BEN_PER_CM_PRVDD_F and the package HR_BIS. The primary data source is BEN_PER_CM_PRVDD_F, the date-tracked ("_F") table that stores per-person communication provided records, keyed by PER_CM_PRVDD_ID and PER_CM_ID. The view aliases this table as PCD and applies a security predicate restricting rows to NVL(HR_BIS.GET_SEC_PROFILE_BG_ID, PCD.BUSINESS_GROUP_ID), so callers see only data for the business group returned by their security profile.

HR_BIS is an HR utility package invoked through the BIS_DECODE_LOOKUP function to translate stored code values into their lookup meanings. It is also the source of the GET_SEC_PROFILE_BG_ID security profile function used in the WHERE clause. A descriptive flexfield reference ('_DF:BEN:BEN_PER_CM_PRVDD_F:PCD') is also projected for context-sensitive flexfield reporting.

Key Columns

The view exposes date-effective and lifecycle attributes, decoded meanings, and surrogate keys:

Common Use Cases and Queries

Typical scenarios include auditing life-event correspondence, confirming which communications were requested versus mandated, and feeding downstream notification or compliance extracts. A representative query filtering to requested communications for a person's life event follows:

Because the view applies the business-group security predicate automatically, queries executed under a valid BEN responsibility return only the current user's authorized business group, eliminating the need for manual BUSINESS_GROUP_ID filtering in most reporting contexts.