Search Results fnd_user




The FND_USER table is a fundamental component of Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2, serving as the central repository for user account information. It stores critical details about individuals or system entities that interact with the Oracle EBS environment, including employees, suppliers, customers, and automated processes. This table is part of the Oracle Application Object Library (FND) and is essential for authentication, authorization, and user management within the EBS ecosystem.

Key Attributes of FND_USER

The FND_USER table contains several key columns that define user properties and access controls:
  • USER_ID: A unique numeric identifier for each user, serving as the primary key.
  • USER_NAME: The login name used for authentication (case-insensitive).
  • ENCRYPTED_USER_PASSWORD: Stores hashed passwords using Oracle's encryption algorithms.
  • SESSION_NUMBER: Tracks active sessions for the user.
  • START_DATE and END_DATE: Define the active period for the user account.
  • LAST_LOGON_DATE: Records the most recent successful authentication.
  • DESCRIPTION: Optional field for user information.
  • PASSWORD_DATE: Tracks when the password was last changed.
  • PASSWORD_ACCESSES_LEFT: Used for password attempt limitations.
  • EMAIL_ADDRESS: Stores the user's email for notifications.
  • FAX and PERSON_PARTY_ID: Additional contact and party reference information.

Integration with Oracle EBS Security

The FND_USER table integrates with several security components:
  • FND_USER_RESP_GROUPS: Links users to responsibilities (access profiles)
  • FND_RESPONSIBILITY: Defines application access rights
  • PER_ALL_PEOPLE_F: Integrates with HRMS for employee users
  • HZ_PARTIES: Connects to Trading Community Architecture for non-employee users

Technical Implementation Details

In Oracle EBS 12.1.1 and 12.2.2, the FND_USER table:
  • Uses Oracle's standard table naming conventions (FND prefix for Application Object Library)
  • Implements referential integrity through foreign keys
  • Is accessed through APIs like FND_USER_PKG for data manipulation
  • Supports Oracle's multi-org access control (MOAC) through ORG_ID context

Password Security Features

The table supports comprehensive password management:
  • Password encryption using SHA-1 or stronger algorithms
  • Password history tracking through FND_USER_PASSWORD_HISTORY
  • Complexity requirements enforcement
  • Expiration policies
  • Lockout mechanisms after failed attempts

Common Use Cases

Typical operations involving FND_USER include:
  • User account creation and maintenance
  • Authentication processes
  • Password reset procedures
  • User access reporting
  • Security audits
  • Integration with LDAP or SSO solutions

Performance Considerations

For optimal performance:
  • Indexes exist on USER_ID (PK) and USER_NAME
  • Regular purging of inactive accounts is recommended
  • Partitioning may be considered for very large implementations
  • Caching mechanisms are implemented at the application tier
The FND_USER table remains a critical component in Oracle EBS security architecture, providing the foundation for user identity management across all EBS modules. Its design reflects Oracle's comprehensive approach to enterprise security while maintaining flexibility for diverse implementation scenarios.