Search Results timeout_option

Overview

ENG_CHANGE_ROUTE_STEPS_VL is an APPS-owned, VALID Oracle EBS view in the Engineering (ENG) product family, exposed as a translated (TL) "VL" view. In Oracle EBS 12.1.1 and 12.2.2, the "_VL" suffix denotes a view that joins a base (non-translated) table to its translation table and filters on the session language, thereby presenting user-facing descriptive text in the login's language. This view surfaces the individual steps that make up a change order route, together with workflow orchestration attributes, scheduling attributes, descriptive text, and the standard WHO audit and concurrent program context columns.

The "route" concept in ENG represents the approval and processing path a change order follows. Each row in this view corresponds to a single route step, sequenced by STEP_SEQ_NUM, and carries workflow item type, item key, and process name so that Oracle Workflow can drive the step's execution. Because the view is queryable directly from the APPS schema, it is a natural source for custom reports, BI Publisher data templates, Oracle Discoverer workbooks, and interface extracts. For the user searching on "required_date," the view exposes REQUIRED_DATE directly, which makes it the authoritative object for reporting target completion dates against change route steps.

Underlying Base Objects

The view is defined over two documented base objects, both presented in the ETRM metadata as synonyms: ENG_CHANGE_ROUTE_STEPS (aliased ECRS) and ENG_CHANGE_ROUTE_STEPS_TL (aliased ECRSTL). The join is on STEP_ID (ECRS.STEP_ID = ECRSTL.STEP_ID), and the translation table is additionally constrained by ECRSTL.LANGUAGE = USERENV('LANG'), returning only the description row for the current session language.

All columns other than INSTRUCTION originate from ENG_CHANGE_ROUTE_STEPS; INSTRUCTION is the only attribute sourced from the translation table. This explains the "VL" nature of the view: the descriptive, translatable text is separated from the structural and workflow data, and the view reunites them for consumption. The presence of LANGUAGE filtering means the view must be queried in a session whose NLS language setting matches an available translation row.

Key Columns

The columns most relevant to change management reporting and the user's "required_date" search include:

• REQUIRED_DATE — The absolute target date by which the route step should be completed. This is the column the user searched for and is the primary scheduling anchor for step-level reporting.
• REQUIRED_RELATIVE_DAYS — The offset in days from a reference point used to derive or compare against REQUIRED_DATE; together these two columns describe both relative and absolute scheduling intent.
• STEP_START_DATE / STEP_END_DATE — Actual execution window for the step, useful for cycle-time and slip analysis against the required date.
• STEP_STATUS_CODE and TIMEOUT_OPTION — Indicate where the step is in its lifecycle and what happens when it breaches its required date.
• STEP_ID, ROUTE_ID, STEP_SEQ_NUM — The structural keys linking the step to its route and ordering it within the sequence.
• INSTRUCTION — The translated instruction text for the step, from ENG_CHANGE_ROUTE_STEPS_TL.
• WF_ITEM_TYPE, WF_ITEM_KEY, WF_PROCESS_NAME — Workflow routing identifiers that tie the step to its background process.
• ADHOC_STEP_FLAG, CONDITION_TYPE_CODE, ASSIGNMENT_CODE — Control flags describing how the step is assigned and whether it is conditional or ad hoc.
• ATTRIBUTE1–15, ATTRIBUTE_CATEGORY — The standard DFF (descriptive flexfield) columns for extension data.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — WHO audit columns.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — Concurrent program context columns; ORIGINAL_SYSTEM_REFERENCE supports cross-system traceability.

Common Use Cases and Queries

The most frequent reason to query this view is to report scheduled and overdue route steps, which is precisely the scenario the "required_date" search implies. A typical query lists steps whose required date has passed while the step is still open:

• Overdue route steps: SELECT step_id, route_id, step_seq_num, step_status_code, required_date FROM apps.eng_change_route_steps_vl WHERE required_date < SYSDATE AND step_status_code NOT IN ('COMPLETE','CANCELLED') ORDER BY required_date;
• Step detail for a specific route: filter on ROUTE_ID and order by STEP_SEQ_NUM to produce an ordered itinerary of the change route.
• Workflow failure diagnosis: select STEP_ID, STEP_SEQ_NUM, WF_PROCESS_NAME, WF_ITEM_KEY where STEP_STATUS_CODE indicates an error, then reconcile with Workflow status.
• Step-level instruction reporting: join on STEP_ID and select INSTRUCTION (automatically language-filtered) for printed or emailed change packages.
• Cycle-time analysis: compute STEP_END_DATE minus STEP_START_DATE and compare to REQUIRED_DATE to measure on-time performance.

Because the view filters on USERENV('LANG'), reports run in a different language than the stored translation may return no descriptive text; querying the underlying base table directly avoids that restriction when translation is not required. All access should be granted through the APPS schema with the appropriate Engineering responsibility, and care should be taken not to modify the view's underlying tables directly, as route steps are maintained by Engineering and Workflow processes.