Search Results fnd_user

Overview

The FND_USER table is the central repository for all user definitions within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. Owned by the APPLSYS schema and part of the Application Object Library (FND) module, it serves as the master table for user authentication, authorization, and profile management. Every individual who accesses the EBS application, whether an employee, customer, supplier, or system administrator, must have a corresponding record in this table. Its primary role is to store core user credentials and metadata, enabling system login, responsibility assignment, and user-level personalization across the entire application suite.

Key Information Stored

The table's structure is designed to manage user identity and access. The primary key is USER_ID, a unique numeric identifier. The USER_NAME column, also a unique key, stores the login username. Critical security columns include ENCRYPTED_USER_PASSWORD and ENCRYPTED_FOUNDATION_PASSWORD for authentication. Key descriptive columns include DESCRIPTION (full name), EMAIL_ADDRESS, and PERSON_PARTY_ID, which links the user to a person record in the Trading Community Architecture (TCA) via the HZ_PARTIES table. Status is managed through columns like START_DATE, END_DATE (for deactivating users), and PASSWORD_DATE. The table also includes audit columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY.

Common Use Cases and Queries

Common administrative and reporting tasks revolve around user management. A frequent query is to list active users: SELECT user_name, description, email_address, start_date FROM fnd_user WHERE sysdate BETWEEN start_date AND NVL(end_date, sysdate+1);. To find a user's responsibilities, FND_USER is joined with FND_USER_RESP_GROUPS_DIRECT. Resetting a password or reactivating an expired account are standard support procedures. For auditing, queries often join with FND_LOGINS to analyze access patterns. The user's search for "prp_email_history" suggests an interest in email notification history, which may involve joining FND_USER with workflow notification tables (e.g., WF_NOTIFICATIONS) using the USER_ID or USER_NAME as a key.

Related Objects

FND_USER is a foundational table referenced extensively throughout EBS. As indicated in the metadata, it has foreign key relationships with numerous application tables, including AP_EXPENSE_REPORT_HEADERS_ALL, AR_ACTION_NOTIFICATIONS, and AMS_LIST_HEADERS_ALL, tracking user actions across Financials, CRM, and other modules. Key related objects for user management include FND_USER_RESP_GROUPS_DIRECT (responsibility assignments), FND_PROFILE_OPTION_VALUES (user profile settings), and the TCA entity HZ_PARTIES for person details. Standard APIs for interacting with this table include FND_USER_PKG and the FND_USER_PUB package, which should be used for programmatic user creation and updates instead of direct DML.