Results for “function_class”

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

Overview

FF_FUNCTIONS_V is an Oracle E-Business Suite view owned by the APPS schema and registered under the FF (FastFormula) product family. Its documented purpose within ETRM is to support the FastFormula user interface, presenting function definitions in a denormalized, user-friendly form rather than requiring the UI layer to resolve lookup codes independently. The view remains VALID in both EBS 12.1.1 and 12.2.2 and is available across all reporting and integration channels that can reach the APPS schema, including BI Publisher, Oracle Reports, OAF-based pages, and custom PL/SQL packages.

Because FastFormula is the shared expression language used by Oracle Payroll, Oracle HRMS, Oracle Time and Labor, Oracle Advanced Benefits, and similar modules, this view provides a single consistent window onto the function library those products rely on. The searched term alias_name is one of the columns exposed directly by the view, making FF_FUNCTIONS_V the standard entry point for identifying how a function is referenced in formula text versus how it is labeled.

Underlying Base Objects

The view is defined over two APPS synonyms:

• FF_FUNCTIONS — the primary table that stores each FastFormula function, its class, data type, definition text, alias, legislation, and audit columns.
• FF_LOOKUPS — the lookup table that supplies decoded meanings for the FUNCTION_CLASS and DATA_TYPE lookup types.

The view text performs two outer joins between FF_FUNCTIONS and FF_LOOKUPS: one constrained to LOOKUP_TYPE = 'FUNCTION_CLASS' matched against FF.CLASS, and a second constrained to LOOKUP_TYPE = 'DATA_TYPE' matched against FF.DATA_TYPE. As a result, function class and data type appear both as raw codes and as their translated meanings. Note that the ROWID of the base FF_FUNCTIONS row is exposed as ROW_ID, and the view is not key-preserving in a manner that guarantees DML through the view; it is intended as a query-only read model.

Key Columns

• ROW_ID — the FF_FUNCTIONS ROWID, useful for locating the underlying row.
• FUNCTION_ID — the primary key of the function definition.
• CLASS_CODE / CLASS — the raw lookup code and its meaning for FUNCTION_CLASS, indicating the functional grouping of the function.
• NAME — the internal name of the FastFormula function.
• ALIAS_NAME — the alias by which the function can be referenced; frequently used to locate a function when the formula author knows only the shorthand token.
• DATA_TYPE_CODE / DATA_TYPE — the raw code and decoded meaning of DATA_TYPE, identifying the return or parameter data type.
• DEFINITION — the definition body or signature of the function.
• BUSINESS_GROUP_ID — the business group scoping the row; null indicates a seeded, global definition.
• LEGISLATION_CODE — the legislation the function is restricted to, where applicable.
• DESCRIPTION and the standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

Typical use cases include auditing the function library, resolving an alias to a function name, and filtering functions by class or data type for documentation and impact analysis.

Locate a function by alias:

SELECT function_id, name, alias_name, class, data_type
FROM   apps.ff_functions_v
WHERE  upper(alias_name) = upper(:p_alias);

List all functions of a given class:

SELECT name, alias_name, data_type, legislation_code
FROM   apps.ff_functions_v
WHERE  class_code = 'FUNCTION_CLASS_CODE'
ORDER  BY name;

Inventory seeded versus business-group-specific definitions:

SELECT business_group_id, COUNT(*)
FROM   apps.ff_functions_v
GROUP  BY business_group_id;

Because the view joins two lookups, it should be treated as read-only, and queries returning ALIAS_NAME should account for nulls, as not every function is assigned an alias.