Search Results wf_local_users_pk

Overview

WF_LOCAL_USERS is a core Oracle Workflow directory table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified under the FND – Application Object Library product and is documented in ETRM as a VALID table with the description "Local Users table." The object stores the local, Workflow-visible representation of users and roles that participate in notification routing, approval processes, and the Workflow directory service. Rather than acting as the system of record for human resources or application user accounts, it serves as a flattened, locally cached view synthesized from multiple underlying sources, including FND_USER and the Oracle Workflow directory repository, so that the Notification System can resolve recipients such as users, roles, and groups uniformly.

From a Data Vault modeling perspective, the metadata heuristically classifies WF_LOCAL_USERS as standalone. That classification suggests it is best modeled as a hub-like entity keyed on the natural business key NAME, with surrounding descriptive attributes treated as satellite data. The table is not a transactional fact table; it is a reference or directory dimension.

Key Information Stored

The table contains 13 documented columns. Its primary key is WF_LOCAL_USERS_PK, defined on NAME, which functions as the surrogate or principal identifier for each directory entry. A second unique index, WF_LOCAL_USERS_U1, covers the composite business key (NAME, ORIG_SYSTEM, ORIG_SYSTEM_ID), indicating that the same NAME may legitimately appear across multiple originating systems and must be qualified by origin.

• NAME — the primary key and the Workflow directory name used for recipient resolution.
• DISPLAY_NAME — the human-readable name shown in notifications and directory lookups.
• DESCRIPTION — free-text description of the user or role entry.
• NOTIFICATION_PREFERENCE — the delivery preference (for example, MAILHTML or MAILTEXT) governing how notifications reach the recipient.
• LANGUAGE and TERRITORY — localization attributes controlling notification language and regional formatting.
• EMAIL_ADDRESS and FAX — electronic delivery destinations used by the Notification Mailer.
• STATUS — the active or inactive state of the directory entry, which determines whether the recipient can be resolved.
• START_DATE and EXPIRATION_DATE — effective dating that bounds when the entry is valid for notification routing.
• ORIG_SYSTEM and ORIG_SYSTEM_ID — identify the source system and its identifier, with ORIG_SYSTEM_ID carrying a foreign key to HZ_ORIG_SYSTEMS_B.

Common Use Cases and Queries

WF_LOCAL_USERS is queried most often when diagnosing notification delivery failures, validating recipient resolution, or reporting on Workflow participants. Typical scenarios include confirming that a user has an active, non-expired entry with a valid email address before an approval notification is dispatched.

To retrieve active recipients with email addresses:

• SELECT name, display_name, email_address, notification_preference FROM wf_local_users WHERE status = 'ACTIVE' AND (expiration_date IS NULL OR expiration_date > SYSDATE);

To reconcile entries back to their originating system:

• SELECT l.name, l.orig_system, l.orig_system_id FROM wf_local_users l WHERE l.orig_system = 'FND_USER';

The table also supports joins to WF_LOCAL_ROLES and WF_LOCAL_USER_ROLES to build a complete directory picture of users, roles, and their memberships for security and approval-path reporting.

Related Objects

The most significant related objects are those that share the Workflow local directory model or supply the origin reference:

• HZ_ORIG_SYSTEMS_B — referenced through the foreign key WF_LOCAL_USERS.ORIG_SYSTEM_ID, providing the registered origin system definitions (for example, FND_USER, PER, or HZ_PARTY).
• WF_LOCAL_ROLES — the parallel directory table for roles and groups; joined on NAME to resolve role-based recipients.
• WF_LOCAL_USER_ROLES — the association table linking users to roles; joined on NAME to traverse role membership.
• WF_ROLES and WF_USER_ROLES — the underlying Workflow role definitions from which the local directory is derived.
• FND_USER — the application user repository that is a primary source for synchronizing local user entries.
• WF_NOTIFICATIONS and WF_NOTIFICATION_ATTRIBUTES — the transactional notification tables whose RECIPIENT_ROLE and recipient attributes resolve against WF_LOCAL_USERS.NAME.
• WF_DIRECTORY — the public Workflow directory API view that queries the local users and roles tables.

Two related APIs, WF_DIRECTORY.GetUser and WF_DIRECTORY.GetRoleName, are commonly used at runtime to resolve recipient names into display names using this table.