Search Results fnd_run_function




Overview
Explore in AI Chat

Overview

FND_RUN_FUNCTION is an Oracle E-Business Suite Applications (APPS) PL/SQL package body that provides the runtime mechanism for resolving and launching Oracle Forms-based functions from within the EBS environment. In the Oracle EBS architecture, a "function" is a form, subfunction, or other executable unit that is granted to responsibilities and made available to users through the menu hierarchy. The FND_RUN_FUNCTION package translates a function reference into an executable launcher URL or link that the Applications framework can dispatch to the Forms server.

The package operates within the Applications security and session management layers. It validates that the requested function is accessible to the current user's active responsibility, applies session and security-group considerations, and constructs the appropriate launch parameters. Because it bridges the stored function definitions held in the FND_FORM_FUNCTIONS tables with the runtime behavior of the Forms listener, it forms a critical part of the navigation and function-execution subsystem in both Oracle EBS 12.1.1 and 12.2.2. The object is documented as VALID in the APPS schema, with a public API classification of OTHER, indicating it is an internal framework utility rather than a published integration API.

Key Procedures and Functions

The ETRM metadata documents five procedures and functions within this package, of which three are named:

  • GET_FORMS_LAUNCHER_SETUP — Retrieves the configuration required to launch an Oracle Forms-based function. This includes resolving the Forms launcher parameters and server-side setup values needed for the session to open the correct form with the correct context.
  • GET_RUN_FUNCTION_URL — Constructs and returns the URL that, when invoked, runs the specified function. This is the core resolution routine that translates a function identifier into a navigable address consumed by the EBS framework or browser session.
  • GET_RUN_FUNCTION_LINK — Produces the rendered link (typically HTML anchor markup) used in the user interface to invoke the function. This is the presentation-layer counterpart to the URL generation routine.

The remaining two documented procedures are not individually named in the metadata; they support the resolution, validation, and session-handling logic used by the three routines above. No parameter lists are asserted here, as the metadata does not enumerate them.

Tables Accessed

The package reads from several core Applications dictionary and security tables through APPS synonyms:

  • FND_FORM_FUNCTIONS and FND_FORM_FUNCTIONS_VL — the function definitions, providing the form name, parameters, and descriptive attributes.
  • FND_APPLICATION — resolves the application to which a function belongs, used for security grouping and context.
  • FND_RESPONSIBILITY — validates that the current responsibility is entitled to the requested function.
  • FND_SECURITY_GROUPS — applies security-group filtering when determining function accessibility.
  • DUAL — used for single-row evaluations and default computations.

Collectively these accesses enforce the responsibility-based access model while assembling the launch metadata.

Usage Notes

FND_RUN_FUNCTION is an internal framework dependency rather than a standalone callable API. It is invoked by the EBS navigation and Forms-launching infrastructure when a user selects a function from a menu or when the framework builds navigation links. The metadata records that it is referenced by 21 other packages but is not itself referenced by any database object, confirming its role as a low-level utility consumed by higher-level navigation packages. It relies heavily on FND_PROFILE, FND_SESSION_MANAGEMENT, FND_SESSION_UTILITIES, FND_WEB_SEC, and FND_WEB_CONFIG for session context and security validation. Customizations should not call these routines directly; instead developers should use supported navigation APIs. Understanding this package is primarily relevant for troubleshooting function-launch failures, URL construction issues, and responsibility-access problems in EBS 12.1.1 and 12.2.2 environments.