Results for “ben_ptnl_ler_for_per_rbv”

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

Overview

BEN_PTNL_LER_FOR_PER_RBV is a table in the BEN (Advanced Benefits) schema within Oracle E-Business Suite 12.1.1 and 12.2.2. The ETRM documentation describes this object as storing "Plan Information Types" and identifies it under the Product/Module designation "BEN - Advanced Benefits." In physical terms, it holds 28 columns and is owned by the BEN schema with a status of VALID.

The table records potential Life Event Records (LER) associated with a person and enrollment period, functioning as a staging or resolution layer that tracks when a life event is detected, processed, unprocessed, voided, or manually entered. The "RBV" suffix in the object name conventionally indicates a relational backing view (a view with an INSTEAD OF trigger that maps to underlying entities). The heuristic Data Vault classification mined from its foreign key structure is standalone, which suggests it can be modeled as an independent hub or as a link-like entity, since it carries its own surrogate key but references several dimension-like parents rather than being a pure satellite of one parent.

Key Information Stored

The primary key of the table, per the documented unique index BEN_PTNL_LER_FOR_PER_RBV_PK, is the composite of BENEFIT_ACTION_ID and PTNL_LER_FOR_PER_ID. This pair functions as the business-key candidate that uniquely identifies each potential life event record.

Important columns include:

• PTNL_LER_FOR_PER_ID — the surrogate identifier for the potential LER/person relationship; also the FK to BEN_PTNL_LER_FOR_PER.
• LER_ID — identifies the life event record the row relates to.
• PERSON_ID — the person whose life event is being tracked.
• ENRT_PERD_ID — the enrollment period context (FK to BEN_ENRT_PERD).
• PTNL_LER_FOR_PER_STAT_CD — status code of the potential LER (e.g., detected, processed, voided).
• PTNL_LER_FOR_PER_SRC_CD — source code indicating how the record was created.
• DTCTD_DT, PROCD_DT, UNPROCD_DT, VOIDD_DT, MNL_DT, MNLO_DT — detection, processing, unprocessing, voiding, manual entry, and manual override dates.
• LF_EVT_OCRD_DT — the date the life event occurred.
• NTFN_DT — notification date associated with the event.
• BENEFIT_ACTION_ID and PERSON_ACTION_ID — FKs to the benefit and person action tables.
• CSD_BY_PTNL_LER_FOR_PER_ID — self-referencing identifier for the record that caused this one.
• Standard WHO/audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, REQUEST_ID, PROGRAM_ID, OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

This table supports benefits administrators and reporting teams who need to determine which life events have been detected for a person, whether they were processed within the correct enrollment period, and which actions remain outstanding. Typical queries reconcile detected versus processed events:

• Listing all pending potential life events for an enrollment period: SELECT PERSON_ID, LER_ID, PTNL_LER_FOR_PER_STAT_CD FROM BEN_PTNL_LER_FOR_PER_RBV WHERE ENRT_PERD_ID = :p_period AND PROCD_DT IS NULL;
• Tracking processing latency by comparing DTCTD_DT and PROCD_DT.
• Identifying manually created records via MNL_DT/MNLO_DT.
• Auditing voided or unprocessed events via VOIDD_DT and UNPROCD_DT.
• Joining to BEN_ENRT_PERD to validate enrollment period context.

Related Objects

• BEN_PTNL_LER_FOR_PER — parent of PTNL_LER_FOR_PER_ID; supplies the base potential LER record.
• BEN_ENRT_PERD — enrollment period referenced by ENRT_PERD_ID.
• BEN_BENEFIT_ACTIONS — referenced by BENEFIT_ACTION_ID and part of the primary key.
• BEN_PERSON_ACTIONS — referenced by PERSON_ACTION_ID.
• BEN_PTNL_LER_FOR_PER_RBV is itself self-referenced through CSD_BY_PTNL_LER_FOR_PER_ID, relating records to their cause.
• Indirectly, PERSON_ID connects to PER_ALL_PEOPLE_F for person reporting and to BEN_LER_FOR_PER for the finalized life event record.