Search Results wf_local_users_u1

Overview

APPLSYS.WF_LOCAL_USERS is the Oracle Workflow directory table that stores the local definition of every workflow-enabled user, role, and resource known to the E-Business Suite. It functions as the resolution layer between the Oracle Workflow engine and the underlying HR or application user populations: when a notification, function activity, or routing rule references a user by name, the Workflow directory services resolve that name against this table to obtain display information, delivery attributes, and availability status before a message is sent.

The table resides in the APPLSYS schema, is registered as FND design data (FND.WF_LOCAL_USERS), and is stored in the APPS_TS_ARCHIVE tablespace with a PCTFREE of 10. Its status is VALID across the 12.1.1 and 12.2.2 releases, and the documented physical schema records thirteen columns. Under a heuristic Data Vault classification derived from its foreign-key structure, the table is modelled as a standalone construct — it does not behave as a pure hub, link, or satellite because its relationships are positional rather than strictly relational. A single inbound association is documented: ORIG_SYSTEM_ID references HZ_ORIG_SYSTEMS_B, tying the workflow directory entry back to the Trading Community Architecture origin system registry.

Key Information Stored

The primary key is WF_LOCAL_USERS_PK, defined on the NAME column, which holds the internal workflow name used by the engine for address resolution. A separate unique index, WF_LOCAL_USERS_U1, spans NAME, ORIG_SYSTEM, and ORIG_SYSTEM_ID, making this composite the principal business-key candidate and the object most commonly referenced in searches for the unique index. Two nonunique indexes support access paths: WF_LOCAL_USERS_N1 on ORIG_SYSTEM and ORIG_SYSTEM_ID, and WF_LOCAL_USERS_N2 on DISPLAY_NAME.

• NAME (VARCHAR2 320) — internal workflow name; also the primary key column.
• DISPLAY_NAME (VARCHAR2 360) — the human-readable name presented to notification recipients.
• DESCRIPTION (VARCHAR2 1000) — free-text description of the directory entry.
• NOTIFICATION_PREFERENCE (VARCHAR2 240) — preferred delivery channel (for example MAILHTML, MAILTEXT, or disabled).
• EMAIL_ADDRESS (VARCHAR2 2000) — destination address used by the mailer component.
• FAX (VARCHAR2 240) — fax number retained for fax-based notification delivery.
• STATUS (VARCHAR2 30) — indicates whether the user is available to participate in a workflow process.
• EXPIRATION_DATE (DATE) — date on which the workflow user entry expires.
• LANGUAGE and TERRITORY (VARCHAR2 240 each) — locale attributes controlling message rendering.
• ORIG_SYSTEM (VARCHAR2 30) and ORIG_SYSTEM_ID (NUMBER) — the source system identifier and its key, which together with NAME form the unique business key.
• START_DATE (DATE) — effective start of the entry's validity.

Note that the table carries no explicit mandatory (NOT NULL) flags in the documented metadata, so integrity is enforced through the Workflow directory synchronization APIs rather than column constraints.

Common Use Cases and Queries

Typical usage centers on diagnosing notification failures, auditing directory synchronization, and reporting on user delivery preferences.

• Resolving a workflow name to its delivery attributes: select NAME, DISPLAY_NAME, EMAIL_ADDRESS, NOTIFICATION_PREFERENCE, STATUS from APPLSYS.WF_LOCAL_USERS where NAME = :name.
• Locating a user by the unique business key: filter on NAME, ORIG_SYSTEM, and ORIG_SYSTEM_ID to exercise WF_LOCAL_USERS_U1.
• Identifying inactive or soon-to-expire participants: filter on STATUS and EXPIRATION_DATE.
• Auditing entries by source system: group by ORIG_SYSTEM and count, using WF_LOCAL_USERS_N1.
• Searching by display name for end-user-facing lookups, leveraging WF_LOCAL_USERS_N2.

Because the table is a directory cache populated and refreshed from HR and TCA sources, direct DML is discouraged; corrections should be made through the originating system and synchronized back. The standard query joins the projection of NAME through DISPLAY_NAME, DESCRIPTION, NOTIFICATION_PREFERENCE, LANGUAGE, TERRITORY, EMAIL_ADDRESS, FAX, STATUS, EXPIRATION_DATE, ORIG_SYSTEM, ORIG_SYSTEM_ID, and START_DATE.

Related Objects

The documented dependency graph is deliberately narrow. APPLSYS.WF_LOCAL_USERS does not reference any database object directly, but it is referenced by APPLSYS.WF_LOCAL_USERS#, its supporting object in the APPLSYS schema. The one outbound association is ORIG_SYSTEM_ID to HZ_ORIG_SYSTEMS_B, the TCA origin-system base table. In practice the directory is consumed alongside other Workflow directory objects such as WF_USERS, WF_ROLES, WF_LOCAL_ROLES, WF_LOCAL_USER_ROLES, and WF_USER_ROLES, which share the NAME key space and are read by the Workflow Notification Mailer and directory service APIs to expand role membership and routing. Administrators typically reconcile discrepancies between this table and PER_ALL_PEOPLE_F or FND_USER when investigating delivery failures.