Results for “ptip_ordr_num”

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

Overview

BEN_ENRT_OVERRIDE_V is an Oracle EBS Advanced Benefits (BEN) view owned by the APPS schema. It exposes enrollment override records generated from eligibility and plan configuration data, presenting a consolidated, session-scoped result set in which each row represents a potential manual enrollment override for a participant. The view is defined over the effective-dated BEN tables plus FND_SESSIONS, and it functions as a reporting and integration surface rather than a transactional entry point. Because it derives its rows from eligibility records flagged as ELIG_FLAG = 'Y', it is principally used to identify persons who are eligible for a plan or program and whose coverage start should be established through an override mechanism instead of normal automated enrollment processing.

The view is documented as VALID in ETRM 12.2.2 and remains consistent with the 12.1.1 data model, as the referenced base objects are unchanged between releases.

Underlying Base Objects

The documented base objects are all APPS synonyms, resolving to the BEN tables that hold eligibility, plan, program, option, and enrollment result data:

• BEN_ELIG_PER_F — person-level eligibility records; supplies PERSON_ID, BUSINESS_GROUP_ID, PL_ID, PGM_ID, and the derived PER_IN_LER_ID.
• BEN_ELIG_PER_OPT_F — option-level eligibility detail, outer-joined ((+)) to person eligibility to optionally restrict results to a specific option.
• BEN_OPT_F — plan option definitions, providing OPT_ID and OPT_NAME.
• BEN_PL_F — plan definitions, supplying PL_ID, PL_NAME, and the non-implied plan unit of measure (NIP_PL_UOM).
• BEN_PGM_F — program definitions, supplying PGM_ID, PGM_NAME, and PGM_UOM.
• BEN_PL_TYP_F — plan type lookup, providing PL_TYP_ID and PL_TYP_NAME.
• BEN_PER_IN_LER — learner/recipient linkage used to resolve the effective PER_IN_LER_ID.
• FND_SESSIONS — restricts output to the current session via USERENV('SESSIONID').
• BEN_OIPL_F, BEN_PRTT_ENRT_RSLT_F — documented as referenced; support option-in-plan and enrollment result resolution.

Key Columns

The view emits a fixed projection. Notable columns include:

• EFFECTIVE_START_DATE — copied from FND_SESSIONS.EFFECTIVE_DATE; drives all effective-dated joins.
• PER_IN_LER_ID — resolved via NVL(EPO.PER_IN_LER_ID, PEP.PER_IN_LER_ID), identifying the person-in-learner relationship.
• OPT_ID, OPT_NAME, PGM_ID, PGM_NAME, PL_ID, PL_NAME, PL_TYP_ID, PL_TYP_NAME — plan, program, and option context.
• UOM — derived from program or plan unit of measure (used for coverage amounts).
• ENRT_CVG_STRT_DT — the enrollment coverage start date, assigned from F.EFFECTIVE_DATE; this is the column most commonly searched by users resolving the enrt_cvg_strt_dt reference.
• ENRT_CVG_THRU_DT — fixed to 12/31/4712 (the EBS high-date).
• ORGNL_ENRT_DT, ENRT_MTHD_CD ('O'), ENRT_OVRIDN_FLAG ('Y'), SSPNDD_FLAG ('N') — flag and method indicators identifying override enrollments.

Common Use Cases and Queries

Typical usage includes verifying override enrollment candidates, reconciling coverage start dates against eligibility, and feeding downstream interfaces. A representative query filtering on the searched column:

• SELECT person_id, pl_id, opt_id, enrt_cvg_strt_dt FROM apps.ben_enrt_override_v WHERE enrt_cvg_strt_dt >= :p_start_date;
• Joining to PER_ALL_PEOPLE_F on PERSON_ID to report employee names and override coverage starts.
• Grouping by PL_NAME and PL_TYP_NAME to summarize override volume by plan type.

Because output is constrained by FND_SESSIONS, the view returns data only within an active EBS session context and should not be used for batch reporting outside a session-bound connection.