Search Results ff_function_context_usg_api




Overview
Explore in AI Chat

Overview

FF_FUNCTION_CONTEXT_USG_API is a public PL/SQL API in the APPS schema that manages the association between Oracle EBS Functions and the contexts in which those functions are made available. It is part of the Oracle Application Object Library (FND) family of "FF" packages, which together define the metadata that drives the menu and function security model. In Oracle EBS 12.1.1 and 12.2.2, every Function can be restricted so that it is only rendered or invoked when a particular runtime context is active (for example, a specific responsibility, business group, or operating unit). This package is the programmatic interface through which those function-to-context usages are created, maintained, and removed without direct DML against the underlying FND table.

The package is classified as an API and is documented as VALID in ETRM for 12.2.2. It depends on HR_API and the SYS.STANDARD package, and it is referenced by FF_FUNCTIONS_API, indicating that it plays a supporting role in the broader function definition lifecycle managed by the FF_FUNCTIONS_API package.

Key Procedures and Functions

Three documented procedures constitute the public interface of the package:

  • CREATE_CONTEXT — Inserts a new function-context usage record, establishing the relationship between a Function and the context in which it applies. This is the entry point used when a new function-to-context association must be registered in the metadata repository.
  • UPDATE_CONTEXT — Modifies an existing function-context usage record. It is used to change the attributes of an association that has already been created, preserving referential integrity with the Function definition.
  • DELETE_CONTEXT — Removes a function-context usage record. It is invoked when a previously defined association is no longer required, cleaning up the metadata so that the function is not constrained by an obsolete context.

No parameter lists are documented in the ETRM excerpt; therefore the exact signatures should be confirmed against the package specification in the target instance before any custom invocation.

Tables Accessed

The only table referenced by this package, via an APPS synonym, is FF_FUNCTION_CONTEXT_USAGES. This table stores the persistent mapping of functions to their applicable contexts. CREATE_CONTEXT writes rows to this table, UPDATE_CONTEXT modifies existing rows, and DELETE_CONTEXT removes them. The package does not write directly to the core FND function definition tables; those are managed by the related FF_FUNCTIONS_API package, which itself calls into FF_FUNCTION_CONTEXT_USG_API to keep the context-usage records consistent with the function definitions.

Usage Notes

FF_FUNCTION_CONTEXT_USG_API is typically invoked indirectly rather than by end users. The primary caller is FF_FUNCTIONS_API, which uses it to synchronize function-context usages whenever a function is defined, modified, or deleted through the standard EBS function maintenance flow. In 12.1.1 and 12.2.2, these operations are normally reached through the Forms-based Function and Menu administration screens, or through the corresponding concurrent and loader programs that seed function metadata.

Custom code should invoke this package only when a bespoke requirement exists to manage function-context associations programmatically. Because the package is a documented API with a VALID status, it is the supported alternative to direct INSERT, UPDATE, or DELETE statements against FF_FUNCTION_CONTEXT_USAGES. Developers should call the three procedures with commit semantics appropriate to their transaction, confirm the exact parameter signatures from the package specification, and verify that no active FF_FUNCTIONS_API processing is in progress that could conflict with the change. Direct DML on the underlying table is not recommended, as it bypasses the validation and dependency handling implemented within the API.