Search Results set_function_mode




Overview
Explore in AI Chat

Overview

APPS.FND_FORM_FUNCTIONS_PKG is the table handler package for the FND_FORM_FUNCTIONS entity, the core metadata object that defines every form function registered in Oracle E-Business Suite. A form function is the executable entry point referenced by menus, responsibilities, and the function security model; each row describes a target form, web host, HTML call, or subfunction together with its application, parameters, and security attributes. The package encapsulates the DML and validation logic required to insert, update, lock, translate, and delete these definitions, isolating callers from the physical column layout of the underlying tables.

The package is registered under the FND product with a public scope, an active lifecycle, and a compatibility rating of S (supported). It is classified as a OTHER API within the ETRM metadata for 12.2.2 and carries the business entity category FND_FUNCTION. The header comment identifies it explicitly as a table handler for the FND_FORM_FUNCTIONS table, and its documented interface exposes fourteen procedures that cover the full maintenance lifecycle of a function definition. Several entry points are deliberately overloaded: the comments state that certain older signatures omit columns such as LAST_UPDATE_DATE, MAINTENANCE_MODE_SUPPORT, and CONTEXT_DEPENDENCE so that they remain callable from legacy Forms code, and those variants are marked obsolete for new development.

Key Procedures and Functions

  • INSERT_ROW — Creates a new form function record, including web host and agent details, HTML call, encryption and security flags, icon, region and object associations, form and application identifiers, parameters, type, user function name, and description, together with standard WHO audit columns. An older overload omitting newer columns is retained for backward compatibility.
  • LOCK_ROW — Acquires a row-level lock on an existing function definition for the columns supplied, supporting the optimistic locking pattern used by the Forms-based maintenance screens.
  • UPDATE_ROW — Modifies an existing function definition, applying the same attribute and audit column set as INSERT_ROW.
  • LOAD_ROW — Loads or refreshes a function definition, typically used by seed data and upgrade routines to synchronise shipped metadata.
  • DELETE_ROW — Removes a function definition from the repository.
  • ADD_LANGUAGE — Inserts translation rows for a function definition so that it becomes available in an additional language.
  • TRANSLATE_ROW — Maintains the translatable attributes, principally the user function name and description, for an existing definition.
  • SET_FUNCTION_MODE — Establishes or alters the function mode attribute associated with a function definition; this is the procedure most commonly referenced in searches relating to function mode maintenance.
  • FUNCTION_VALIDATION — Performs validation of function metadata, ensuring that the defined entry point and its associated attributes are internally consistent before the record is committed.

Tables Accessed

The package operates against FND_FORM_FUNCTIONS and its translated and security counterparts FND_FORM_FUNCTIONS_TL and FND_FORM_FUNCTIONS_S. It validates references to FND_APPLICATION, FND_FORM, and FND_OBJECTS to confirm that the owning application, target form, and associated object exist. Language handling draws on FND_LANGUAGES for ADD_LANGUAGE and TRANSLATE_ROW, while FND_LOOKUP_VALUES supplies lookup validation, notably for the function type. DUAL is used for trivial expression evaluation within the PL/SQL bodies.

Usage Notes

The package is invoked primarily from the Forms-based Form Functions maintenance UI, which calls INSERT_ROW, UPDATE_ROW, and LOCK_ROW as the user commits changes. Setup and patching utilities use LOAD_ROW to install or refresh seeded functions, and multilingual implementations use ADD_LANGUAGE and TRANSLATE_ROW to propagate definitions across installed languages. SET_FUNCTION_MODE is relevant when the operating mode of a defined function must be adjusted programmatically. Five other packages reference this API, confirming its role as a shared maintenance layer. Custom code should call the current supported overloads rather than the obsolete variants that omit the maintenance mode and context dependence columns; direct DML against FND_FORM_FUNCTIONS is strongly discouraged because it bypasses the audit, validation, and translation logic centralised here.