Results for “ff_functions”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FF_FUNCTIONS is a core metadata table in the Oracle E-Business Suite FastFormula (FF) module, residing in the HR schema. It stores the definitions of every function that can be referenced inside a FastFormula — the named callable routines, together with their data types, argument signatures, and implementation strings, that the FastFormula parser and interpreter use when compiling or executing a formula. Because FastFormula is the shared calculation and rule engine behind Oracle Payroll, Oracle HRMS, Oracle Advanced Benefits, Oracle Compensation Workbench, and numerous other products, FF_FUNCTIONS is effectively the function catalog for the entire FastFormula subsystem across release 12.1.1 and 12.2.2.

Under the heuristic Data Vault classification supplied with the ETRM metadata, FF_FUNCTIONS is characterized as hub-leaning. This suggests modeling FUNCTION_ID as a durable business key hub, with descriptive attributes (NAME, CLASS, DATA_TYPE, DEFINITION) held in an associated satellite, and the parameter and context-usage relationships represented as links to their respective tables.

Key Information Stored

The documented physical schema for 12.2.2 contains sixteen columns. The most significant are:

• FUNCTION_ID — surrogate primary key, enforced by FF_FUNCTIONS_PK.
• ZD_EDITION_NAME — editioning discriminator supporting Online Patching (AD_ZD) in 12.2.x; combined with FUNCTION_ID it forms the unique index FF_FUNCTIONS_PK (FUNCTION_ID, ZD_EDITION_NAME).
• NAME and ALIAS_NAME — the primary and alternate identifiers by which the function is invoked in formula text; these are the principal business-key candidates alongside FUNCTION_ID.
• CLASS — logical grouping or category of the function, used to organize the catalog.
• DATA_TYPE — the return type of the function (for example numeric, text, or date), which drives formula compilation checks.
• DEFINITION — the actual implementation or signature string executed by the FastFormula interpreter.
• BUSINESS_GROUP_ID — the enterprise/legislative grouping to which the definition belongs.
• LEGISLATION_CODE — country-specific localization, allowing different function sets per legislation.
• DESCRIPTION — human-readable explanation of the function's purpose.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard WHO audit columns.
• OBJECT_VERSION_NUMBER — optimistic locking column for concurrent access control.

Common Use Cases and Queries

Typical usage includes cataloging available functions for formula authors, troubleshooting compilation errors, auditing legislated customizations, and reporting on function coverage by class or data type. A basic lookup by name:

• SELECT function_id, name, class, data_type, legislation_code FROM hr.ff_functions WHERE name = :p_name;

Enumerating parameters for a specific function joins to FF_FUNCTION_PARAMETERS on FUNCTION_ID, while context usage is retrieved via FF_FUNCTION_CONTEXT_USAGES.FUNCTION_ID. Because ZD_EDITION_NAME participates in the unique index, queries on 12.2.x should filter or group on that column when reconciling editions after patching.

Related Objects

The ETRM relationship data identifies two direct dependent (child) tables, both keyed to FF_FUNCTIONS via FUNCTION_ID:

• FF_FUNCTION_PARAMETERS — FF_FUNCTION_PARAMETERS.FUNCTION_ID references FF_FUNCTIONS; holds argument definitions for each function.
• FF_FUNCTION_CONTEXT_USAGES — FF_FUNCTION_CONTEXT_USAGES.FUNCTION_ID references FF_FUNCTIONS; records the execution contexts in which a function may be used.

Additional objects commonly joined in practice include HR.FF_FORMULAS, which stores formula text that invokes these functions, and HR.FF_FORMULA_FUNCTIONS, which resolves the binding between formulas and their callable functions.