Search Results days_to_approve




Overview
Explore in AI Chat

Overview

ENG_ENG_CHANGES_API_V is an APPS-owned database view in the Oracle E-Business Suite Engineering (ENG) module. Its documented purpose is to serve as the data source for the Engineering Change Order (ECO) workflow, exposing change order header information in a denormalized, display-ready form. Rather than joining multiple engineering and HR tables at the workflow or reporting layer, the view consolidates ECO attributes with their decoded lookup meanings, organizational context, and approval information into a single relational projection. The view is marked VALID and supersedes the internal table ENG_ENGINEERING_CHANGES as the primary query surface for ECO-related workflow and reporting logic. It is available in both 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over several base objects, joined primarily on the Engineering Change Order identifier (CHANGE_NOTICE) and foreign keys to lookup and reference tables. The documented referenced objects are:

Outer joins are used for the reason, priority, and related optional lookups, ensuring ECO rows are not dropped when optional codes are null.

Key Columns

Common Use Cases and Queries

The view is typically queried by ECO approval workflows, ECO status dashboards, and integration extracts requiring decoded change order data. A representative query follows:

  • List pending ECOs with decoded status and requestor:
    SELECT change_notice, eco_status, change_order_type, requestor, days_to_approve FROM apps.eng_eng_changes_api_v WHERE approval_status_type = 'PENDING' AND organization_id = :org_id ORDER BY initiation_date DESC;
  • Aggregate approval cycle times by department:
    SELECT eco_department, AVG(days_to_approve) FROM apps.eng_eng_changes_api_v WHERE approval_date IS NOT NULL GROUP BY eco_department;
  • Extract ECO header details for an external system:
    SELECT change_notice, description, implementation_date, priority_code_description, estimated_eng_cost FROM apps.eng_eng_changes_api_v WHERE change_notice = :ecn;

Because the view is API-oriented and used by workflow, it should be queried rather than updated directly; ECO modifications must go through the standard Engineering APIs.