Search Results get_years_in_position




Overview

BEN_CWB_PERSON_INFO_PKG is an APPS-owned PL/SQL package within the Oracle EBS Advanced Benefits (BEN) module, specifically supporting the Compensation Workbench (CWB) feature set. Its core responsibility is to assemble, derive, and persist person-level compensation information used by Compensation Workbench planners and summary processes. The package aggregates workforce attributes — job tenure, grade characteristics, salary currency, FTE factor, and comparatio/range positioning — into the BEN_CWB_PERSON_INFO staging table, which downstream CWB components consume. It is classified as an OTHER API in the ETRM registry and remains in VALID status under both 12.1.1 and 12.2.2. Its exposure of sixteen documented procedures and functions positions it as a reusable calculation library rather than a single-entry API, invoked by multiple sibling packages including BEN_CWB_DYN_CALC_PKG, BEN_CWB_CD_SUMMARY_PKG, BEN_CWB_REFRESH_PKG, and BEN_MANAGE_CWB_LIFE_EVENTS.

Key Procedures and Functions

The documented procedures fall into four functional clusters:

Tables Accessed

Via APPS synonyms, the package reads primarily from HR and BEN transactional tables and writes to its own staging table:

Usage Notes

The package is normally invoked indirectly. CWB worksheet generation, refresh concurrent programs, and life-event processing (BEN_MANAGE_CWB_LIFE_EVENTS) call REFRESH_PERSON_INFO and its variants to synchronize person data before planners access the Compensation Workbench. Derived functions such as GET_GRD_COMPARATIO and GET_FTE_FACTOR are called by BEN_CWB_DYN_CALC_PKG during dynamic award calculations, and by BEN_EVALUATE_ELIG_PROFILES and BEN_EVALUATE_RATE_PROFILES during eligibility and rate evaluation. PER_SALADMIN_UTILITY references it for salary administration validation. Customers extending CWB should treat this package as a stable dependency; direct invocation is uncommon, but custom refresh logic may call REFRESH_PERSON_INFO_GROUP_PL after bulk data loads. Because it is an OTHER-classified API, Oracle does not guarantee interface stability across patches, and any custom code should verify signatures against the current application version.