Results for “amv_appr”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The WF_AMV_APPR_UR view is a directory integration object owned by the APPS schema and delivered under the FND — Application Object Library product. Its documented purpose is to serve as a Bulk Sync Directory Service User Role View for Role Orig System AMV_APPR. In practical terms, the view exposes a flattened, pre-joined representation of users and the roles they hold for the AMV_APPR originating system, so that Oracle Workflow's directory synchronization services can push user-to-role assignments into an external directory (such as Oracle Internet Directory or an LDAP-based repository) in bulk rather than one record at a time.

The view is part of the family of WF_AMV_* directory synchronization views, which were originally introduced for Oracle Applications Advanced Management and remain relevant throughout 12.1.1 and 12.2.2. It is defined against Resource Manager (JTF_RS) role tables combined with Human Resources person and FND user data. Because the view is a pure SELECT construct with no DML, it is read-only and carries an APPS-owned synonym for consumer access.

Underlying Base Objects

The documented base objects referenced by WF_AMV_APPR_UR are all exposed to the view as synonyms. They comprise:

• JTF_RS_ROLES_B — the Resource Manager role definition table, filtered here for ROLE_TYPE_CODE = 'MES' and ROLE_CODE = 'MES_APPROVE'.
• JTF_RS_ROLE_RELATIONS — maps roles to resources, either as RS_INDIVIDUAL or RS_GROUP.
• JTF_RS_GROUPS_B, JTF_RS_GROUP_MEMBERS, and JTF_RS_GROUP_USAGES — used in the group branch to expand group membership into individual resources, using usage MES_GROUP.
• JTF_RS_RESOURCE_EXTNS — resource extension table filtered on CATEGORY = 'EMPLOYEE', linking resources to people.
• PER_ALL_PEOPLE_F — the HR people effective-dated view, constrained to rows active on TRUNC(SYSDATE).
• FND_USER — the application user table, joined by EMPLOYEE_ID to obtain the login name.

Two branches are UNIONed: the first resolves roles assigned directly to individual resources, and the second resolves roles assigned to groups and expands their members. Both branches return the same column list, so the union is structurally consistent.

Key Columns

• USER_NAME — the FND user login name obtained from FND_USER.USER_NAME.
• USER_ORIG_SYSTEM — a literal returned as 'PER', indicating the origin system for the user identifier.
• USER_ORIG_SYSTEM_ID — the person identifier (PER.PERSON_ID) as the origin-system key for the user.
• ROLE_NAME — the role name, returned as the literal 'AMV_APPR'.
• ROLE_ORIG_SYSTEM — the originating system for the role, also 'AMV_APPR'.
• ROLE_ORIG_SYSTEM_ID — the numeric identifier 520 associated with the AMV_APPR role for directory sync purposes.
• START_DATE and EXPIRATION_DATE — returned as TO_DATE(NULL), indicating no explicit assignment window is propagated.
• SECURITY_GROUP_ID — returned as NULL; meaningful in multi-org–enabled environments.
• PARTITION_ID — the literal partition indicator 5 used by the directory synchronization framework.

Common Use Cases and Queries

Typical use is verifying which EBS users will be synchronized into the directory as AMV_APPR approvers. A simple query lists synchronized users:

• SELECT user_name, role_name, role_orig_system, partition_id FROM wf_amv_appr_ur ORDER BY user_name;

To reconcile a specific user before a sync run:

• SELECT user_name, user_orig_system_id, role_orig_system_id FROM wf_amv_appr_ur WHERE user_name = :login;

Because the view depends on PER_ALL_PEOPLE_F for current effective dates and on FND user linkage, users whose employee record is end-dated or whose FND_USER.EMPLOYEE_ID is missing will not appear. When investigating missing directory entries, compare the expected population against this view, then trace back into JTF_RS_ROLE_RELATIONS and JTF_RS_GROUP_MEMBERS to determine whether the assignment exists at the source or was dropped by a filter in the view.