Search Results igw_org_map_details

Overview

FND_USER is the core identity table of Oracle E-Business Suite, owned by the APPLSYS schema and belonging to the FND — Application Object Library product. It represents every application user provisioned within an EBS instance, whether an internal employee, a supplier contact, or a customer-facing self-service user. Each row defines a login identity together with its authentication credentials, effective dating, password policy attributes, and optional links to HR, trading partner, and customer master records.

FND_USER functions as a central reference point across virtually every EBS module. Functional setups, concurrent requests, workflow approvals, personalizations, and audit columns throughout the database resolve to a user identity through this table. Given its role as the stable, uniquely identified source of user records referenced by an extremely large number of foreign keys, the heuristic Data Vault classification of hub is appropriate: FND_USER is best modeled as a business key hub (USER_ID / USER_NAME) with dependent reference attributes carried in adjoining satellites, and its many inbound foreign keys treated as links to downstream transactional or setup hubs.

Key Information Stored

The table is documented with 27 columns in the 12.2.2 physical schema. The most significant are:

• USER_ID — Surrogate primary key (FND_USER_PK); the internal identifier used by all foreign-key references. Also exposed as unique index FND_USER_U1.
• USER_NAME — The login name presented to the user; the principal business-key candidate, enforced by unique index FND_USER_U2.
• ENCRYPTED_USER_PASSWORD and ENCRYPTED_FOUNDATION_PASSWORD — Hashed credential values used for authentication, including the foundation-layer password used by forms and concurrent processing.
• WEB_PASSWORD — Credential used for self-service and web-based access.
• START_DATE and END_DATE — Effective-dating range that determines whether the account is currently active, future-dated, or terminated.
• LAST_LOGON_DATE — Timestamp of the most recent successful sign-on; widely used for dormant-account reporting.
• PASSWORD_DATE, PASSWORD_ACCESSES_LEFT, PASSWORD_LIFESPAN_ACCESSES, PASSWORD_LIFESPAN_DAYS — Password policy state used by sign-on validation and expiry enforcement.
• EMPLOYEE_ID — Optional link to the HR employee record for internal users.
• CUSTOMER_ID and PERSON_PARTY_ID — Optional links to HZ_PARTIES, identifying customer or person-party associations for external users.
• SUPPLIER_ID — Optional supplier association for iSupplier and procurement-facing users.
• EMAIL_ADDRESS and FAX — Contact attributes used by workflow notification and approval routing.
• USER_GUID — Globally unique identifier supporting integration and single sign-on scenarios.
• DESCRIPTION — Free-text annotation for administrative reference.

Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the remaining technical columns complete the structure.

Common Use Cases and Queries

Typical scenarios include user provisioning audits, dormant or terminated account reviews, password expiry monitoring, and resolving user IDs to display names in reports. Common query patterns include:

• Listing all active users: SELECT user_id, user_name, start_date, end_date FROM fnd_user WHERE SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1);
• Identifying dormant accounts: SELECT user_name, last_logon_date FROM fnd_user WHERE last_logon_date < ADD_MONTHS(SYSDATE, -6);
• Resolving a user name to an ID from audit columns: SELECT created_by, user_name FROM fnd_user; joined to any transactional table on CREATED_BY or LAST_UPDATED_BY.
• Retrieving the current session user via the standard profile value, joined to FND_USER for reporting.
• Reporting on external users by filtering on CUSTOMER_ID, SUPPLIER_ID, or PERSON_PARTY_ID to isolate customer, supplier, or party-linked accounts.

Related Objects

FND_USER participates in an extensive web of relationships. The most significant are:

• HZ_PARTIES — Referenced through FND_USER.CUSTOMER_ID and FND_USER.PERSON_PARTY_ID, linking users to trading partner master data.
• PSB_EMPLOYEES — Referenced through FND_USER.EMPLOYEE_ID for internal user-to-employee association.
• FND_LOGINS and FND_UNSUCCESSFUL_LOGINS — Reference USER_ID and record successful and failed authentication events.
• FND_CONCURRENT_REQUESTS — References FND_USER through REQUESTED_BY, identifying who submitted each concurrent program.
• FND_PROFILE_OPTION_VALUES — References LEVEL_VALUE, storing user-level profile option settings.
• FND_USER_PREFERENCES and FND_USER_DESKTOP_OBJECTS — Hold per-user preferences and desktop configuration, joined on USER_NAME and USER_ID respectively.
• ICX_SESSIONS and ICX_FAILURES — Track self-service session activity and access failures by user.
• JTF_TASKS_B and JTF_TASK_AUDITS_B — Reference assignor and assignee user IDs for CRM task management.
• UMX_REG_REQUESTS — Records user provisioning requests through the User Management infrastructure.
• AP_WEB_PROXY_ASSIGNMENTS — References ASSIGNOR_ID and ASSIGNEE_ID, governing approval delegation between users.