Search Results eng_list




Overview
Explore in AI Chat

Overview

The WF_ENG_LIST_UR view is a directory-services synchronization view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is delivered under the FND — Application Object Library product and carries a VALID status in the ETRM repository. Its formal description identifies it as the "Bulk Sync Directory Service User Role View for Role Orig System ENG_LIST." In practical terms, the view materializes the relationship between Oracle EBS application users and the Engineering Change Order (ECO) approval lists to which they belong, expressing that relationship in the normalized user-role format required by Oracle Internet Directory (OID) and similar LDAP-based directory products.

The view is not intended for ad hoc transactional access. It is consumed by the bulk synchronization programs that push user-to-role membership assignments from EBS into the directory tier, ensuring that workflow notifications, approval routing, and identity-based access for engineering change management remain consistent between the two environments. The name suffix "UR" denotes "User Role," distinguishing it from the parallel role and user views in the WF_ENG_LIST family. Users who search for "eng_ecn_approvers" typically arrive at this view because it is the principal bridge between the ENG_ECN_APPROVERS table and the FND identity model.

Underlying Base Objects

The view is defined over four base objects, all referenced through public synonyms: ENG_ECN_APPROVAL_LISTS, ENG_ECN_APPROVERS, FND_USER, and PER_ALL_PEOPLE_F. The join path is deliberate and restrictive. ENG_ECN_APPROVERS supplies the employee-to-approval-list assignment via EMPLOYEE_ID and APPROVAL_LIST_ID. PER_ALL_PEOPLE_F resolves that employee identifier to a PERSON_ID and restricts the result to currently effective person records using TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE. FND_USER links PER.PERSON_ID to USR.EMPLOYEE_ID, filtering on active accounts with TRUNC(SYSDATE) BETWEEN START_DATE AND NVL(END_DATE, SYSDATE+1). ENG_ECN_APPROVAL_LISTS contributes the APPROVAL_LIST_ID used to construct the role name. Approvers with a DISABLE_DATE earlier than the current date are excluded.

Key Columns

  • USER_NAME — the FND_USER login name of the approver, forming the user side of the role assignment.
  • USER_ORIG_SYSTEM / USER_ORIG_SYSTEM_ID — the originating system for the user, hard-coded to 'PER' and PER.PERSON_ID respectively, matching the HR person orig system convention.
  • ROLE_NAME — a concatenated identifier built as 'ENG_LIST'||':'||EEAL.APPROVAL_LIST_ID, uniquely naming each approval list as a directory role.
  • ROLE_ORIG_SYSTEM / ROLE_ORIG_SYSTEM_ID — the role origin, fixed at 'ENG_LIST' with the numeric APPROVAL_LIST_ID as its identifier.
  • START_DATE / EXPIRATION_DATE — both returned as TO_DATE(NULL), leaving effective dating to be managed by the synchronization process rather than the view.
  • SECURITY_GROUP_ID — returned as NULL; the column exists to satisfy the standard WF directory view signature.
  • PARTITION_ID — a constant 7, indicating the partition assignment used by the bulk synchronization logic.

Common Use Cases and Queries

Typical uses include verifying which users are currently included in ECO approval list synchronization, troubleshooting approvers who are missing from OID role membership, and reconciling ENG_ECN_APPROVERS assignments against FND_USER accounts. Because the view itself is not date-stamped on output, it always reflects the "as of today" population.

To list all current user-role pairs:

  • SELECT user_name, role_name FROM apps.wf_eng_list_ur ORDER BY role_name, user_name;

To find all approvers assigned to one approval list:

  • SELECT user_name, user_orig_system_id FROM apps.wf_eng_list_ur WHERE role_orig_system_id = :approval_list_id;

To confirm a specific user's ECO approval list memberships:

  • SELECT role_name FROM apps.wf_eng_list_ur WHERE user_name = :user_name;

Users investigating "eng_ecn_approvers" should note that the view filters on both person and user effective dates, so an approver whose FND_USER end date has passed, or whose PER_ALL_PEOPLE_F record is not currently effective, will not appear even though the ENG_ECN_APPROVERS row still exists.