Search Results default_enrt_rule




Overview
Explore in AI Chat

Overview

APPS.BEN_LER_CHG_PTIP_ENRT_D is an internal Oracle E-Business Suite view belonging to the Advanced Benefits (BEN) application module. In Oracle EBS 12.1.1 and 12.2.2, this view surfaces the enrollment processing rules attached to a Life Event Reason (LER) for a specific Plan Type in Plan Type enrollment processing. Its designation with the "_D" suffix and its inclusion of denormalized descriptive columns such as PLAN_TYPE_NAME and LER_NAME indicate that it is intended for display, reporting, and form-driven query purposes rather than for direct transactional update. Oracle classifies the object with the warning "Oracle Internal Use Only," and access is supported only through standard Oracle Applications programs. The view is registered under FND Design Data as BEN.BEN_LER_CHG_PTIP_ENRT_D and is marked VALID.

Underlying Base Objects

The view is defined over a small set of core BEN and shared objects. According to the documented dependency list, it references BEN_LER_CHG_PTIP_ENRT_F, the base table holding Life Event Reason / Plan Type enrollment change rules; BEN_LER_F, the Life Event Reason definitions; BEN_PL_TYP_F, the Plan Type definitions; BEN_PTIP_F, the Plan Type in Program (PTIP) definitions; FND_USER, used to resolve the identity of the last updater; and the HR_GENERAL package, which supplies standard date and utility logic. All of these are exposed to the view through public synonyms in the APPS schema. The view itself is not referenced by any other database object, confirming that it sits at the top of its dependency chain and serves purely as a consumer of the four BEN base tables plus user and utility sources.

Key Columns

The primary key column is LER_CHG_PTIP_ENRT_ID (NUMBER 15). The view is date-tracked through EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, consistent with the datetracked "_F" base table. Descriptive names are denormalized for readability: PLAN_TYPE_NAME and LER_NAME (each VARCHAR2 240) provide the human-readable Plan Type and Life Event Reason labels.

Common Use Cases and Queries

This view supports troubleshooting and reporting of life event enrollment rule configuration. Typical scenarios include auditing which default enrollment codes are attached to a life event and plan type, verifying flag combinations that govern whether participants may change elections, and reconciling configured defaults against enrollment results. A representative query follows:

SELECT LER_NAME, PLAN_TYPE_NAME, DEFAULT_ENRT_CD, DEFAULT_FLAG, DEFAULT_ENRT_RULE, ENROLLMENT_CODE, ENRT_METHOD_CODE, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE FROM APPS.BEN_LER_CHG_PTIP_ENRT_D WHERE DEFAULT_ENRT_CD = :p_enrt_cd AND SYSDATE BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE ORDER BY LER_NAME, PLAN_TYPE_NAME;

Because the object is documented for internal use only, any query should be restricted to read-only diagnostic or reporting activity, and production integrations should rely on supported Oracle APIs rather than direct SQL against this view.