Results for “enrt_mthd”

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

Overview

APPS.BEN_LER_CHG_PGM_ENRT_D is a read-only internal view in the Oracle E-Business Suite 12.1.1 / 12.2.2 Benefits (BEN) module. It exposes the denormalized change-history of program enrollment method assignments defined at the Life Event Reason (LER) level. The object is registered in the Applications FND Design Data repository as BEN.BEN_LER_CHG_PGM_ENRT_D and carries a status of VALID. It is explicitly flagged as Oracle Internal Use Only: Oracle Corporation does not support direct customer access to applications data through this object except from standard Oracle Applications programs. Consequently the view should be treated as a reporting and diagnostic surface rather than a supported integration endpoint.

Functionally, the view resolves the raw foreign-key identifiers stored in the underlying _F (frozen/date-tracked) entity table into user-facing meanings by joining lookup values and translated name columns. For the search term enrt_mthd_meaning, the relevant attribute is the column of the same name, which returns the decoded meaning for the enrollment method associated with a program enrollment change record. This makes the view useful for LER setup verification, benefits configuration audits, and migration validation.

Underlying Base Objects

The view is defined over the following documented base objects, each exposed through an APPS synonym:

• BEN_LER_CHG_PGM_ENRT_F — the primary date-tracked table holding the LER change program enrollment records, supplying LER_CHG_PGM_ENRT_ID and the effective-date range.
• BEN_LER_F — supplies the Life Event Reason definition and resolves LER_NAME.
• BEN_PGM_F — supplies the program definition and resolves PGM_NAME.
• FF_FORMULAS_F — provides the Fast Formula reference used to derive the automatic enrollment method name (AUTO_ENRT_MTHD_NAME).
• FND_USER — resolves the standard Who column LAST_UPDATED_BY to a user identity.
• HR_API — a PL/SQL package invoked within the view logic for Business Group / security context evaluation.
• HR_LOOKUPS — the shared lookup view that decodes stored lookup codes into the various _MEANING columns, including ENRT_MTHD_MEANING.

The view is not referenced by any other database object, confirming its role as a reporting leaf rather than a component of a deeper dependency chain.

Key Columns

• ROW_ID — the physical rowid of the underlying table row, useful for direct row addressing.
• LER_CHG_PGM_ENRT_ID — primary identifier for the LER change program enrollment record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-tracked validity window of the configuration row.
• ENRT_MTHD_MEANING — the decoded meaning of the enrollment method; the primary attribute returned for the search term.
• ENRT_MEANING / ENRT_NAME — the enrollment code meaning and its translated display name.
• DFLT_ENRT_MEANING / DFLT_ENRT_NAME — the default enrollment designation for the record.
• AUTO_ENRT_MTHD_NAME — the Fast Formula-derived automatic enrollment method label.
• CRNT_ENRT_PRCLDS_CHG_MEANING — indicates behavior related to current enrollment when prior coverage changes.
• STL_ELIG_CANT_CHG_MEANING — indicates whether eligibility can still be changed.
• PGM_NAME / LER_NAME — the program and Life Event Reason display names.
• LAST_UPDATE_DATE / LAST_UPDATED_BY — standard Who audit columns.

Common Use Cases and Queries

Typical scenarios include auditing the enrollment method configured per LER and program, reconciling configuration across Business Groups, and validating the effect of date-tracked changes. A representative query filtering explicitly on the searched attribute is shown below.

SELECT ler_name, pgm_name, enrt_name, enrt_mthd_meaning, dflt_enrt_name, effective_start_date, effective_end_date FROM apps.ben_ler_chg_pgm_enrt_d WHERE enrt_mthd_meaning IS NOT NULL ORDER BY ler_name, pgm_name, effective_start_date;

Because the view is an Oracle-internal object, any query should be executed under the APPS schema with appropriate responsibility-based security, and results should not be surfaced in custom integrations against the vendor's support policy.