Search Results eng_engineering_changes_erv

Overview

The APPS.ENG_ENGINEERING_CHANGES_ERV view is a denormalized reporting and integration object within the Oracle E-Business Suite Engineering (ENG) module. Its name follows the EBS convention for "Enterprise Reporting Views" (ERV), a class of database objects designed to flatten the normalized transactional schema into a single, human-readable projection suitable for external reporting tools, Oracle Discoverer workbooks, Oracle Business Intelligence Publisher data templates, and interface programs. The view consolidates engineering change order (ECO) master data with its associated descriptive lookups, organizational context, approval workflow attributes, and project/task references, so that consumers do not need to re-implement the extensive joins to ENG_ENGINEERING_CHANGES and its satellite tables.

The view is owned by the APPS schema, shares the standard APPS synonym/GRANT model, and is documented as VALID in ETRM 12.2.2. It is read-only by contract; all underlying data manipulation occurs against the base tables and synonyms listed below.

Underlying Base Objects

The view is defined over a mixture of base tables, synonyms to base tables, and subordinate views. The principal driving object is ENG_ENGINEERING_CHANGES (aliased EEC), the ECO header table. Supporting objects include:

• ENG_CHANGE_ORDER_TYPES_V, ENG_CHANGE_PRIORITIES, ENG_CHANGE_REASONS, ENG_CHANGE_STATUSES_VL, and ENG_CHANGE_MGMT_TYPES — lookup and classification tables supplying type, priority, reason, and status meanings.
• ENG_CHANGE_ORDER_REVISIONS and ENG_CURRENT_SCHEDULED_DATES — revision and scheduling context for affected items.
• ENG_ECN_APPROVAL_LISTS and ENG_WF_PROCESS_V — approval routing and Oracle Workflow display names.
• ENG_CHANGE_TYPE_PROCESSES — association between change types and workflow processes.
• MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS_TL — inventory organization code and translated organization name.
• HZ_PARTIES — requestor party name resolution.
• MFG_LOOKUPS — generic lookup meanings such as approval status.
• PA_PROJECTS_ALL and PA_TASKS — project and task linkage.
• PER_ORGANIZATION_STRUCTURES — organization hierarchy context.
• FND_PROFILE — profile-option driven filters and secure access values.

Because the view joins these objects with SELECT DISTINCT, it is explicitly a reporting projection rather than a transactional interface; consumers should expect column-level multiplicity to be resolved by the DISTINCT clause and should not treat ROW_ID as a stable key.

Key Columns

ROW_ID exposes the underlying EEC.ROWID for legacy tooling. CHANGE_NOTICE is the ECO number and the primary business identifier. ORGANIZATION_ID, ORGANIZATION_CODE, and ORGANIZATION_NAME provide the inventory organization context, while ECO_DEPARTMENT (from HOU.NAME) identifies the responsible engineering organization.

Lifecycle columns include INITIATION_DATE, IMPLEMENTATION_DATE, CANCELLATION_DATE, CANCELLATION_COMMENTS, APPROVAL_DATE, and APPROVAL_REQUEST_DATE, together with the derived metric DAYS_TO_APPROVE. Classification columns include ECO_STATUS, APPROVAL_STATUS, PRIORITY_CODE, REASON_CODE, CHANGE_ORDER_TYPE, ASSEMBLY_TYPE, and CHANGE_MGMT_TYPE_CODE. Cost estimates are surfaced via ESTIMATED_ENG_COST and ESTIMATED_MFG_COST. Approver routing is represented by APPROVAL_LIST_NAME and APPROVAL_PROCESS. Project integration columns include PROJECT_NAME, PROJECT_NUMBER, TASK_NAME, and TASK_NUMBER. Fifteen ATTRIBUTE columns and the ATTRIBUTE_CATEGORY expose descriptive flexfield content.

Common Use Cases and Queries

Typical uses include ECO status dashboards, approval cycle-time analysis, ECO cost estimation reporting, and extract feeds to external PLM or MES systems. A simple status report:

• SELECT change_notice, organization_code, eco_status, approval_status, initiation_date, implementation_date FROM apps.eng_engineering_changes_erv WHERE eco_status = 'Open' ORDER BY initiation_date DESC;

Cycle-time analysis using the derived column:

• SELECT change_notice, change_order_type, approval_list_name, days_to_approve FROM apps.eng_engineering_changes_erv WHERE approval_date BETWEEN :start_date AND :end_date AND days_to_approve > 30 ORDER BY days_to_approve DESC;

Project-linked changes:

• SELECT e.change_notice, e.project_number, e.task_number, e.current_revision, e.estimated_eng_cost FROM apps.eng_engineering_changes_erv e WHERE e.project_id = :project_id;

Because access is governed by FND_PROFILE and organization security, callers should run queries as an APPS-responsibility user or an account granted EXECUTE on the view, and should restrict by ORGANIZATION_ID where multi-org visibility is a concern. Performance is generally acceptable for reporting because the DISTINCT and multi-table joins are stable, but high-volume extracts should be filtered by date or organization to avoid full scans of the ECO history.