Results for “sal_chg_reason_cd”

26 results




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

Overview

BENBV_ENRT_PERD_V is a business view in the Oracle Advanced Benefits (BEN) module, defined in the APPS schema and shipped with Oracle E-Business Suite 12.1.1 and 12.2.2. It identifies a specific instance of an enrollment period for a program or plan within a defined enrollment type cycle, such as an open enrollment, a life event, or a periodic enrollment. The view is the standard reporting and integration interface for enrollment period configuration data, exposing the date rules, coverage start and end rules, budget and worksheet update windows, approval settings, and hierarchy controls that govern how eligibility and rate processing behave during a given enrollment cycle.

The object is a VIEW with a status of VALID. Its role is consistent with other BENBV_* business views: it decouples consumers from the underlying table structure, adds descriptive flexfield support, and enriches coded columns with decoded meanings through the HR_BIS package. This makes it suitable for concurrent program report queries, Oracle BI Publisher data models, and inbound/outbound interface extracts.

Underlying Base Objects

The documented base objects for BENBV_ENRT_PERD_V are BEN_ENRT_PERD (referenced through a SYNONYM) and the HR_BIS package. BEN_ENRT_PERD is the principal table storing enrollment period definitions; the view selects its columns and aliases them with the ENP prefix. The HR_BIS package supplies the BIS_DECODE_LOOKUP function, which is invoked repeatedly in the view text to translate lookup codes into user-facing descriptions. No joins to other base tables are documented in the excerpt, so the view is effectively a single-table projection over BEN_ENRT_PERD with lookup decoding applied. Descriptive flexfield attributes are surfaced through the special '_DF:BEN:BEN_ENRT_PERD:ENP' token, which the BEN framework expands at runtime.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing enrollment period configuration, validating coverage and rate date rules before an open enrollment, reconciling budget and worksheet windows against payroll calendars, and confirming which hierarchy rule governs a cycle. A representative query is:

SELECT strt_dt, end_dt, enrt_cvg_strt_dt, enrt_cvg_end_dt,
       hrchy_rl, auto_distr_flag
  FROM apps.benbv_enrt_perd_v;

To inspect decoded controls, select the paired descriptor columns alongside their code columns. Reporting joins typically link HRCHY_RL back to BEN's hierarchy rule tables where a descriptive name is required, since the view itself exposes the rule identifier rather than its label.