Search Results get_run_function_link




Overview

FND_RUN_FUNCTION is a public PL/SQL package in the APPS schema that serves as the core interface for generating URLs that execute Oracle EBS functions within a defined security context. Its primary consumer is the Oracle Workflow engine, which relies on it to build navigable links that launch forms-based functionality directly from workflow notifications and other generated pages. The package is classified under the ETRM business entity FND_NAVIGATION and carries the display name "Function Security Navigation," reflecting its role in bridging stored function definitions with runtime execution while honoring responsibility, application, and security group boundaries.

The package header dates to release 12.0 and was last revised in 2008, and it remains active and documented in both 12.1.1 and 12.2.2. It is referenced by 21 other packages, underscoring its position as a shared utility rather than an application-specific routine. The user search term "get_run_function_link" corresponds directly to one of the package's documented functions, which is the primary entry point for constructing hyperlinks to executable functions.

Key Procedures and Functions

  • GET_RUN_FUNCTION_LINK — Returns a URL to execute a specified function within a given security context. The caller supplies a function identifier together with responsibility, application, and security group parameters. If the responsibility is not known in advance, nulls may be passed, and the user is presented with a list of responsibilities in which the function is available after navigating to the generated URL. An optional parameters argument allows arguments to be passed to functions that accept them, and an override agent argument exists for internal use. An organization identifier can further restrict the responsibility list when no responsibility is supplied.
  • GET_RUN_FUNCTION_URL — Produces the underlying URL used to launch the requested function. This function supports the link-generation behavior above and isolates URL construction from the surrounding rendering logic.
  • GET_FORMS_LAUNCHER_SETUP — Returns the iframe tag and JavaScript initialization code required by the Forms Launcher. This HTML must be emitted on any page that contains links generated by GET_RUN_FUNCTION_LINK for FORM-type functions, so the launcher infrastructure is present when the user activates the link.

Two additional documented functions complete the package's five-entry interface, consistent with this family of URL and launcher utilities.

Tables Accessed

The package reads from several core Application Object Library tables through APPS synonyms. FND_FORM_FUNCTIONS supplies the function definition being executed. FND_APPLICATION and FND_RESPONSIBILITY are consulted to resolve and validate the responsibility and application context, and to build the list of responsibilities in which a function is available when none is specified. FND_SECURITY_GROUPS provides the security group context that scopes the execution. DUAL is used for single-row evaluations. No write operations against application data are documented; the package is a read-only configuration and navigation utility.

Usage Notes

FND_RUN_FUNCTION is typically invoked programmatically rather than through a standard concurrent program or form. Workflow notification templates and custom PL/SQL that embed actionable links call GET_RUN_FUNCTION_LINK to obtain a URL, then render GET_FORMS_LAUNCHER_SETUP output on the same page when the target is a form function. Developers extending workflow or building custom navigation should treat these functions as the supported public interface and avoid constructing function URLs manually, since responsibility and security group validation are performed within the package. Because nulls are accepted for responsibility parameters, the package also supports "function-first" navigation, where users select an authorized responsibility after following the link.