Search Results clear_down_pepcache




Overview
Explore in AI Chat

Overview

The APPS.BEN_PEP_CACHE package is a PL/SQL cache management and eligibility resolution utility within the Oracle EBS Advanced Benefits (OLTP) module. Its principal business function is to provide a server-side in-memory cache of "PEP" (Person Eligibility Period / Participation Eligibility Profile) determination results so that repeated eligibility evaluations during a benefits processing session do not require redundant re-derivation from the base eligibility tables. The package header identifies it as an AUTHID CURRENT_USER package, meaning it executes with the privileges of the invoking schema rather than the defining schema.

According to the ETRM metadata, the package is owned by APPS and is classified with an OTHER API classification. It exposes eight documented program units and is referenced by ten other packages, indicating that it functions as an internal shared service for benefits eligibility derivation rather than as a standalone public API. The header history shows continual revision between 1999 and 2005, with notable work on the eligibility cache revamp (Bug 3412822) and performance tuning through the removal of obsolete procedures (Bug 4350303) and restoration of package locals as globals (Bug 4425771).

Key Procedures and Functions

The documented program units are:

  • GET_PILPEP_DETS — Returns PEP detail information relating to the PIL (Person-Instance-Level) eligibility structure.
  • GET_PILEPO_DETS — Returns PEP determination details associated with the PILEPO (Person-Instance-Level Eligibility Profile Object) construct. A version-specific variant, get_pilepo_dets11521, was added in version 115.9.
  • GET_CURRPEPEPO_DETS — Retrieves the current PEP eligibility profile object details. Caching into this routine based on compensation object list row values was introduced in version 115.5.
  • GET_CURROIPLIPPEP_DETS — Retrieves current Other-Instance PEP detail information. Added in version 115.4.
  • GET_CURRPLNPEP_DETS — Retrieves the current Plan PEP detail set. Also introduced in version 115.4.
  • CLEAR_DOWN_CACHE — Invalidates the general eligibility cache contents maintained by the package.
  • CLEAR_DOWN_PEPCACHE — Clears the PEP-specific cache structures (the g_pilpep_lookup and g_pilpep_instance globals), resetting the g_pilpep_cached boolean flag to FALSE so that subsequent calls re-query the source tables. This is the procedure referenced by the user search term clear_down_pepcache.
  • CLEAR_DOWN_EPOCACHE — Clears the eligibility profile object (EPO) cache portion maintained by the package.

The package also declares a PL/SQL record type g_pep_rec (which grew to include inelg_rsn_cd in version 115.6) and an indexed collection type g_pep_inst_tbl based on ben_derive_part_and_rate_facts.g_cache_structure.

Tables Accessed

Per the documented table references (via APPS synonyms), the package reads from:

  • BEN_ELIG_PER_F — The eligibility profile definition entity, the primary source of PEP eligibility criteria.
  • BEN_ELIG_PER_OPT_F — Eligibility profile option/qualification rows that further refine eligibility determination.
  • BEN_PER_IN_LER — The person-to-LEL/LER assignment table used to resolve which eligibility records apply to a given person.
  • PLITBLM — A general PL/SQL index-by table (BLOB/line table) utility used for bulk lookup management.

These tables are read to populate the in-memory cache structures; the package does not appear to write directly to the base eligibility tables.

Usage Notes

Because it is an internal caching service, BEN_PEP_CACHE is typically invoked indirectly by the ten dependent benefits packages rather than by end users. In a normal session, callers first request detail sets through the GET_* routines; when underlying eligibility data changes within a session, the appropriate invalidation routine (CLEAR_DOWN_PEPCACHE for PEP data, CLEAR_DOWN_EPOCACHE for EPO data, or CLEAR_DOWN_CACHE for the full cache) must be invoked to force re-derivation. Custom forms, concurrent programs, or wrapper APIs that modify eligibility profile data and then immediately re-evaluate eligibility should call the clear-down routine to avoid stale results. The use of AUTHID CURRENT_USER means callers must have the necessary privileges on the referenced BEN tables.