Results for “password_date”

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

Overview

JTF_FM_FND_USER_V is a database view owned by the APPS schema within the JTF – CRM Foundation product family. As documented in the ETRM repository, the view is a projection over the FND_USER table, exposing a defined subset of its columns together with two derived fields: F_DELETEDFLAG and OBJECT_VERSION_NUMBER. The view is marked VALID and is available in both Oracle EBS 12.1.1 and 12.2.2 environments.

Because FND_USER is the central repository of application user accounts in Oracle E-Business Suite, this view serves as a controlled, CRM-oriented access point to user identity information. It enables reporting and integration components in the CRM Foundation layer to resolve application users without querying the base table directly. The presence of LAST_LOGON_DATE in the column list is significant: this column supports the common requirement of identifying inactive or dormant user accounts, and it appears directly in the view definition.

Underlying Base Objects

The view is defined over a single documented base object: FND_USER, accessed through a synonym. No joins, unions, or aggregations are present in the view text. The projection maps standard FND_USER audit and identity columns directly, and appends two synthetic columns:

• F_DELETEDFLAG — exposed as NULL in the view text
• OBJECT_VERSION_NUMBER — exposed as the constant 1

These two columns follow the standard Oracle Applications Framework convention for entity views, providing a uniform row-state and optimistic-locking interface for consumers such as OAF-based CRM pages. Because the view maps one-to-one to FND_USER, query performance is effectively equivalent to querying the base table, subject to the usual predicate pushdown behaviour.

Key Columns

• USER_ID — primary identifier for the application user; joins to FND_USER and related tables.
• USER_NAME — the login name assigned to the user account.
• LAST_LOGON_DATE — timestamp of the user's most recent successful sign-on; the column most commonly queried for activity and dormancy analysis.
• START_DATE / END_DATE — effective date range of the account, used for validity checks.
• PASSWORD_DATE, PASSWORD_ACCESSES_LEFT, PASSWORD_LIFESPAN_ACCESSES, PASSWORD_LIFESPAN_DAYS — password policy attributes reflecting expiry and attempt limits.
• ENCRYPTED_FOUNDATION_PASSWORD, ENCRYPTED_USER_PASSWORD, WEB_PASSWORD — encrypted credential columns; these should never be selected in reporting queries.
• EMPLOYEE_ID, CUSTOMER_ID, SUPPLIER_ID — foreign references linking the user to HR, customer, or supplier entities.
• EMAIL_ADDRESS, FAX — contact attributes.
• F_DELETEDFLAG, OBJECT_VERSION_NUMBER — framework-managed row-state and versioning columns.

Common Use Cases and Queries

The view is typically used for user activity reporting, CRM integration lookups, and data migration validation. A representative query returns users who have not logged on within a given window:

SELECT user_id, user_name, last_logon_date, email_address
FROM apps.jtf_fm_fnd_user_v
WHERE last_logon_date < SYSDATE - 90
  AND end_date IS NULL
ORDER BY last_logon_date;

A second common pattern resolves the responsible employee or customer associated with a CRM user:

SELECT user_name, employee_id, customer_id, start_date, end_date
FROM apps.jtf_fm_fnd_user_v
WHERE user_name = :p_user_name;

Report developers should restrict selected columns to identity and activity fields, avoid the encrypted password columns, and always include the APPS schema prefix or rely on the appropriate synonym. Because the view presents no filtering of its own, all business predicates — active accounts, date ranges, or activity thresholds — must be applied by the calling query.