Search Results change_order

Overview

The APPS.ENG_ENGINEERING_CHANGES_V view is a denormalized reporting layer over the Engineering Change Order (ECO) tables within the Oracle E-Business Suite Engineering (ENG) module. It presents engineering change notices as a single, query-friendly row per change order, joined to descriptive lookups for status, priority, reason, approval list, change order type, and owning organization. Because it consolidates codes and their meanings into one projection, it is the standard access path for ECO-based reporting, BI Publisher extracts, OBIEE/OTBI-style feeds, and inbound/outbound integrations that must reference engineering change orders by change notice, change ID, or status. The view is owned by APPS, has a VALID status, and appears identically in the 12.1.1 and 12.2.2 code lines.

Underlying Base Objects

The view is a multi-table join. The primary driving table is ENG_ENGINEERING_CHANGES (referenced as a synonym), aliased EEC, which holds the change notice master data. It is enriched by these documented base objects:

• ENG_CHANGE_ORDER_TYPES_V and ENG_CHANGE_REASONS, ENG_CHANGE_PRIORITIES, and ENG_ECN_APPROVAL_LISTS — supply type, reason, priority, and approval-list names and descriptions.
• ENG_CHANGE_STATUSES_VL — supplies the ECO status name and status code.
• MFG_LOOKUPS — supplies the approval status meaning.
• HR_ORGANIZATION_UNITS and PER_ORGANIZATION_STRUCTURES — supply the owning/department organization name.
• PA_PROJECTS_ALL and PA_TASKS — supply project and task name/number for ECOs tied to a project.

The join also references the packages FND_PROFILE, HR_GENERAL, and HR_SECURITY. HR_SECURITY is the critical dependency: the view applies organization-level security through it, so a user sees only the inventory organizations and HR organizations for which they are authorized. HR_GENERAL and FND_PROFILE resolve user/organization context during query execution.

Key Columns

• CHANGE_NOTICE / CHANGE_ID — the user-visible ECO number and its internal primary key.
• ORGANIZATION_ID — the engineering organization that owns the change order.
• STATUS_TYPE / ECO_STATUS / STATUS_CODE — internal status type and the decoded status name from ENG_CHANGE_STATUSES_VL.
• APPROVAL_STATUS / APPROVAL_STATUS_TYPE / APPROVAL_DATE / APPROVAL_REQUEST_DATE / DAYS_TO_APPROVE — the approval lifecycle; DAYS_TO_APPROVE is computed as APPROVAL_DATE minus APPROVAL_REQUEST_DATE.
• INITIATION_DATE / IMPLEMENTATION_DATE / CANCELLATION_DATE / CANCELLATION_COMMENTS — lifecycle milestones through implementation or cancellation.
• PRIORITY_CODE, REASON_CODE, CHANGE_ORDER_TYPE plus their _DESCRIPTION columns — decoded classification values.
• ESTIMATED_ENG_COST / ESTIMATED_MFG_COST — forecast engineering and manufacturing costs.
• REQUESTOR_ID / ASSIGNEE_ID / RESPONSIBLE_ORGANIZATION_ID / ECO_DEPARTMENT — ownership and assignment.
• PROJECT_ID, PROJECT_NAME, PROJECT_NUMBER, TASK_ID, TASK_NAME, TASK_NUMBER — project accounting linkage.
• HIERARCHY_FLAG / HIERARCHY_ID — placement in a change hierarchy.
• PLM_OR_ERP_CHANGE / CHANGE_MGMT_TYPE_CODE — distinguishes PLM-originated versus ERP change management records.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — the standard DFF flex columns.
• LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID — audit and concurrency columns for incremental extracts.

Common Use Cases and Queries

Typical uses include operational ECO dashboards, aging/approval-cycle analysis, and integration extracts. A status summary query:

• SELECT ECO_STATUS, COUNT(*) FROM APPS.ENG_ENGINEERING_CHANGES_V GROUP BY ECO_STATUS;
• Find open approvals: SELECT CHANGE_NOTICE, ECO_STATUS, APPROVAL_STATUS, APPROVAL_REQUEST_DATE, DAYS_TO_APPROVE FROM APPS.ENG_ENGINEERING_CHANGES_V WHERE APPROVAL_STATUS IS NULL OR DAYS_TO_APPROVE IS NULL;
• Recent changes for a project: SELECT CHANGE_NOTICE, PROJECT_NUMBER, TASK_NUMBER, IMPLEMENTATION_DATE FROM APPS.ENG_ENGINEERING_CHANGES_V WHERE PROJECT_ID = :p_id ORDER BY INITIATION_DATE DESC;
• Incremental extract: SELECT * FROM APPS.ENG_ENGINEERING_CHANGES_V WHERE LAST_UPDATE_DATE >= :last_run;

Because organization security is enforced, callers should initialize the HR security profile (via FND_GLOBAL / MO_GLOBAL) before issuing large extracts, or expected authorization filtering will silently reduce result sets. When the search term is "change_order," this view is the recommended starting point for reporting on engineering change orders and their approval status.