Results for “mes_group”

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

Overview

APPS.WF_AMV_APPR_UR is a database view in the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 environment. The name follows the standard Oracle Workflow (WF_) naming convention, and the AMV_APPR suffix identifies it as part of the Approvals Management (AMV / AME) framework. Its specific function is to resolve which FND_USER accounts correspond to approvers for the "MES_APPROVE" role, which belongs to the Oracle Field Service / TeleService resource role model (Role Type Code "MES").

Rather than storing approvals data, the view is a resolution mechanism. It joins the JTF Resource Manager schema (roles, role relations, groups, group memberships, and resource extensions) with human resources (PER_ALL_PEOPLE_F) and application users (FND_USER) to produce a list of user names and person identifiers that the Approval Management Engine can treat as valid approvers. In EBS reporting and integration, this view is therefore consulted when Workflow or AME needs to determine the set of users eligible to approve transactions routed through the MES_APPROVE role.

Underlying Base Objects

The view is defined over eight documented base objects, all accessed through APPS synonyms:

• JTF_RS_ROLES_B — the base role definition; filtered on ROLE_TYPE_CODE = 'MES' and ROLE_CODE = 'MES_APPROVE'.
• JTF_RS_ROLE_RELATIONS — links a role to either an individual resource (RS_INDIVIDUAL) or a group (RS_GROUP).
• JTF_RS_RESOURCE_EXTNS — the resource extension table carrying the CATEGORY ('EMPLOYEE') and SOURCE_ID (person identifier).
• JTF_RS_GROUPS_B, JTF_RS_GROUP_USAGES, JTF_RS_GROUP_MEMBERS — used in the group branch to expand group-based role assignments into individual resources.
• PER_ALL_PEOPLE_F — the HR person record; date-effective filtering is applied against SYSDATE.
• FND_USER — the application user account; joined on EMPLOYEE_ID = PERSON_ID.

The view is the UNION of two branches: the first resolves direct individual role assignments, and the second resolves group-based assignments. Both branches converge on the same join path from JTF_RS_RESOURCE_EXTNS to PER_ALL_PEOPLE_F to FND_USER, ensuring a single, deduplicated style of output row.

Key Columns

The view exposes ten positional columns, several of which are literal constants rather than derived data:

• USER_NAME — the FND_USER login name of the resolved approver.
• Constant 'PER' — indicates the identifier type is a person.
• PERSON_ID — the PER_ALL_PEOPLE_F primary key for the approver.
• Constants 'AMV_APPR' and 'AMV_APPR' — approval-role and approval-type markers.
• Constant 520 — a numeric role/usage identifier used by the AME engine.
• Two TO_DATE(NULL) columns — effective date placeholders, left null.
• NULL — a further placeholder column.
• Constant 5 — a sequence or order indicator.

Common Use Cases and Queries

Typical usage is diagnostic or integration-based: validating that the expected users are recognized as MES_APPROVE approvers, or feeding user lists into AME setup.

List all resolved approver user names and person IDs:

• SELECT user_name, person_id FROM apps.wf_amv_appr_ur;

Check whether a specific user is recognized as an approver:

• SELECT user_name, person_id FROM apps.wf_amv_appr_ur WHERE user_name = :p_user;

Reconcile the view against active users:

• SELECT u.user_name FROM apps.fnd_user u WHERE u.user_name IN (SELECT user_name FROM apps.wf_amv_appr_ur);

Because the view relies on date-effective checks (SYSDATE between EFFECTIVE_START_DATE and EFFECTIVE_END_DATE), results reflect only currently active employees, and both the individual and group branches must be considered when auditing approver populations.