Search Results enrollment_code




Overview
Explore in AI Chat

Overview

APPS.BEN_LER_CHG_PLIP_ENRT_D is a documented Oracle E-Business Suite database view owned by the APPS schema. Its FND Design Data designation is BEN.BEN_LER_CHG_PLIP_ENRT_D, and it is registered with a status of VALID. In the context of Oracle EBS 12.1.1 and 12.2.2, this view belongs to the Benefits (BEN) application module, and more specifically to the configuration of enrollment processing rules that govern Life Event changes and Plan-in-Program (PLIP) enrollment behavior.

The view presents a denormalized, read-friendly projection of enrollment-related change rule definitions. It joins life event reason (LER) definitions, plan-in-program (PLIP) definitions, plan (PL) definitions, and the enrollment change rule entities into a single queryable surface. This design allows reporting and integration consumers to retrieve descriptive names—such as PLAN_NAME and LER_NAME—alongside configuration codes without having to manually resolve the underlying foreign key relationships between the benefits setup tables.

The object carries an explicit Oracle Internal Use Only warning, and Oracle does not support direct access to this view except from standard Oracle Applications programs. It is therefore best treated as a diagnostic and reporting surface rather than as an integration API. The presence of a user-audit column such as LAST_UPDATED_BY and the trailing _D suffix indicate that the view is a denormalized read layer over the corresponding _F base entities.

Underlying Base Objects

According to the documented dependency metadata, BEN_LER_CHG_PLIP_ENRT_D references the following objects:

  • BEN_LER_CHG_PLIP_ENRT_F — the primary base entity holding the enrollment change rule records for a life event reason and plan-in-program combination.
  • BEN_LER_F — the life event reason definitions, supplying the LER_NAME value.
  • BEN_PLIP_F — the plan-in-program definitions that group plans for enrollment purposes.
  • BEN_PL_F — the plan definitions, supplying the PLAN_NAME value.
  • FND_USER — the application user table, used to resolve the identity captured in LAST_UPDATED_BY.
  • HR_GENERAL — a packaged API referenced for general HR utility functions used in the view definition.

The view is exposed under the APPS schema and is referenced by a public synonym, BEN_LER_CHG_PLIP_ENRT_D, which allows session-level access without schema qualification. Because the dependencies are fetched as synonyms, the view resolves through the standard EBS synonym chain into the Benefits product schema.

Key Columns

The view exposes the following columns, all of which are documented in the ETRM metadata:

Common Use Cases and Queries

Typical use cases include verifying how enrollment codes are assigned per life event reason and plan-in-program, auditing configuration changes, and driving custom reports. Because the column ENROLLMENT_CODE is a frequent search target, a common query filters directly on it:

  • SELECT ler_name, plan_name, enrollment_code, enrt_method_code, default_enrt_cd
  • FROM apps.ben_ler_chg_plip_enrt_d
  • WHERE enrollment_code = :p_enrollment_code
  • AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;

Another scenario retrieves all active rules for a given life event reason to review defaulting and automatic enrollment settings. Analysts also use the view to reconcile which rules default an enrollment code versus which rely on a rule identifier, by comparing DEFAULT_ENRT_CD against DEFAULT_ENRT_RULE. Given the internal-use restriction, any custom query should be treated as a read-only diagnostic rather than a supported integration point.