Search Results eng_changes_v

Overview

ENG_CHANGES_V is a reporting view owned by the APPS schema within the Engineering (ENG) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It presents a denormalized, business-friendly projection of engineering change orders (ECOs) and related change management records. Rather than exposing the raw transactional table ENG_ENGINEERING_CHANGES, the view joins that table to status, type, classification, party, project, and lookup reference objects so that consumers obtain decoded, human-readable attributes alongside the operational columns.

Its principal role is to support reporting, operational dashboards, and integration extracts. Because it exposes descriptive fields such as ECO_STATUS, CHANGE_ORDER_TYPE, APPROVAL_STATUS, PROJECT_NAME, and TASK_NAME, it removes the burden of resolving foreign keys and lookup codes at query time. The view also computes several derived measures — DAYS_TO_APPROVE, REPORTED_DAYS_SINCE, DAYS_SINCE_UPDATED, and DAYS_UNTIL_DUE — making it convenient for aging and cycle-time analysis of change orders.

Underlying Base Objects

The view is defined over the following documented base objects: ENG_ENGINEERING_CHANGES (synonym to the core change table), ENG_CHANGE_CLASSIFICATIONS_VL, ENG_CHANGE_ORDER_TYPES_VL, ENG_CHANGE_STATUSES_VL, FND_LOOKUP_VALUES, MFG_LOOKUPS, HZ_PARTIES, PA_PROJECTS_ALL, PA_PROJ_ELEMENTS, PER_ORGANIZATION_STRUCTURES, and the FND_PROFILE package. The primary driving table is ENG_ENGINEERING_CHANGES; the classification, order type, and status views supply descriptive names via their _VL (translated) definitions. HZ_PARTIES resolves both assignee and requestor party names. PA_PROJECTS_ALL and PA_PROJ_ELEMENTS contribute project and task identifiers.

Key Columns

• CHANGE_ID, CHANGE_NOTICE, CHANGE_NAME — primary identity of the engineering change order.
• INITIATION_DATE, IMPLEMENTATION_DATE, CANCELLATION_DATE — chronological milestones in the change lifecycle; INITIATION_DATE drives the REPORTED_DAYS_SINCE calculation.
• STATUS_TYPE / STATUS_CODE / ECO_STATUS — raw and decoded status of the change order.
• APPROVAL_STATUS, APPROVAL_DATE, APPROVAL_REQUEST_DATE, DAYS_TO_APPROVE — approval timing and the elapsed interval derived from the two date columns.
• NEED_BY_DATE, DAYS_UNTIL_DUE — due-date tracking relative to the current system date.
• PRIORITY_CODE, REASON_CODE, CHANGE_MGMT_TYPE_CODE, RESOLUTION — classification attributes used in analysis.
• PROJECT_NAME, PROJECT_NUMBER, TASK_NAME, TASK_NUMBER — project and task associations resolved from PA tables.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–15 — the standard EBS descriptive flexfield columns.

Common Use Cases and Queries

Typical uses include open-ECO listings, aging reports, approval cycle-time analysis, and extracts feeding downstream change management systems. The following query lists recent change orders by initiation date:

SELECT change_notice,
       change_name,
       eco_status,
       initiation_date,
       reported_days_since,
       need_by_date,
       days_until_due
FROM   apps.eng_changes_v
WHERE  initiation_date >= TRUNC(SYSDATE) - 90
ORDER  BY initiation_date DESC;

A second scenario measures approval efficiency:

SELECT change_notice,
       approval_status,
       approval_request_date,
       approval_date,
       days_to_approve
FROM   apps.eng_changes_v
WHERE  days_to_approve IS NOT NULL
ORDER  BY days_to_approve DESC;

Because the view exposes project, task, and party identifiers, it is equally applicable to cross-module reporting where engineering changes must be correlated with project costing or organizational data.