Search Results assignee_name

Overview

The APPS.ENG_CHANGE_ROUTE_PEOPLE_V view is a reporting and integration construct within the Oracle E-Business Suite Engineering (ENG) module. It presents the list of people, roles, and parties who have been assigned to steps of an Engineering Change Order (ECO) routing workflow, together with each assignee's display name, assignee type, and any recorded response to the routing notification. The view exists in both 12.1.1 and 12.2.2 and is loaded as a VALID object in the APPS schema. Its principal purpose is to resolve the raw identifiers stored on the routing tables into human-readable names — in particular the ASSIGNEE_NAME column, which is the column most frequently searched by report authors and integrators. Because a routing assignee can be either a role (an application menu) or an individual party (a person or organization in the Trading Community Architecture), the view is implemented as a UNION ALL of two branches, each resolving ASSIGNEE_NAME from a different source. This design allows a single query to return a consistent assignee list irrespective of how the routing step was configured, which makes the view suitable for ECO status dashboards, workflow notification tracking, and downstream integration extracts.

Underlying Base Objects

According to the documented ETRM metadata for 12.2.2, the view is defined over the following referenced base objects: ENG_CHANGE_ROUTE_PEOPLE_VL (VIEW), FND_GLOBAL (PACKAGE), FND_LOOKUPS (VIEW), FND_MENUS_TL (SYNONYM), HZ_PARTIES (SYNONYM), and HZ_RELATIONSHIPS (SYNONYM).

• ENG_CHANGE_ROUTE_PEOPLE_VL — the primary driving entity, supplying the routing people records (ROW_ID, ROUTE_PEOPLE_ID, STEP_ID, ASSIGNEE_ID, ASSIGNEE_TYPE_CODE, response attributes, and WHO/audit columns). The _VL suffix indicates it is the translatable variant of the routing people table.
• FND_GLOBAL — invoked via USERENV('LANG') semantics to constrain the menu translation join to the session language.
• FND_LOOKUPS — joined twice: once against lookup type ENG_ROUTE_ASSIGNEE_TYPES to derive ASSIGNEE_TYPE, and once (outer-joined) against lookup type ENG_CHANGE_ROUTE_STATUSES to derive the RESPONSE meaning.
• FND_MENUS_TL — supplies USER_MENU_NAME as ASSIGNEE_NAME for rows where ASSIGNEE_TYPE_CODE = 'ROLE'.
• HZ_PARTIES and HZ_RELATIONSHIPS — resolve PARTY_NAME as ASSIGNEE_NAME, and the related company PARTY_NAME as ASSIGNEE_COMPANY_NAME, for non-role assignees.

Key Columns

• ROW_ID / ROUTE_PEOPLE_ID / STEP_ID — identifiers linking the assignee record to its routing step and parent change object.
• ASSIGNEE_ID — the raw identifier of the assignee; a menu ID when the type is ROLE, otherwise a party identifier.
• ASSIGNEE_NAME — the resolved display name. Derived from FND_MENUS_TL.USER_MENU_NAME for roles and from HZ_PARTIES.PARTY_NAME for parties.
• ASSIGNEE_TYPE_CODE / ASSIGNEE_TYPE — the coded value and its FND_LOOKUPS meaning from ENG_ROUTE_ASSIGNEE_TYPES.
• ASSIGNEE_COMPANY_NAME — the organization associated with a party assignee; populated only in the party branch.
• ADHOC_PEOPLE_FLAG — indicates an assignee added outside the predefined routing.
• WF_NOTIFICATION_ID — the Workflow notification raised to the assignee.
• RESPONSE_CODE / RESPONSE / RESPONSE_DATE / RESPONSE_DESCRIPTION — the coded response, its lookup meaning (ENG_CHANGE_ROUTE_STATUSES), timestamp, and free-text comment.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID — standard audit and concurrent-program columns.

Common Use Cases and Queries

The most frequent use is enumerating assignees for a change routing step, or reporting outstanding and completed responses. The following query lists assignee names and responses for a given step:

• SELECT step_id, assignee_name, assignee_type, response, response_date FROM apps.eng_change_route_people_v WHERE step_id = :p_step_id ORDER BY assignee_name;
• SELECT assignee_name, assignee_company_name, wf_notification_id FROM apps.eng_change_route_people_v WHERE assignee_type_code <> 'ROLE' AND response_code IS NULL; — locates party assignees who have not yet responded.
• SELECT assignee_name, COUNT(*) FROM apps.eng_change_route_people_v GROUP BY assignee_name ORDER BY 2 DESC; — workload analysis by assignee.

Because ASSIGNEE_NAME is name-resolved, the view is well suited to BI Publisher reports, OAF/ADF pages, and interface extracts that must display routing participants without joining FND_MENUS_TL or HZ_PARTIES directly.