Results for “ben_per_in_ler_stat”

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

Overview

APPS.BENBV_PER_IN_LER_V is a read-only business view in the Oracle E-Business Suite Benefits (BEN) module, exposed under the APPS schema and available in both EBS 12.1.1 and 12.2.2. It presents a flattened, reporting-oriented projection of the BEN_PER_IN_LER table, which stores "Person in Life Event" records — the intersection of a person (or participant) with a specific processed Life Event. The view is one of the standard BENBV ("Benefits Business View") objects generated by the Benefits business intelligence layer, designed to deliver decoded lookup values, descriptive flexfield hooks, and security-filtered data rather than raw transactional codes.

The view is declared WITH READ ONLY, indicating it is intended strictly for query and reporting consumption. It plays a recurring role in Benefits reporting, extract generation, and integration interfaces where downstream systems or BI tools require human-readable life event status values and standardized security scoping.

Underlying Base Objects

The ETRM metadata documents three referenced base objects:

• BEN_PER_IN_LER (SYNONYM) — the driving table, aliased PIL in the view text. All persistent columns originate here.
• BEN_BIS_UTILS (PACKAGE) — supplies GET_GROUP_PL_NAME, used to resolve the Group Plan (or Program) name for a given GROUP_PL_ID as of the life event occurrence date.
• HR_BIS (PACKAGE) — supplies BIS_DECODE_LOOKUP, which decodes status codes, and GET_SEC_PROFILE_BG_ID, which enforces Business Group security in the WHERE clause.

The relationship to BEN_PER_IN_LER is therefore one-to-one at the row level, with the packages augmenting each row with decoded descriptions and a security predicate.

Key Columns

The view exposes dates, decoded statuses, identifiers, and WHO columns:

• Status codes and descriptions — PER_IN_LER_STAT_CD and PRVS_STAT_CD expose raw codes, while companion columns call HR_BIS.BIS_DECODE_LOOKUP('BEN_PER_IN_LER_STAT', ...) to return their meaningful lookup meanings for both current and previous status.
• Life event dates — LF_EVT_OCRD_DT (occurrence), PROCD_DT (processed), STRTD_DT (started), VOIDD_DT (voided), BCKT_DT (backed out), CLSD_DT (closed), NTFN_DT (notification), and MGR_OVRID_DT (manager override).
• Identifiers — PER_IN_LER_ID (primary key), LER_ID (life event reason), PERSON_ID, BUSINES_GROUP_ID, PTNL_LER_FOR_PER_ID, ASSIGNMENT_ID, GROUP_PL_ID, BCKT_PER_IN_LER_ID, TRGR_TABLE_PK_ID, WS_MGR_ID, MGR_OVRID_PERSON_ID, plus concurrent request audit fields REQUEST_ID, PROGRAM_APPLICATION_ID, and PROGRAM_ID.
• Descriptive flexfield — a literal '_DF:BEN:BEN_PER_IN_LER:PIL' marker signals to the Benefits flexfield framework that BEN_PER_IN_LER carries a DFF context.
• WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE.

Common Use Cases and Queries

Typical uses include Benefits status dashboards, audit trail reporting, and interfaces that require readable life event states. A simple query returning decoded statuses per person is:

SELECT person_id, per_in_ler_id,
  HR_BIS.BIS_DECODE_LOOKUP('BEN_PER_IN_LER_STAT', per_in_ler_stat_cd) status,
  lf_evt_ocrd_dt, procd_dt
FROM apps.benbv_per_in_ler_v
WHERE lf_evt_ocrd_dt >= :p_from_date;

Because the view includes the Business Group security predicate, queries automatically return only rows the session is authorized to see, making it suitable for multi-organization deployments. Reporting against this view avoids the need to manually join lookup decoding logic, ensuring consistent semantics across Benefits extracts and integrations.