Search Results get_value_cache

Overview

PAY_FI_GENERAL is an Oracle E-Business Suite Payroll (Oracle HRMS) PL/SQL package owned by the APPS schema. It provides a consolidated library of utility routines that support payroll processing for legislations requiring holiday pay accrual, tax card handling, and formula-driven element calculations. The package name and internal structures (fi_cache_rec, fi_cache_table, g_fi_cache_table) indicate that it was originally developed for a Finnish localization ("FI") and has since been extended to cover generic payroll utilities referenced by multiple other packages.

The package serves two primary business functions. First, it resolves and evaluates accrual, holiday pay entitlement, and tax-day rules by invoking Fast Formula logic and caching the results for the duration of a payroll run. Second, it supplies a set of low-level helper routines for reading element entries, input values, balances, soft coding, and personal extra information. Because it is classified as an "OTHER" API, it is not part of a formally published integration interface, but it is widely referenced internally: the ETRM metadata documents that three other packages call into PAY_FI_GENERAL.

Key Procedures and Functions

The 30 documented routines fall into functional groups.

• Accrual and holiday entitlement: GET_ACCRUAL_STATUS determines the accrual status for a time definition and balance date range. GET_HOLIDAY_PAY_ACCR_OVERRIDE retrieves assignment-level overrides for holiday days, compensation, reserve, working days, and working hours. GET_HOLIDAY_PAY_ENTITLE_OVER and RUN_HOLIDAY_PAY_ENTITLEMENT resolve and execute holiday pay entitlement calculations for an assignment, returning summer and winter holiday days, holiday pay, compensation, carryover amounts, and average pay figures. RUN_HOLIDAY_PAY_FORMULA executes the associated Fast Formula.
• Tax processing: GET_TAX_CARD_DETAILS, GET_TAX_DAYS_OVERRIDE, RUN_TAX_DAYS_FORMULA, and GET_TAX_DETAILS support tax card validation and the calculation of tax days for a payroll period.
• Element and input value access: ELEMENT_EXIST is the routine matching the user's search term; it verifies whether a given element exists for an assignment and effective date. GET_INPUT_VALUE_IN_VARCHAR retrieves an element entry input value as a character string. CALC_SCH_BASED_DUR returns a schedule-based duration. GET_HOURLY_SALARIED_TYPE and GOOD_TIME_FORMAT classify the hourly/salaried type and validate time formats. GET_BALANCE_DATE derives a balance date from payroll context.
• Caching utilities: SET_VALUE_CACHE, GET_VALUE_CACHE, DELETE_CACHE_TABLE_ROW, and CLEAR_CACHE operate on the package-level g_fi_cache_table collection, allowing expensive lookups to be memoized during a run. PRINT1 is a debug/diagnostic output routine.

Tables Accessed

The package reads and writes against core HRMS and payroll tables via APPS synonyms.

• Element and entry data: PAY_ELEMENT_TYPES_F, PAY_ELEMENT_LINKS_F, PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, and PAY_INPUT_VALUES_F supply element definitions, linkage eligibility, entry records, and input value metadata used by ELEMENT_EXIST and the value-retrieval routines.
• Assignment and person data: PER_ALL_ASSIGNMENTS_F and PER_ALL_PEOPLE_F provide assignment and person context; PER_PEOPLE_EXTRA_INFO stores legislative extra information.
• Organization and coding: HR_ORGANIZATION_INFORMATION and HR_SOFT_CODING_KEYFLEX support organizational attributes and costing flexfield derivation.
• Time and formulas: PER_TIME_PERIODS defines payroll periods, and FF_FORMULAS_F stores the Fast Formula definitions executed by the RUN_* routines.
• Utility: DUAL is used for single-row evaluation, and PLITBLM is the standard EBS PL/SQL index-by table type used for internal collections.

Usage Notes

PAY_FI_GENERAL is typically invoked from Fast Formula contexts, payroll concurrent programs, and other payroll packages rather than from end-user Forms. Its caching routines are designed to be called early in a payroll run (SET_VALUE_CACHE, CLEAR_CACHE) so that repeated lookups during element processing return cached results. Custom code should treat these routines as internal: the API classification is OTHER, parameters are subject to change across patch levels, and no formal support commitment attaches to direct invocation. When extending or debugging, developers commonly reference ELEMENT_EXIST to confirm that a specific element is linked and valid for an assignment before attempting entry creation.