Results for “user_function_name”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKE_ROLE_FUNCTIONS_V is an Oracle E-Business Suite view owned by the APPS schema and registered under the OKE – Project Contracts product family. Its status is VALID in both 12.1.1 and 12.2.2. The view presents a denormalized, human-readable projection of the role-to-function authorization mappings maintained by Oracle Project Contracts, joining each stored mapping record to the function definition that it references. The result is a single logical row per (role, function) pair, carrying the audit columns of the mapping record alongside the descriptive function attributes.

Because Oracle EBS function security is the primary mechanism by which application responsibilities grant or withhold access to individual form functions, OKE_ROLE_FUNCTIONS_V serves as the reporting and integration surface for answering the question “which functions does this Project Contracts role expose, and what are those functions called?” Rather than forcing downstream queries to replicate the join between OKE_ROLE_FUNCTIONS and FND_FORM_FUNCTIONS_VL, the view encapsulates it, providing a stable, documented access path for custom reports, XML Publisher templates, and interface extracts.

Underlying Base Objects

The view text is a straightforward equijoin between two documented base objects:

• OKE_ROLE_FUNCTIONS (referenced in the view as the synonym OKE_ROLE_FUNCTIONS, aliased RF) — the transactional table that stores the role-to-function grants, including the standard EBS WHO columns.
• FND_FORM_FUNCTIONS_VL (aliased F) — the Oracle Application Object Library view that exposes form function definitions with their translatable name columns, keyed by FUNCTION_ID.

The join predicate is F.FUNCTION_ID = RF.FUNCTION_ID. FUNCTION_ID is the common key: it is the surrogate identifier assigned to each registered function in FND_FORM_FUNCTIONS, and it is the value stored on each OKE_ROLE_FUNCTIONS row. No outer join is applied, so any role/function mapping whose FUNCTION_ID has no matching row in FND_FORM_FUNCTIONS_VL would be excluded from the result set; conversely, functions defined in the foundation tables but never granted to an OKE role do not appear. The view therefore returns only the intersection — mappings that are both stored and resolvable.

Key Columns

• ROLE_ID — Identifier of the Project Contracts role to which the function grant belongs. This is the grouping key for role-centric reporting.
• FUNCTION_ID — Surrogate key of the granted form function; participates in the join to FND_FORM_FUNCTIONS_VL.
• FUNCTION_NAME — The internal, untranslated function name as registered in the application. Use this for joins, comparisons, and technical diagnostics.
• USER_FUNCTION_NAME — The user-facing, translatable function name as presented in the EBS user interface. Use this for report output and display.
• CREATION_DATE, CREATED_BY — Audit attributes recording when and by whom the role/function mapping row was created.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Audit attributes capturing the most recent modification of the mapping row, along with the login that performed it.

The audit columns originate from OKE_ROLE_FUNCTIONS; FUNCTION_NAME and USER_FUNCTION_NAME originate from FND_FORM_FUNCTIONS_VL. The view does not expose application or responsibility context, because those are associated at the menu/responsibility layer rather than at the role-function mapping layer.

Common Use Cases and Queries

Typical uses include security audits that enumerate the functions exposed by each Project Contracts role, gap analysis comparing granted functions against an intended baseline, and extracts feeding external authorization models. A representative query lists all functions for a given role with their user-facing names:

• SELECT role_id, function_id, function_name, user_function_name FROM apps.oke_role_functions_v WHERE role_id = :p_role_id ORDER BY user_function_name;
• SELECT f.user_function_name, COUNT(*) grant_count FROM apps.oke_role_functions_v f GROUP BY f.user_function_name HAVING COUNT(*) > 1 ORDER BY grant_count DESC; — identifies functions granted across multiple roles.
• SELECT rf.role_id, rf.user_function_name, rf.last_update_date, rf.last_updated_by FROM apps.oke_role_functions_v rf WHERE rf.last_update_date >= TRUNC(SYSDATE) - 30 ORDER BY rf.last_update_date DESC; — tracks recent changes to role-function mappings.

When reporting, filter by ROLE_ID to scope results, and prefer USER_FUNCTION_NAME for display while retaining FUNCTION_NAME for deterministic comparison. Because the view is read-only and defined entirely over base objects, it is safe for query-only responsibilities and requires no maintenance.