Search Results oke_role_functions




Overview
Explore in AI Chat

Overview

OKE_ROLE_FUNCTIONS is a reference table in the OKE (Project Contracts) module of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. It defines the allowable functions available to each role within the Oracle Contracts Core security model. Each row represents a single grant of a form function to a role, forming the atomic unit of functional privilege assignment in the contract authoring and administration environment. The table therefore acts as the junction that binds a security role to a specific function registered in Oracle Application Object Library.

From a dimensional modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table carries no independent descriptive attributes of its own; it records the association between two business entities and would typically be modeled as a link or satellite hanging off the ROLE and FUNCTION hubs rather than as a hub itself.

Key Information Stored

The documented physical schema contains seven columns in the OKE schema. The most significant are:

  • ROLE_ID — The identifier of the security role to which a functional privilege is granted. Forms part of the composite primary key.
  • FUNCTION_ID — The identifier of the form function being granted, sourced from FND_FORM_FUNCTIONS. Forms the second component of the composite primary key.
  • CREATION_DATE — Timestamp when the role-to-function grant row was created.
  • CREATED_BY — The application user who created the grant record.
  • LAST_UPDATE_DATE — Timestamp of the most recent modification to the grant.
  • LAST_UPDATED_BY — The user who last modified the record.
  • LAST_UPDATE_LOGIN — The login session associated with the most recent update.

The surrogate primary key is OKE_ROLE_FUNCTIONS_PK, defined over (ROLE_ID, FUNCTION_ID). A unique index, OKE_ROLE_FUNCTIONS_U1, covers the same two columns, confirming that the business key of a role-function pairing is unique and that duplicate grants are not permitted. The audit columns (CREATION_DATE through LAST_UPDATE_LOGIN) follow Oracle's standard WHO-column convention and are populated automatically by the application.

Common Use Cases and Queries

Typical usage centers on security auditing, role provisioning analysis, and reporting on functional access within Project Contracts. Administrators and auditors frequently need to enumerate all functions granted to a given role, or conversely, to identify every role that holds a particular function.

A representative query listing functions for a specific role joins to FND_FORM_FUNCTIONS:

  • SELECT f.function_name, f.user_function_name FROM oke_role_functions rf, fnd_form_functions f WHERE rf.function_id = f.function_id AND rf.role_id = :p_role_id;
  • SELECT rf.role_id, rf.function_id FROM oke_role_functions rf WHERE rf.function_id = :p_function_id;

These patterns support segregation-of-duties reviews, comparison of role definitions across environments, and impact analysis before modifying or retiring a function definition. Because the table stores only grant rows, reporting should always resolve the human-readable role and function names through their respective parent tables.

Related Objects

The following objects are most significant to OKE_ROLE_FUNCTIONS and join directly on the documented columns:

  • FND_FORM_FUNCTIONS — Referenced by OKE_ROLE_FUNCTIONS.FUNCTION_ID; the authoritative source of function names, descriptions, and associated form or web entry points.
  • OKE_ROLES (and its siblings in the OKE security hierarchy) — The role definition side of the relationship, joined on ROLE_ID.
  • FND_COMPILED_MENU_FUNCTIONS — Provides the menu structure through which granted functions are exposed to users.
  • FND_RESPONSIBILITY and FND_USER_RESP_GROUPS — Connect roles and responsibilities to end users for effective-privilege reporting.
  • FND_APPLICATION — Identifies the owning application of each function for module-scoped audits.

Together with these objects, OKE_ROLE_FUNCTIONS provides the queryable linkage between Oracle Project Contracts roles and the functions they are permitted to execute.