Results for “ler_id”

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

Overview

BEN_PERSON_ACTIONS is a core table within the Oracle Advanced Benefits (BEN) module of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It identifies the persons being processed by the benefits batch process, serving as a per-person work record that ties an individual to a specific benefits action executed by a concurrent program or batch job. Because benefits processing involves large volumes of participants whose eligibility, enrollment, and life-event processing must be tracked independently, this table acts as the operational tracking mechanism for that work.

From a Data Vault modeling perspective, the heuristic classification of this table is hub-leaning. The primary key PERSON_ACTION_ID behaves as a durable business key that anchors references from many dependent tables, and its largely descriptive column set (status, version, action linkage) is consistent with a hub-and-satellite pattern rather than a pure transaction link. This classification is offered as a modeling suggestion; the table is a standard third-normal-form EBS table.

Key Information Stored

The table contains eight documented columns in the 12.2.2 physical schema. The most significant are summarized below.

• PERSON_ACTION_ID — the surrogate primary key and unique business-key candidate, defined by index BEN_PERSON_ACTIONS_PK. All downstream benefit detail tables reference a person's run data through this value.
• PERSON_ID — identifies the person being processed. This is the link to the person/assignment model (PER_ALL_PEOPLE_F) and is the column used to filter a run down to a specific participant.
• BENEFIT_ACTION_ID — foreign key to BEN_BENEFIT_ACTIONS, identifying the benefits action (for example, an enrollment or life-event process) under which this person is being processed.
• ACTION_STATUS_CD — the processing status of the person's action, allowing the batch to mark records as pending, in progress, completed, or errored.
• LER_ID — the life-event reason identifier, linking the person action to the qualifying life event that triggered processing, where applicable.
• NON_PERSON_CD — a code used to distinguish processing that is not attached to an actual person record, such as placeholder or system-level actions.
• OBJECT_VERSION_NUMBER — the standard EBS optimistic locking column used to detect concurrent updates.
• CHUNK_NUMBER — a batch-partitioning column indicating which chunk a person action belongs to, supporting parallel processing of large populations.

Common Use Cases and Queries

The primary use case is monitoring and troubleshooting batch benefits processing. A typical query lists persons still in a non-complete status for a given benefits action:

• Monitoring a concurrent run: select PERSON_ID, ACTION_STATUS_CD, CHUNK_NUMBER from BEN_PERSON_ACTIONS where BENEFIT_ACTION_ID = :p_action_id and ACTION_STATUS_CD is the value for pending or errored.
• Diagnosing a single person: select PERSON_ACTION_ID, PERSON_ID, BENEFIT_ACTION_ID, LER_ID from BEN_PERSON_ACTIONS where PERSON_ID = :p_person_id.
• Parallel-processing reconciliation: group rows by CHUNK_NUMBER to confirm each chunk was processed and validate the starting/ending person action IDs recorded in BEN_BATCH_RANGES.
• Life-event audit: join LER_ID to the life-event tables to confirm that the correct qualifying event drove processing.

Because virtually every BEN result view is keyed by PERSON_ACTION_ID, reports that reconcile enrollment results, eligibility, rates, and premiums begin by resolving this identifier for the target person and action.

Related Objects

The table participates in a wide reference structure. The most significant related objects and their join columns are:

• BEN_BENEFIT_ACTIONS — referenced via BENEFIT_ACTION_ID; defines the benefits action being processed.
• BEN_BATCH_RANGES — references this table through STARTING_PERSON_ACTION_ID and ENDING_PERSON_ACTION_ID, bounding each parallel chunk.
• The BEN_*_RBV result views (for example BEN_ENRT_BNFT_RBV, BEN_ENRT_RT_RBV, BEN_ELIG_PER_ELCTBL_CHC_RBV, BEN_PTNL_LER_FOR_PER_RBV) — each joins on PERSON_ACTION_ID to return enrollment, rate, eligibility, and life-event detail.
• OTA_BULK_ENR_REQ_MEMBERS — the Oracle Training Administration requisition member table, which references PERSON_ACTION_ID to associate learners with benefit processing records.
• PER_ALL_PEOPLE_F — joined via PERSON_ID to resolve the person's name and assignment attributes for reporting.