Search Results ben_per_in_ler_f




Overview
Explore in AI Chat

Overview

APPS.BEN_REOPEN_LER_CONC is the concurrent-program driver package responsible for the "Reopen Life Events" process in Oracle Advanced Benefits. The package's stated purpose, taken from its own header comments, is to "reopen latest life event for all the persons" identified by the concurrent request parameters. In the Oracle EBS benefits model, a life event record in BEN_LER_F represents a person's eligibility to make benefit elections in response to a qualifying event (marriage, birth, hire, termination, and similar triggers). Once processed, a life event is locked into its completed state and can no longer accept changes. The reopen process reverses that condition for the most recent life event of each selected person, re-enabling the life event so that elections and dependent designations can be corrected or reprocessed.

The package is the technical backbone behind the executable BENROLER, which is mapped to the "Reopen Life Events" concurrent program. The header identifies it as source file benrecon.pkb and records the original author, gsehgal, who created it in August 2006. The revision history documents an early correction for the "no persons selected" scenario (Bug 5589226), which had caused the process to error out, and a change to the person selection rule that also corrected SSN output and the display of the from-date parameter.

Key Procedures and Functions

  • PROCESS — The main entry point invoked by the BENROLER executable. It accepts the concurrent request parameters (benefit action, effective date, business group, life event, from-date, organization, location, benefits group, legal entity, and person selection criteria) together with the standard concurrent-manager OUT parameters errbuf and retcode. It drives person selection, validation, and the reopening of each selected person's latest life event, and is the procedure that generates the concurrent output and log.
  • DO_MULTITHREAD — The multithreading control procedure. It partitions the selected population into ranges so that multiple parallel workers can process subsets of persons concurrently. This procedure is what supports the BEN_BATCH_RANGES table access, which stores the range boundaries assigned to each worker thread for a given request.
  • SUBMIT_ALL_REPORTS — Extracts and reports on the outcome of the run. It emits the results of the completed processing so that the request log records which persons were processed, which were skipped, and which errored. The package's global counter g_max_person_err (set to 100) bounds the number of person-level errors retained, while g_persons_errored and g_persons_procd track totals.

Tables Accessed

  • BEN_LER_F — The life event records table; the central object of the reopen operation, updated to restore the latest life event per person.
  • BEN_PER_IN_LER — Associates persons with life events. This is the table named in the user's search term "ben_per_in_ler_f" and is the primary driver for the individual-level reopen worker logic.
  • BEN_PERSON_ACTIONS — Tracks benefit actions performed against a person, recording the reopen activity for audit and follow-up processing.
  • BEN_BENEFIT_ACTIONS — Identifies the benefit action context (p_benefit_action_id) governing the run.
  • BEN_BATCH_RANGES — Stores the chunking boundaries used by DO_MULTITHREAD.
  • PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F — Source the person and assignment selection criteria, including organization and location filters.
  • HR_SOFT_CODING_KEYFLEX — Resolves soft-coding key flexfield combinations for benefits eligibility.
  • PLITBLM — The generic PL/SQL index-by table type used for passing collections of person identifiers between the driver and worker procedures.

Usage Notes

BEN_REOPEN_LER_CONC is not a public API and is not referenced by any other package. It is invoked exclusively through the "Reopen Life Events" concurrent program (executable BENROLER), typically submitted from the Benefits responsibility when a population of persons requires their latest life events to be reopened. The request parameters mirror the PROCESS signature: benefit action, effective date, business group, life event, from-date, organization, location, benefits group, legal entity, and person selection rule. In EBS 12.1.1 and 12.2.2 the calling convention and behavior are unchanged, as the package was not modified after its 115.x/120.x revisions. Because it performs direct DML on life event data with no rollback boundary exposed to the caller, it should only be run during controlled benefits maintenance windows, ideally with the validate parameter set to 'Y' on an initial review run before the production reopen is committed.