Search Results set_pps_object

Overview

APPS.BEN_PERSON_OBJECT is an Oracle E-Business Suite PL/SQL caching package that belongs to the Oracle Advanced Benefits (OAB) module. Its stated purpose, drawn directly from the package header, is to return person object information. The package name reflects the "Person Object Caching Routine" designation carried in the source header (benperde.pkh, version 120.0.12000000.1, last modified 2007/01/19).

The package was designed to avoid repeated, expensive queries against the core HR person and assignment tables during benefits processing. Rather than re-reading PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, and related tables for every benefits calculation, callers invoke a SET_* routine once to populate an in-memory cache, and subsequent logic reuses the cached structure. The history log traces the package's evolution from its creation in June 1999, adding caches for person date information, FTE totals for primary assignments, active life events, benefits balances, assignment extra information, contacts, assignment status types, soft coding keyflex structures, person type information, benefits assignments, and applicants assignments. Later revisions removed the css cache, changed the business group id handling in set_ast_object, and applied NOCOPY compiler directives for performance.

Key Procedures and Functions

The documented package exposes 62 procedures and functions. The principal SET_* cache loaders are:

• SET_OBJECT — the general entry point for populating the person object cache.
• SET_PER_OBJECT — caches person-level information.
• SET_ASS_OBJECT and SET_ALL_ASS_OBJECT — cache assignment data, with the ALL variant handling the full set of assignments for a person.
• SET_BENASS_OBJECT and SET_APP_ASS_OBJECT / SET_APPASS_OBJECT — cache benefits-specific and applicant-specific assignment records; the applicants assignment cache is multirow.
• SET_ALLASS_OBJECT — caches the complete assignment set.
• SET_BAL_OBJECT, SET_BAL_PER_OBJECT, and SET_BNB_OBJECT — cache benefits balance information sourced from the balance Flexfield views.
• SET_CON_OBJECT and SET_CON_PER_OBJECT — cache participant contact information.
• SET_TYP_OBJECT and SET_TYP_PER_OBJECT — cache person type and person type usage data.
• SET_AST_OBJECT — caches assignment status type information (business group id was removed from this routine in version 115.8).
• SET_HSC_OBJECT — caches soft coding keyflex information.
• SET_PAD_OBJECT — caches person address details.
• SET_PIL_OBJECT — caches person-in-learner/extra assignment contexts.
• SET_PPS_OBJECT — caches period-of-service information, the routine returned when users search for "set_pps_object."

Tables Accessed

The package reads from core HR and benefits tables through APPS synonyms:

• PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F — person and assignment source records.
• PER_PERIODS_OF_SERVICE — period of service data cached by SET_PPS_OBJECT.
• PER_PERSON_TYPES and PER_PERSON_TYPE_USAGES_F — person type classification.
• PER_ASSIGNMENT_STATUS_TYPES — status lookups.
• PER_ASSIGNMENT_EXTRA_INFO and PER_ASSIGNMENT_BUDGET_VALUES_F — assignment supplements.
• PER_CONTACT_RELATIONSHIPS — participant contact data.
• PER_ADDRESSES — address information.
• HR_SOFT_CODING_KEYFLEX — soft coding keyflex structures.
• BEN_BNFTS_BAL_F and BEN_PER_BNFTS_BAL_F — benefits balance facts and person balance facts.
• BEN_PER_IN_LER — person life event records.
• PLITBLM — a PL/SQL index-by table type used in cache structures.

All access is read-oriented; the package populates caches rather than persisting business rows.

Usage Notes

BEN_PERSON_OBJECT is an internal benefits infrastructure package rather than a client-callable API. It is invoked by other benefits packages — ETRM records 29 referencing packages — typically as the first step in a benefits calculation, eligibility evaluation, or life event processing routine. Forms in the OAB module may trigger cache population indirectly through these callers. Custom extensions that process large volumes of benefits data can call the SET_* routines to prime the cache, but doing so requires care: the cache is session-scoped and must be refreshed when person or assignment data changes. Because the package is AUTHID CURRENT_USER and undocumented as a public API, direct invocation is not recommended for new development.