Search Results web_password

Overview

ICX_PO_USER_DETAILS_V is a seeded Oracle E-Business Suite database view owned by the APPS schema. It belongs to the ICX product family — Oracle iProcurement — and is documented with the description User Details View. The view presents a simplified, procurement-oriented projection of user account information drawn from the Oracle Applications user repository. It is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2, confirming it remains a supported and queryable object across both release streams.

Functionally, the view acts as an abstraction layer over the core user table. Rather than forcing iProcurement code, reports, and integrations to query FND_USER directly, the view exposes a stable column list tailored to purchasing and self-service user-detail requirements. This decoupling is significant for reporting and integration developers: it advertises a documented interface in the ETRM repository and shields consumers from the majority of the roughly fifty columns carried by the underlying base table.

Because the view is a single-table projection with no joins, aggregation, or filtering predicates, rows returned correspond one-for-one with rows in the base table. There are no DISTINCT clauses, hints, or view-level security predicates in the documented view text, so any row-level access control continues to be governed by the base table and by Oracle Applications row-level security applied around it.

Underlying Base Objects

The documented base object is FND_USER, referenced in the view definition as a synonym. FND_USER is the central Oracle EBS repository for application user accounts, storing credentials, effective-dating information, password policy attributes, and linkage to HR employees. The view definition reads, in order:

• USER_ID, USER_NAME
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN
• ENCRYPTED_FOUNDATION_PASSWORD, ENCRYPTED_USER_PASSWORD (documented as USER_PASSWORD in the metadata column list)
• SESSION_NUMBER, START_DATE, END_DATE, DESCRIPTION
• LAST_LOGON_DATE, PASSWORD_DATE
• PASSWORD_ACCESSES_LEFT, PASSWORD_LIFESPAN_ACCESSES, PASSWORD_LIFESPAN_DAYS
• EMPLOYEE_ID, EMAIL_ADDRESS, FAX, WEB_PASSWORD

The absence of joins means the view inherits FND_USER indexing directly; queries filtering on USER_NAME or USER_ID benefit from the base table's unique indexes.

Key Columns

The column most frequently searched — and the one that prompted this reference — is LAST_LOGON_DATE. It records the date and time of the user's most recent successful sign-on to Oracle EBS. It is widely used for dormant-account analysis, license reconciliation, and security auditing. Operational caveats apply: the value can be null for users who have never logged in, and it is refreshed at authentication time, so it should not be treated as a substitute for audit-trail tables such as FND_LOGINS or FND_UNSUCCESSFUL_LOGINS.

Other significant columns include USER_NAME (the login identifier), START_DATE and END_DATE (account effective-dating; a user is active only when the current date falls within this range), EMPLOYEE_ID (foreign key to the HR person record for the standard Oracle EBS user-to-employee link), EMAIL_ADDRESS, PASSWORD_DATE, password-policy counters (PASSWORD_ACCESSES_LEFT, PASSWORD_LIFESPAN_ACCESSES, PASSWORD_LIFESPAN_DAYS), and DESCRIPTION. The who-columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) provide standard Oracle EBS auditability.

Common Use Cases and Queries

Typical uses are dormant-user reporting, preparer/approver lookups in iProcurement requisition tooling, email harvesting for notifications, and reconciliation between EBS accounts and HR assignments.

Retrieve users who have never signed on or who have been inactive for an extended period:

SELECT user_id, user_name, last_logon_date
FROM apps.icx_po_user_details_v
WHERE last_logon_date IS NULL
OR last_logon_date < SYSDATE - 90;

Join to HR to identify active users linked to current employees:

SELECT u.user_name, u.email_address, u.last_logon_date
FROM apps.icx_po_user_details_v u,
apps.per_all_people_f p
WHERE u.employee_id = p.person_id
AND SYSDATE BETWEEN p.effective_start_date AND p.effective_end_date
AND u.start_date <= SYSDATE
AND NVL(u.end_date, SYSDATE + 1) > SYSDATE;

Always grant the querying responsibility read access via a custom GRANT on the view rather than direct FND_USER privileges, and avoid selecting the password columns for reporting purposes. Oracle proprietary and confidential information — see Legal Notices.