Search Results hierarchy_flag




Overview
Explore in AI Chat

Overview

ENG_ENGINEERING_CHANGES_ALL_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, exposed by the Engineering (ENG) product for releases 12.1.1 and 12.2.2. Its documented purpose is to present "all engineering change orders" recorded in the enterprise. Functionally, the view acts as the reporting and integration surface for the ECO (Engineering Change Order) entity: it consolidates change notice header information — identification, status, approval state, scheduling dates, cost estimates, descriptive flexfield context, and organization hierarchy routing — into a single queryable object. In Oracle EBS reporting and integration patterns, such views are the recommended access layer for external tools (BI Publisher, OA Framework inquiries, interfaces, and third-party integrations), because they insulate the caller from the underlying base table's column evolution and provide a consistent APPS-owned synonym. Any custom report, concurrent program, or interface reading ECO data should query this view rather than the base table directly.

Underlying Base Objects

The view is defined over exactly one documented base object: ENG_ENGINEERING_CHANGES, referenced through a synonym and aliased as EEC in the view text. There is no join; the view is a projection of the base table with an expression applied to one column. The defining query selects most header columns from EEC directly and applies NVL(EEC.HIERARCHY_FLAG, 2) to guarantee a non-null value for HIERARCHY_FLAG, defaulting to 2 when the stored value is null. The view therefore has a one-to-one row correspondence with ENG_ENGINEERING_CHANGES — it does not filter, aggregate, or union data, and it does not join to the change order lines or affected items tables. The "_ALL" suffix follows the standard EBS convention indicating the view is not constrained by organization security at the view level; organization scoping is represented by data columns (ORGANIZATION_ID and RESPONSIBLE_ORGANIZATION_ID) and must be applied by the query or by the calling form's security logic.

Key Columns

Common Use Cases and Queries

Typical scenarios include open ECO aging reports, approval status dashboards, integration extracts to PLM or MES systems, and audit queries. Because the view is unfiltered, always constrain by organization or status in production queries. A representative query retrieving active change orders with flexfield context is:

  • SELECT change_notice, description, organization_id, status_type, approval_status_type, initiation_date, implementation_date, ddf_context, attribute1, attribute2 FROM apps.eng_engineering_changes_all_v WHERE organization_id = :org_id AND status_type IN ('3','4') ORDER BY initiation_date DESC;
  • SELECT change_notice, priority_code, reason_code, estimated_eng_cost, estimated_mfg_cost FROM apps.eng_engineering_changes_all_v WHERE requestor_id = :person_id AND implementation_date IS NULL;
  • SELECT change_notice, organization_hierarchy, hierarchy_flag FROM apps.eng_engineering_changes_all_v WHERE responsible_organization_id = :org_id AND change_order_type_id = :type_id;

Because HIERARCHY_FLAG is coalesced, queries can rely on it being non-null; conversely, note that a null stored value is indistinguishable from an explicit value of 2. For dashboard and extract purposes, joining this view to change order line and affected item tables using CHANGE_NOTICE, ORGANIZATION_ID, and the change order identifier provides the detail-level breakdown the header view does not include.