Search Results cancelation_date

Overview

ENG_CHANGE_LINES_VL is a valid, reporting-oriented view owned by the APPS schema within the Oracle E-Business Suite Engineering (ENG) product. It presents the change line records that constitute an Engineering Change Order (ECO), combining the transactional change line data with its translatable descriptive attributes. In the context of Oracle EBS 12.1.1 and 12.2.2, this view serves as the principal read-only interface for querying engineering change line information without directly joining the underlying transactional and translation tables. Because it exposes the APPROVAL_REQUEST_DATE and related approval columns, it is commonly targeted by users and integration developers seeking approval-cycle information for engineering change lines. The "_VL" suffix denotes a view that resolves the language-specific columns through the user's session language, so callers receive names and descriptions in their own language.

Underlying Base Objects

The documented view metadata identifies two referenced base objects, both exposed to APPS as synonyms: ENG_CHANGE_LINES and ENG_CHANGE_LINES_TL. The view is defined as an inner join between these two objects, keyed on CHANGE_LINE_ID, with the additional predicate restricting the translation row to the user's session language via USERENV('LANG'). ENG_CHANGE_LINES supplies the transactional columns — identifiers, audit fields, dates, status codes, approval attributes, routing, and sequencing. ENG_CHANGE_LINES_TL supplies the translatable NAME and DESCRIPTION columns. Only change lines that have a translation row in the current session language are returned, which is the standard behavior of "_VL" views in EBS. The ROW_ID column is derived from the ECL.ROWID, providing a pseudo-column for the underlying base row.

Key Columns

• CHANGE_LINE_ID — Primary identifier of the change line; the join key to both base objects.
• CHANGE_ID — Foreign key to the parent Engineering Change Order header.
• APPROVAL_REQUEST_DATE — The date the change line approval was requested; central to approval-cycle reporting and the column most relevant to approval_request_date queries.
• APPROVAL_DATE and APPROVAL_STATUS_TYPE — The date and status type of the approval action for the line.
• STATUS_CODE — The current lifecycle status of the change line.
• ASSIGNEE_ID — The individual assigned to the change line.
• NEED_BY_DATE, SCHEDULED_DATE, IMPLEMENTATION_DATE, CANCELATION_DATE — Milestone dates describing the change line schedule and disposition.
• NAME and DESCRIPTION — Language-resolved translatable text from ENG_CHANGE_LINES_TL.
• ROUTE_ID, REQUIRED_FLAG, COMPLETE_BEFORE_STATUS_CODE, START_AFTER_STATUS_CODE — Routing and sequencing controls governing when the line may be completed or started.
• Audit and concurrency columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include ECO status dashboards, approval-latency reporting based on APPROVAL_REQUEST_DATE, and integration extraction of change line detail for downstream systems. A representative query lists approval activity for open change lines:

SELECT change_line_id, change_id, name, status_code,
       approval_status_type, approval_request_date, approval_date
FROM   apps.eng_change_lines_vl
WHERE  approval_request_date >= :from_date
ORDER BY approval_request_date DESC;

A second common pattern joins the view to the ECO header to report pending approvals in the user's language, or filters by STATUS_CODE and ASSIGNEE_ID to build workload reports. Because the view already resolves translations, it is preferred over manual joins to ENG_CHANGE_LINES_TL.

Oracle Proprietary, Confidential Information — Legal Notices.