Search Results fetch_setup_formula_id




Overview

HRI_BPL_FAST_FORMULA_UTIL is a utility PL/SQL package owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the Oracle HRMS (Human Resources Management System) module, more specifically to the HR Intelligence / Business Intelligence foundation layer that supports FastFormula processing. Its primary purpose is to resolve the correct Formula identifier at runtime and to execute a FastFormula, given a set of input parameters.

The package addresses a recurring challenge in Oracle HRMS: multiple formulas may share the same name across different contexts — a Business Group, a Setup-level formula, or a seeded formula delivered by Oracle. Rather than forcing callers to know precisely which copy of a formula to use, this package encapsulates the lookup logic and search sequence. Callers supply a formula name and, optionally, business group and formula type context, and the package returns the appropriate formula ID. It also provides a single procedure to run the resolved formula with indexed VARCHAR2 input and output parameter tables.

Key Procedures and Functions

  • RUN_FORMULA — Executes a FastFormula identified by its formula ID. Accepts an input parameter table and returns an output parameter table, allowing callers to pass and retrieve named formula parameters.
  • FETCH_BG_FORMULA_ID — Returns the formula ID for a formula that belongs to a specific Business Group. It is overloaded to optionally accept a formula type name in addition to the formula name and business group ID.
  • FETCH_SETUP_FORMULA_ID — Returns the formula ID for a Setup-level formula identified by its name. Setup formulas are typically customer-defined defaults that apply across business groups.
  • FETCH_SEEDED_FORMULA_ID — Returns the formula ID for a seeded (Oracle-delivered) formula identified by its name. This is the function referenced by the search term "fetch_seeded_formula_id." It is the fallback resolver used when no customer-defined formula is found.
  • FETCH_FORMULA_ID — The composite resolver. Given a formula name plus optional business group, business group formula name, setup formula name, and seeded formula name, it returns the correct formula ID. Flags (p_try_bg_formula, p_try_setup_formula, p_try_seeded_formula) control which resolution paths are attempted, allowing callers to prioritize Business Group formulas, then Setup formulas, then seeded formulas.

Tables Accessed

  • FF_FORMULAS_F — The core FastFormula definition table. It stores formula names, formula IDs, and the association between formulas and their owning business group or context. The fetch functions query this table to resolve names to IDs.
  • FF_FORMULA_TYPES — Defines the category to which a formula belongs (for example, payroll, benefits, or accrual). It supports the overloaded FETCH_BG_FORMULA_ID variant that filters by formula type.
  • PLITBLM — A system table of long text lines used by the PL/SQL engine and by formula parsing and compilation logic. It is referenced when formula source text or compiled tokens must be processed during execution.

Usage Notes

This package is a utility (API classification: UTIL) and is not exposed directly through forms or concurrent programs. It is invoked programmatically:

  • By other PL/SQL packages — two packages in the EBS codebase reference it. These typically need to resolve and execute HRMS FastFormulas without hardcoding formula IDs.
  • In custom code and extensions where a developer must call a seeded or customer formula by name, honoring the standard Business Group → Setup → Seeded resolution priority.
  • When a formula may exist in multiple business groups, use FETCH_BG_FORMULA_ID with the appropriate business group ID to guarantee the correct variant is returned. Use FETCH_SEEDED_FORMULA_ID only when the Oracle-delivered version is explicitly intended.
  • Always pass the correct formula type where applicable; otherwise a name collision across formula types can return an unexpected ID.

Because the package is owned by APPS, custom callers should invoke it fully qualified as APPS.HRI_BPL_FAST_FORMULA_UTIL and should not assume signature stability across major releases beyond the documented forms.