Results for “ben_batch_ranges_pk”

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

Overview

BEN_BATCH_RANGES is a transactional table in the BEN (Advanced Benefits) schema of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It stores the ranges of person actions that are processed within a single batch run of the Oracle Advanced Benefits engine. When a batch process such as a benefits open enrollment, life event processing, or eligibility recalculation is executed, the processing workload is divided into discrete ranges. Each row in BEN_BATCH_RANGES corresponds to one such range, defining the slice of person actions covered by a given benefit action within the batch. The table therefore acts as a control and partitioning mechanism that allows long-running benefits batch programs to be tracked, restarted, and audited.

Under a heuristic Data Vault classification derived from the documented foreign key structure, BEN_BATCH_RANGES is best modeled as a link table. It resolves the association between a benefit action and a bounded set of person actions, referencing BEN_BENEFIT_ACTIONS and BEN_PERSON_ACTIONS as its hub-like parent entities. This classification is a modeling suggestion rather than a normative Oracle designation.

Key Information Stored

The table contains 11 documented columns. The most important are:

• RANGE_ID — The surrogate primary key, uniquely identified by the BEN_BATCH_RANGES_PK unique index. It is the only documented business-key candidate.
• BENEFIT_ACTION_ID — Foreign key to BEN_BENEFIT_ACTIONS, identifying the benefit action whose processing is being partitioned.
• STARTING_PERSON_ACTION_ID — Foreign key to BEN_PERSON_ACTIONS, marking the first person action in the range.
• ENDING_PERSON_ACTION_ID — Foreign key to BEN_PERSON_ACTIONS, marking the last person action in the range.
• RANGE_STATUS_CD — The processing status of the range, used to track whether the range is pending, in progress, or complete.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle framework to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard audit columns capturing who created and last modified each row and when.

The STARTING_PERSON_ACTION_ID and ENDING_PERSON_ACTION_ID pair defines the inclusive boundaries of the range; the RANGE_STATUS_CD supports status-driven monitoring and restart logic.

Common Use Cases and Queries

Typical use cases include monitoring batch progress, restarting failed ranges, and reporting on processing coverage. A common query joins the range to its benefit action and to the boundary person actions:

• Identify all ranges for a batch: SELECT RANGE_ID, BENEFIT_ACTION_ID, RANGE_STATUS_CD, STARTING_PERSON_ACTION_ID, ENDING_PERSON_ACTION_ID FROM BEN_BATCH_RANGES WHERE BENEFIT_ACTION_ID = :p_action_id;
• Find incomplete ranges for restart: SELECT RANGE_ID FROM BEN_BATCH_RANGES WHERE RANGE_STATUS_CD = :pending_status;
• Resolve boundaries to actual persons by joining STARTING_PERSON_ACTION_ID and ENDING_PERSON_ACTION_ID to BEN_PERSON_ACTIONS.

Report developers frequently surface range status alongside benefit action descriptions to give administrators visibility into long-running processes.

Related Objects

The documented foreign keys tie BEN_BATCH_RANGES to the following principal objects:

• BEN_BENEFIT_ACTIONS — Referenced through BENEFIT_ACTION_ID; defines the benefit action being partitioned.
• BEN_PERSON_ACTIONS — Referenced twice, via STARTING_PERSON_ACTION_ID and ENDING_PERSON_ACTION_ID, defining the range boundaries.

These relationships form the link structure described above. Additional batch-control and logging objects in the BEN schema typically surround this table, but the FK metadata documents only the three references listed, which are the definitive dependencies.