Search Results fnd_irep_function_flavors




Overview
Explore in AI Chat

Overview

FND_IREP_FUNCTION_FLAVORS is a configuration table in the APPLSYS schema belonging to the FND — Application Object Library product within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores overload flavors for functions registered in the EBS function registry. In the Oracle EBS architecture, a "function" is a granular unit of executable navigation or logic that is secured through menus and responsibilities. When a function has more than one callable signature or behavior — an overload — the flavor records defined in this table distinguish those variants by scope, lifecycle mode, and compatibility semantics. This allows the application to resolve the correct function variant at runtime based on the context in which it is invoked.

Under the heuristic Data Vault classification shown in the ETRM metadata, this object is modeled as a standalone table. Because the classification was derived from a limited foreign-key footprint, it should be treated as a modeling suggestion rather than a definitive hub, link, or satellite designation. Functionally, the table behaves as a detail or configuration store keyed to functional definitions, and its nine columns carry both identity and descriptive attributes.

Key Information Stored

The table's structure centers on a composite primary key and a set of flavor-defining attributes:

  • FUNCTION_ID — Identifies the parent function to which the overload flavor belongs. This is the principal link back to the EBS function registry.
  • OVERLOAD_SEQ — Sequence number that distinguishes multiple flavors of the same function. It participates in the composite primary key.
  • USER_FLAVOR_NAME — The user-facing name of the flavor, used when presenting or selecting the overload.
  • SCOPE_TYPE — Defines the scope or context in which the flavor applies.
  • LIFECYCLE_MODE — Indicates the lifecycle state or behavioral mode governing the flavor's availability.
  • COMPATIBILITY_FLAG — A flag indicating compatibility characteristics of the flavor.
  • DESCRIPTION — Full descriptive text for the flavor.
  • SHORT_DESCRIPTION — Abbreviated description used in list-based or constrained user interfaces.
  • ZD_EDITION_NAME — Editioning column supporting Oracle EBS 12.2 online patching and edition-based redefinition.

The documented primary key is FND_IREP_FUNCTION_FLAVORS_PK, defined on the composite of OVERLOAD_SEQ and FUNCTION_ID. The metadata also records a unique index, SYS_IL0000398806C00006$$, associated with a LOB segment rather than a true business-key candidate; the practical business identity of a row remains the composite primary key. No additional unique business-key candidates were documented beyond that internal index.

Common Use Cases and Queries

Typical use cases include auditing function overload definitions, validating that every registered function has consistent flavor records, and diagnosing runtime errors where the wrong overload signature is selected. Because the table is maintained by application setup rather than end-user transactions, queries are generally read-oriented and join to the function registry on FUNCTION_ID.

  • Listing all flavors for a given function: SELECT OVERLOAD_SEQ, USER_FLAVOR_NAME, SCOPE_TYPE, LIFECYCLE_MODE FROM FND_IREP_FUNCTION_FLAVORS WHERE FUNCTION_ID = :function_id ORDER BY OVERLOAD_SEQ;
  • Checking lifecycle mode distribution across the instance to identify stale or inactive flavors.
  • Verifying that every FUNCTION_ID present has at least one row with a non-null COMPATIBILITY_FLAG before an upgrade or patch cycle.
  • Reporting on editioned rows (ZD_EDITION_NAME) as part of EBS 12.2 online patching validation.

Related Objects

The relationship metadata classifies this object as standalone, meaning no foreign-key relationships were mined from the documented structure. In practice, the FUNCTION_ID column references the EBS function registry, and the following objects are most significant when working with this table: