Search Results cust_cont

Overview

WF_USERS_OLD is a legacy compatibility view owned by the FND – Application Object Library product in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a unified directory of workflow-enabled users by consolidating three distinct populations: EBS application users linked to an HR person record, application users with no employee linkage, and Oracle Trading Community Architecture (TCA) party contacts stored in the HZ schema. The view exists primarily to service the Oracle Workflow notification and directory engines, which require a single flattened source of user names, display names, e-mail addresses, fax numbers, preferred language, preferred territory, and mail format.

The ETRM metadata explicitly records the implementation note "Not implemented in this database," and the embedded header comment $HEADER: AFREGVW.LDT 115.3 2002/06/17 18:39:12 SSUNG NOSHIP indicates an NOSHIP designation carried forward from release 11i. In practice, WF_USERS_OLD is retained for backward compatibility with customizations and third-party integrations that referenced the pre-11.5.10 user directory model. Oracle Workflow's current directory views (WF_USERS and WF_LOCAL_USERS) supersede it, but the object is not physically dropped in many 12.1.1 and 12.2.2 environments.

Underlying Base Objects

Although the ETRM record lists no referenced base objects, the view text documents its full dependency set. The first two branches join FND_USER to FND_LANGUAGES (restricted to INSTALLED_FLAG = 'B') and, where EMPLOYEE_ID is populated, to PER_ALL_PEOPLE_F using the effective-dated predicate TRUNC(SYSDATE) BETWEEN PER.EFFECTIVE_START_DATE AND PER.EFFECTIVE_END_DATE. The third branch draws on the TCA model: HZ_PARTY_RELATIONSHIPS, HZ_PARTIES, HZ_ORG_CONTACTS, HZ_PERSON_LANGUAGE, FND_TERRITORIES, and FND_LANGUAGES. Preferences are resolved dynamically through the WF_PREF.GET_PREF function against the WF_PREF preference store.

The metadata comment referencing Bug 1391687 confirms that the HZ_PARTY branches replaced an earlier CUST_CONT query, reflecting the migration of customer contact data from the legacy Customer Contacts schema into TCA.

Key Columns

• USER_NAME – For application users, the FND_USER.USER_NAME. For TCA parties, a synthesized value of the form 'HZ_PARTY:'||TO_CHAR(PR.PARTY_ID).
• FULL_NAME / DESCRIPTION – The person's display name from PER_ALL_PEOPLE_F, the FND_USER description, or the HZ party name.
• MAILTYPE – Mail format preference, defaulting to 'MAILHTML'; TCA rows are hard-coded to 'MAILTEXT'.
• LANGUAGE / TERRITORY – Workflow preferences resolved via WF_PREF.GET_PREF, falling back to the NLS language and territory of the installed language.
• EMAIL_ADDRESS, FAX – Contact endpoints from the person or user record.
• ORIGIN ('PER', 'FND_USR', 'HZ_PARTY') and the corresponding PERSON_ID, USER_ID, or PARTY_ID – Identify which source population produced the row.
• STATUS – 'ACTIVE' or 'INACTIVE', derived from FND_USER.END_DATE or HZ_PARTIES.STATUS.

Because the third branch references HZ_PERSON_LANGUAGE, the view is a plausible hit for searches such as "hz_person_language," though its role there is limited to a language-resolution join.

Common Use Cases and Queries

WF_USERS_OLD is typically queried to reconcile Workflow directory entries against FND_USER and TCA party contacts, to audit inactive notification recipients, or to troubleshoot notification delivery failures caused by missing e-mail addresses or language preferences.

List all non-employee workflow identities:

SELECT user_name, full_name, origin, status
FROM   wf_users_old
WHERE  origin = 'FND_USR';

Identify TCA party contacts with a resolved language:

SELECT user_name, full_name, language, territory, email_address
FROM   wf_users_old
WHERE  origin = 'HZ_PARTY'
AND    email_address IS NOT NULL;

Audit inactive recipients:

SELECT user_name, full_name, origin
FROM   wf_users_old
WHERE  status = 'INACTIVE';