Results for “ff_function_context_usages”

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

Overview

FF_FUNCTION_CONTEXT_USAGES is an HR-schema table within the FastFormula (FF) product family in Oracle EBS 12.1.1 and 12.2.2. Its documented purpose is to record the contexts required by a function — that is, the set of named FastFormula contexts that a given function depends upon when it is compiled or executed. In the FastFormula architecture, functions are reusable computational units that may reference contextual values such as effective dates, assignment identifiers, or payroll run attributes. This table captures that dependency relationship, ensuring the formula engine can resolve the appropriate context values before a function is evaluated.

The table is classified, per heuristic analysis of its foreign-key structure, as a link table in a Data Vault modeling sense. This is a modeling suggestion rather than a physical designation: the table resolves a many-to-many association between functions and contexts and carries no descriptive attributes of its own beyond the mandatory audit and versioning columns. It is a pure intersection entity whose grain is one row per function-context pairing, ordered by sequence.

Key Information Stored

The documented physical schema contains ten columns, of which the most significant are the following.

• FUNCTION_ID — Foreign key to FF_FUNCTIONS, identifying the function for which a context dependency is declared. This column participates in both unique indexes.
• CONTEXT_ID — Foreign key to FF_CONTEXTS, identifying the specific context that the function requires. Together with FUNCTION_ID it forms the business-key unique index.
• SEQUENCE_NUMBER — Orders the contexts associated with a function, which is significant where the evaluation order of contexts matters. It forms part of the primary key.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications framework to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording when and by whom the row was last modified.
• CREATED_BY, CREATION_DATE — Standard audit columns recording row creation.
• ZD_EDITION_NAME — Editioning column present in the 12.2.2 schema, supporting the Online Patching / Edition-Based Redefinition model.

The surrogate primary key is FF_FUNCTION_CONTEXT_USAGES_PK, defined on (FUNCTION_ID, SEQUENCE_NUMBER, ZD_EDITION_NAME). The second unique index, FF_FUNCTION_CONTEXT_USAGES_UK2, is defined on (FUNCTION_ID, CONTEXT_ID, ZD_EDITION_NAME) and constitutes the true business-key candidate, since it enforces that a function cannot declare the same context twice. Note the divergence between the primary key and business key: the primary key uses the ordering column, while the business key uses the context identity.

Common Use Cases and Queries

Typical usage centers on introspection and dependency analysis of FastFormula definitions. Developers and support analysts query this table to determine which contexts a function requires, to trace the impact of changing or removing a context, and to validate that function-context wiring is complete before a formula is compiled.

A common reporting pattern joins the table to both parent tables to produce a readable inventory of function dependencies:

• SELECT f.function_name, c.context_name, fu.sequence_number FROM hr.ff_function_context_usages fu, hr.ff_functions f, hr.ff_contexts c WHERE fu.function_id = f.function_id AND fu.context_id = c.context_id ORDER BY f.function_name, fu.sequence_number;
• To find all functions requiring a specific context, filter on c.context_name and enumerate the matching function rows.
• To detect ordering anomalies, compare the SEQUENCE_NUMBER values per FUNCTION_ID for gaps or duplicates.
• For impact analysis before a context is retired, join against FF_CONTEXTS by CONTEXT_ID and count dependent functions.

Because the table is editioned, queries issued against a non-editioned session resolve to the appropriate edition automatically; upgrade and patching scripts should account for ZD_EDITION_NAME when constructing direct DML.

Related Objects

This table sits at the intersection of two parent entities and is meaningful only in combination with them.

• FF_FUNCTIONS — parent table referenced via FUNCTION_ID; supplies function identity and definition metadata.
• FF_CONTEXTS — parent table referenced via CONTEXT_ID; supplies context names and semantics.
• FF_FUNCTION_CONTEXT_USAGES_PK — primary-key index on (FUNCTION_ID, SEQUENCE_NUMBER, ZD_EDITION_NAME).
• FF_FUNCTION_CONTEXT_USAGES_UK2 — unique business-key index on (FUNCTION_ID, CONTEXT_ID, ZD_EDITION_NAME).
• FF_FORMULAS and related FastFormula definition tables — functions declared here are referenced by formulas that bind context values at runtime.
• FF_CONTEXT_USAGES — the companion usage table at formula level, useful for comparing formula-declared contexts against function-required contexts.

Collectively these objects form the metadata backbone that the FastFormula compiler and runtime consult to resolve required context values for any function invoked during formula evaluation.