Search Results ff_compiled_info_x




Overview
Explore in AI Chat

Overview

FF_COMPILED_INFO_X is a date-effective (date-tracked) view owned by the APPS schema in Oracle E-Business Suite. It belongs to the FastFormula (FF) product family and exposes the compiled representation of FastFormula definitions as stored in the underlying FF_COMPILED_INFO_F table. In Oracle EBS 12.1.1 and 12.2.2, FastFormula is the rule and calculation engine used across modules such as Payroll, Human Resources, Benefits, Compensation, and Advanced Supply Chain Planning. When a formula is compiled, Oracle EBS stores both the source token information and the compiled executable text so that the runtime engine can evaluate the formula without recompiling on every execution.

The "_X" suffix in the object name is the Oracle Applications convention for a date-effective (translated) view. The view dynamically resolves the row that is valid as of the current system date by filtering on EFFECTIVE_START_DATE and EFFECTIVE_END_DATE. This allows multiple versions of compiled formula information to coexist in the foundation table while the view always presents the single currently effective version. This role is significant for reporting and integration because consumers can query the view without needing to construct their own effective-date predicates.

Underlying Base Objects

FF_COMPILED_INFO_X is defined over a single referenced base object, FF_COMPILED_INFO_F, which is exposed to the view through a synonym. The "_F" suffix denotes the foundation (non-translated, date-effective) table that physically stores all effective-dated rows. The view text is:

The predicate TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE is what makes the view date-effective. Because the filter uses SYSDATE rather than a bind parameter, the row returned changes automatically as time passes and new versions are inserted. The relationship is therefore one-to-many at the base-table level but presented as effectively one row per FORMULA_ID through the current-date filter. Note that the view carries no join to FF_FORMULAS; FORMULA_ID is the linking key that must be joined externally to obtain descriptive formula attributes such as formula name or type.

Key Columns

  • FORMULA_ID — The unique identifier of the FastFormula definition. This is the primary join key to FF_FORMULAS and other FastFormula metadata objects.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The date-effective range defining the validity period of this compiled version. These columns drive the view's current-date filtering logic.
  • FDIU_ENTRY_COUNT — The count of FDIU (FastFormula Database Item Unit) entries referenced by the compiled formula. It reflects how many database items the formula accesses at runtime.
  • SELECT_STATEMENT_COUNT — The number of SELECT statements contained in the compiled formula, useful for performance and tuning analysis of formula logic.
  • TEXT_LENGTH — The character length of the compiled formula text held in COMPILED_TEXT. This column is frequently used to gauge formula size and complexity.
  • COMPILED_TEXT — The compiled executable text of the FastFormula as generated by the compiler. This is the payload consumed by the FastFormula runtime engine.

Common Use Cases and Queries

Typical scenarios include auditing formula compilation output, measuring formula complexity, identifying formulas with large compiled bodies, and diagnosing runtime behavior tied to database item or SELECT usage. The many-to-one effective-date filter of the view makes it convenient for "current state" reporting.

To list currently effective compiled formulas joined to their descriptive metadata:

  • SELECT f.formula_name, f.formula_type, c.text_length, c.fdiu_entry_count, c.select_statement_count FROM apps.ff_compiled_info_x c, apps.ff_formulas f WHERE c.formula_id = f.formula_id ORDER BY c.text_length DESC;

To identify the largest compiled formulas for tuning review:

  • SELECT formula_id, text_length, compiled_text FROM apps.ff_compiled_info_x WHERE text_length > 10000 ORDER BY text_length DESC;

To inspect the full compiled body for a specific formula:

  • SELECT formula_id, effective_start_date, effective_end_date, compiled_text FROM apps.ff_compiled_info_x WHERE formula_id = :formula_id;

Because the view resolves only the currently effective row, historical analysis of prior compiled versions requires querying FF_COMPILED_INFO_F directly with explicit date predicates.