Search Results fnd_user_ap_pkg




Overview
Explore in AI Chat

Overview

FND_USER_AP_PKG is a lightweight Oracle Application Object Library (FND) package owned by the APPS schema that provides a convenience wrapper for resolving an internal FND user identifier into the corresponding application user name. The header comment indicates the package has been part of the EBS codebase since 1999 and has remained essentially unchanged through the 12.1.1 and 12.2.2 releases, which is consistent with its role as a stable, low-level utility rather than a business-logic API. Because it is granted to PUBLIC through the standard APPS synonym (APPS.FND_USER_AP_PKG) and declared with AUTHID CURRENT_USER, it executes with the privileges of the calling session rather than the defining schema, allowing any EBS session to resolve user names without requiring direct SELECT privileges on FND_USER.

Key Procedures and Functions

The package exposes a single documented function, GET_USER_NAME. It accepts an internal user identifier (l_user_id of type NUMBER) and returns the corresponding user name as a VARCHAR2, or NULL if no matching FND_USER row exists. The function is declared with PRAGMA RESTRICT_REFERENCES(get_user_name, WNDS, WNPS, RNPS), which guarantees to the PL/SQL compiler that the function writes no database state, writes no package state, and reads no package state. This assertion permits the function to be called safely from SQL statements, from parallel-enabled contexts, and from other PL/SQL programs that require purity guarantees. No other procedures, functions, or overloads are documented in the package specification.

Tables Accessed

The package reads a single table: FND_USER, accessed through the APPS synonym. It performs a lookup keyed on USER_ID and projects the USER_NAME column. Because of the RESTRICT_REFERENCES pragma, the function is read-only: no INSERT, UPDATE, or DELETE operations are performed against FND_USER or any other table. This design reflects the package's narrow purpose — user-name translation — and keeps it safe for high-frequency use inside SQL queries and views.

Usage Notes

GET_USER_NAME is typically invoked from Forms, concurrent programs, and custom PL/SQL or SQL code whenever a stored numeric user ID must be rendered as a human-readable name, for example in reports, audit displays, and workflow notifications. The RESTRICT_REFERENCES pragma makes it particularly useful inside SELECT statements, such as SELECT fnd_user_ap_pkg.get_user_name(created_by) FROM <table>, without incurring purity violations. The ETRM metadata records that the package is referenced by twelve other packages, confirming its role as a shared low-level utility within the FND stack. Note that this function returns the user name only; it does not account for effective dates, end-dated users, or case-insensitive lookups in the same way as higher-level FND_USER_PKG utilities. For current-user context, most EBS code should prefer FND_GLOBAL.USER_ID combined with this package, or the more feature-rich FND_USER_PKG, whereas FND_USER_AP_PKG remains appropriate for simple, read-only ID-to-name resolution.