Search Results ecg_ecn_status




Overview
Explore in AI Chat

Overview

APPS.ENG_WEB_SCHEDULE_V is a reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that consolidates engineering change order (ECO) header data with the revised item schedule lines generated against each change. It is owned by the APPS schema and is defined over the core Engineering (ENG) tables, joining them to BOM, inventory, HR, and lookup views to present a denormalized, web-oriented result set suitable for the Engineering Change Order scheduling and status screens.

The view answers the practical question of "which revised items are scheduled against which engineering change orders, in which organization, and at what status?" Because it resolves lookup codes into their meanings and resolves IDs into human-readable item numbers and person names, it is well suited for reporting and for integration interfaces that need ECO schedule data without reimplementing the join logic. The user search term "ecg_ecn_status" corresponds directly to the lookup type used inside this view: both ECO.STATUS_TYPE and ERI.STATUS_TYPE are resolved against MFG_LOOKUPS.LOOKUP_TYPE = 'ECG_ECN_STATUS', so the view is a primary consumer of that lookup.

Underlying Base Objects

Per the documented ETRM metadata, the view references the following base objects: BOM_BILL_OF_MATERIALS (view), ENG_CHANGE_ORDER_TYPES (synonym), ENG_CHANGE_REASONS (synonym), ENG_ENGINEERING_CHANGES (synonym), ENG_REVISED_ITEMS (synonym), MFG_LOOKUPS (view), MTL_ITEM_FLEXFIELDS (view), MTL_PARAMETERS (synonym), PER_PEOPLE_F (view), HR_ORGANIZATION_UNITS (view), and the packages FND_GLOBAL, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY.

The driving relationship is between ENG_ENGINEERING_CHANGES (aliased ECO) and ENG_REVISED_ITEMS (aliased ERI), joined on CHANGE_NOTICE and ORGANIZATION_ID. ENG_CHANGE_ORDER_TYPES supplies the change order type description, ENG_CHANGE_REASONS supplies the reason description, and MTL_ITEM_FLEXFIELDS supplies the revised item number, padded item number, and description. MTL_PARAMETERS provides the organization code. MFG_LOOKUPS is joined five times to decode status, approval status, revised item status, MRP active flag, and update WIP flag. HR views and packages (PER_PEOPLE_F, HR_ORGANIZATION_UNITS, HR_GENERAL, HR_PERSON_NAME, HR_SECURITY) resolve the requestor name and responsible department while enforcing HR security. BOM_BILL_OF_MATERIALS is an outer join (indicated by (+)) on BILL_SEQUENCE_ID so schedule lines without a bill are still returned. FND_GLOBAL typically supplies session context such as organization and user identifiers.

Key Columns

Common Use Cases and Queries

Typical uses include ECO schedule dashboards, revised item status reporting, and integration extracts feeding downstream planning or manufacturing systems. Because status meanings are already decoded, consumers can filter directly on readable values.

Query pending revised items for an organization:

  • SELECT change_notice, revised_item, new_item_revision, eco_status, scheduled_date FROM apps.eng_web_schedule_v WHERE organization_id = :org_id AND implementation_date IS NULL ORDER BY scheduled_date;

Query all schedules for a given ECO number:

  • SELECT revised_item, revised_item_description, revised_item_status, update_wip, mrp_active FROM apps.eng_web_schedule_v WHERE change_notice = :change_notice;

Aggregate workload by department and status:

  • SELECT department, eco_status, COUNT(*) FROM apps.eng_web_schedule_v GROUP BY department, eco_status;

Filter by approval status meaning:

  • SELECT change_notice, approval_status, approval_date FROM apps.eng_web_schedule_v WHERE approval_status = 'Approved';

Note that the view applies HR security through HR_SECURITY and HR_GENERAL, so rows may be restricted based on the querying user's security profile. For high-volume extracts, restrict by ORGANIZATION_ID and date ranges to limit the multi-way join cost.