Results for “ben_batch_ler_info”

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

Overview

BEN_BATCH_LER_INFO is a table within the BEN (Advanced Benefits) product schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores life event information that is created during a batch run — specifically, the interim and processed records that the Advanced Benefits life event batch process generates when evaluating participant eligibility for life events. The object holds a status of VALID in the ETRM documentation and is owned by the BEN schema. Its purpose is to capture the outcome of batch evaluation logic so that downstream benefits processing, eligibility determination, and life event enrollment can proceed correctly.

From a heuristic Data Vault classification standpoint, this table is modeled as a link. This classification is derived from its foreign key structure: BEN_BATCH_LER_INFO references BEN_BENEFIT_ACTIONS via BENEFIT_ACTION_ID and BEN_PER_IN_LER via PER_IN_LER_ID. Rather than acting as a standalone hub of business entities, the table serves to associate batch-generated life event records with the benefit actions and person-in-life-event relationships they relate to, which is characteristic of a link structure.

Key Information Stored

The table contains 25 documented columns. The surrogate primary key is BATCH_LER_ID, enforced by the unique index BEN_BATCH_LER_INFO_PK. Because the primary key is a system-generated identifier rather than a natural business key, it is best treated as a surrogate key. The most significant columns are:

• BATCH_LER_ID — Surrogate primary key uniquely identifying each batch life event record.
• BENEFIT_ACTION_ID — Foreign key to BEN_BENEFIT_ACTIONS, linking the record to the associated benefit action.
• PER_IN_LER_ID — Foreign key to BEN_PER_IN_LER, tying the record to the person-in-life-event relationship.
• PERSON_ID — Identifies the person for whom the batch life event record was produced.
• LER_ID — Identifier of the life event reason being evaluated.
• BUSINESS_GROUP_ID — Business group context for the record.
• LF_EVT_OCRD_DT — Life event occurred date, driving eligibility timing.
• REPLCD_FLAG — Indicates whether the life event record has been replaced.
• CRTD_FLAG — Indicates whether the life event has been created.
• DLTD_FLAG — Indicates whether the record has been deleted.
• CLSD_FLAG — Indicates whether the life event is closed.
• OPEN_AND_CLSD_FLAG — Captures records that are open and closed within the same batch.
• STL_ACTV_FLAG — Indicates whether the life event is still active.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / CREATED_BY / CREATION_DATE — Standard audit columns.

Additional status flags (TMPRL_FLAG, NOT_CRTD_FLAG, CLPSD_FLAG, CLSN_FLAG, NO_EFFECT_FLAG, CVRGE_RT_PREM_FLAG) and OBJECT_VERSION_NUMBER support concurrency and lifecycle tracking.

Common Use Cases and Queries

Typical uses involve diagnosing batch life event processing results, auditing which persons had events detected, and reconciling records linked to benefit actions. A representative query joins the batch record to its parent life event:

• Retrieve all records for a person: SELECT * FROM BEN_BATCH_LER_INFO WHERE PERSON_ID = :person_id;
• Join to benefit actions: SELECT b.BATCH_LER_ID, a.* FROM BEN_BATCH_LER_INFO b JOIN BEN_BENEFIT_ACTIONS a ON b.BENEFIT_ACTION_ID = a.BENEFIT_ACTION_ID;
• Join to person-in-life-event: SELECT b.*, p.* FROM BEN_BATCH_LER_INFO b JOIN BEN_PER_IN_LER p ON b.PER_IN_LER_ID = p.PER_IN_LER_ID;
• Filter active/unprocessed events using the status flags (CRTD_FLAG, DLTD_FLAG, STL_ACTV_FLAG).

Reporting commonly examines LF_EVT_OCRD_DT against batch run dates to validate event detection windows.

Related Objects

• BEN_BENEFIT_ACTIONS — Referenced via BENEFIT_ACTION_ID; the action generated by the batch life event.
• BEN_PER_IN_LER — Referenced via PER_IN_LER_ID; the person-in-life-event relationship.
• BEN_BATCH_LER_INFO_PK — Primary key index on BATCH_LER_ID.
• Related BEN life event and eligibility tables that consume batch results, including those joined through PERSON_ID and LER_ID, complete the processing chain.