Results for “voidd_dt”

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

Overview

BEN_PTNL_LER_FOR_PER is the participant potential life event table within the Oracle Advanced Benefits (BEN) module. It records life events that a participant may potentially experience or has been identified as eligible to report, forming the bridge between an enrollment period and the specific life event reason (LER) that could trigger an enrollment opportunity. In Oracle EBS 12.1.1 and 12.2.2, this table supports the life event processing framework that determines when participants may change their benefit elections outside of open enrollment.

From a Data Vault modeling perspective, the mined foreign key structure suggests a satellite-leaning classification. The table carries descriptive attributes and timestamps that track the lifecycle of a potential life event, while its relationship to BEN_ENRT_PERD positions it as dependent context rather than an independent hub. This heuristic should be treated as a modeling suggestion rather than a definitive architectural assertion.

Key Information Stored

The table is defined in the BEN schema with 27 documented columns. The surrogate primary key is PTNL_LER_FOR_PER_ID, enforced by the unique index BEN_PTNL_LER_FOR_PER_PK, which is the only documented business-key candidate.

• PTNL_LER_FOR_PER_ID — Surrogate primary key uniquely identifying each potential life event record.
• PERSON_ID — The participant associated with the potential life event.
• LER_ID — The life event reason identifier linking to the configured life event definition.
• ENRT_PERD_ID — Foreign key to BEN_ENRT_PERD, identifying the enrollment period context.
• LF_EVT_OCRD_DT — The date the life event actually occurred.
• DTCTD_DT — Date the potential life event was detected.
• PROCD_DT / UNPROCD_DT — Dates the record was processed or left unprocessed.
• VOIDD_DT — Date the potential life event was voided.
• PTNL_LER_FOR_PER_STAT_CD — Status code reflecting the processing state of the record.
• PTNL_LER_FOR_PER_SRC_CD — Source code indicating how the record was created.
• BUSINESS_GROUP_ID — Business group partitioning column for multi-tenant data separation.
• MNL_DT / MNLO_DT — Manual processing dates.
• NTFN_DT — Notification date associated with the event.
• CSD_BY_PTNL_LER_FOR_PER_ID — Self-referencing column indicating the record that caused this one.
• TRGR_TABLE_PK_ID — Identifier of the source trigger table row that generated this potential life event.

Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) and concurrent program columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE) support auditing and traceability.

Common Use Cases and Queries

Typical reporting scenarios include identifying participants with pending potential life events, auditing life event processing status, and reconciling detected versus processed events. A representative query joins to the enrollment period and person tables:

• Querying all potential life events for a person within an enrollment period, filtered by status code, to determine open enrollment eligibility.
• Reporting unprocessed potential life events (where UNPROCD_DT is not null) for benefits administrators.
• Auditing detection-to-processing latency by comparing DTCTD_DT and PROCD_DT.
• Identifying voided events using VOIDD_DT for reconciliation of canceled elections.
• Tracing chained events through the CSD_BY_PTNL_LER_FOR_PER_ID self-reference.

Related Objects

The following objects are the most significant dependencies based on the documented relationship data:

• BEN_ENRT_PERD — Referenced through the ENRT_PERD_ID foreign key; provides enrollment period context.
• BEN_PER_IN_LER — Child table referencing PTNL_LER_FOR_PER_ID; stores the person's life event details derived from this record.
• BEN_PTNL_LER_FOR_PER_RBV — Read-only business view projecting this table for reporting.
• BEN_PER_IN_LER_RBV — Read-only view referencing PTNL_LER_FOR_PER_ID, used for downstream reporting.
• BEN_LER_FOR_PER_F and life event configuration tables accessed via LER_ID.
• PER_ALL_PEOPLE_F — Joined via PERSON_ID to resolve participant identity in reporting queries.

These relationships confirm that BEN_PTNL_LER_FOR_PER functions as a central staging point for life event detection before records are promoted into the person-in-life-event structures used by the benefits processing engine.