Search Results response_code

Overview

ENG_CHANGE_ROUTE_PEOPLE_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite, belonging to the Engineering (ENG) product module. It exposes routed personnel records associated with Engineering Change Order (ECO) routing steps and, critically, resolves the user-facing RESPONSE_DESCRIPTION text for each assignee response. Because the underlying translation table stores descriptions per language, the view restricts rows to the session language via USERENV('LANG'), allowing Oracle Forms, OAF pages, and concurrent programs to display response text in the user's own language without additional joins. The view is documented as VALID in both 12.1.1 and 12.2.2 ETRM repositories, and the user's search term response_description maps directly to the column of that name exposed here.

Underlying Base Objects

The view is defined over two base objects, referenced in the ETRM metadata as synonyms: ENG_CHANGE_ROUTE_PEOPLE (the transactional route-people table, aliased ECRP) and ENG_CHANGE_ROUTE_PEOPLE_TL (the translation table, aliased ECRPTL). The join is on ROUTE_PEOPLE_ID, constrained by ECRPTL.LANGUAGE = USERENV('LANG'). The view therefore behaves as a denormalized combination: all routing, assignment, workflow, and audit attributes come from the base table, while RESPONSE_DESCRIPTION is drawn from the TL table for the current language. A ROWID from the base table is exposed as ROW_ID for locked-row update handling through the view.

Key Columns

• ROUTE_PEOPLE_ID — primary identifier joining the transactional and translation records.
• STEP_ID — the ECO routing step to which the assignee belongs.
• ASSIGNEE_ID / ASSIGNEE_TYPE_CODE — the person, group, or role responsible for the step.
• RESPONSE_DESCRIPTION — the translated, displayable description of the assignee's response; the column of interest in the user's search.
• RESPONSE_CODE / RESPONSE_DATE — the coded response value and when it was recorded.
• RESPONSE_CONDITION_CODE — the conditional path selected by the response.
• WF_NOTIFICATION_ID — links the record to the Oracle Workflow notification used for approval routing.
• ADHOC_PEOPLE_FLAG — indicates ad hoc assignment of personnel.
• PARENT_ROUTE_PEOPLE_ID / ORIGINAL_ASSIGNEE_ID / ORIGINAL_SYSTEM_REFERENCE — support reassignment lineage and source tracking.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — standard EBS Who and concurrent-program audit columns.

Common Use Cases and Queries

Typical uses include ECO approval-status reporting, workflow response auditing, and integration extracts that need translated response text. Because RESPONSE_DESCRIPTION is language-aware, reports run under different sessions automatically surface the appropriate translation. A simple query listing responses for a given routing step:

SELECT erp.ROUTE_PEOPLE_ID,
       erp.STEP_ID,
       erp.ASSIGNEE_ID,
       erp.RESPONSE_DESCRIPTION,
       erp.RESPONSE_CODE,
       erp.RESPONSE_DATE
FROM   APPS.ENG_CHANGE_ROUTE_PEOPLE_VL erp
WHERE  erp.STEP_ID = :step_id
ORDER  BY erp.ROUTE_PEOPLE_ID;

To reconcile workflow notifications with recorded responses, select WF_NOTIFICATION_ID alongside RESPONSE_DESCRIPTION. For reassignment analysis, filter on ORIGINAL_ASSIGNEE_ID or PARENT_ROUTE_PEOPLE_ID. Because the view is not a key-preserved partition beyond ROW_ID, updates should target the base table unless the EBS form layer explicitly permits view-level DML.