Search Results mfg_implementaion_costs

Overview

The APPS.ENGBV_ENGINEERING_CHNG_ORDERS view is a Business View (BV) in the Oracle E-Business Suite Engineering (ENG) module. It presents a denormalized, read-only representation of Engineering Change Orders (ECOs) by joining engineering change records to their owning inventory organization and to the human resources organization definition. The view is retained across both Oracle EBS 12.1.1 and 12.2.2 and is catalogued as VALID in the ETRM metadata for release 12.2.2.

Its principal role is to expose engineering change order data in a reporting-friendly and integration-friendly format. The view resolves internal surrogate identifiers and lookup codes into human-readable names and meanings — for example, organization names, organization codes, and translated values for approval status and change order status — so that downstream reports, extracts, and interface programs do not need to reconstruct these joins or resolve lookups themselves. The view is defined WITH READ ONLY and includes a security predicate on the organization identifier, meaning it is intended strictly for query access and is subject to organization-level access control for the querying responsibility.

Underlying Base Objects

The view is defined over three documented base objects, each referenced through a synonym in the APPS schema:

• ENG_ENGINEERING_CHANGES — the primary ECO table, aliased as EN in the view text. It supplies the change notice number, dates, cost estimates, statuses, and the full set of foreign key identifiers.
• HR_ALL_ORGANIZATION_UNITS — aliased as AL, joined on ORGANIZATION_ID to provide the organization NAME.
• MTL_PARAMETERS — aliased as PA, also joined on ORGANIZATION_ID, to provide the ORGANIZATION_CODE used in inventory reporting contexts.

The join condition requires that EN.ORGANIZATION_ID equal both AL.ORGANIZATION_ID and PA.ORGANIZATION_ID, so an ECO is returned only where a matching inventory organization and HR organization unit exist. The security predicate '_SEC:EN.ORGANIZATION_ID' IS NOT NULL enforces organization-level access filtering at runtime.

Key Columns

The view exposes the following significant columns:

• ECO_NAME — the engineering change notice number (EN.CHANGE_NOTICE); the primary human identifier for the ECO.
• ORGANIZATION_NAME / ORGANIZATION_CODE — the owning organization's descriptive name and inventory code, sourced from HR_ALL_ORGANIZATION_UNITS and MTL_PARAMETERS respectively.
• ECO_CREATION_DATE — derived from EN.INITIATION_DATE; this is the column users typically retrieve when searching for the ECO creation date (the mapped term "eco_creation_date").
• DESCRIPTION, IMPLEMENTATION_DATE, CANCELLATION_DATE, CANCELLATION_COMMENTS — narrative and lifecycle dates for the change.
• PRIORITY_CODE, REASON_CODE — classification codes for the change.
• ENG_IMPLEMENTATION_COSTS / MFG_IMPLEMENTAION_COSTS — estimated engineering and manufacturing costs derived from EN.ESTIMATED_ENG_COST and EN.ESTIMATED_MFG_COST (note the documented column name spelling).
• "_LA:APPROVAL_STATUS_TYPE" and "_LA:STATUS_TYPE" — lookup-attribute display columns resolving approval status and ECO status through MFG_LOOKUPS.
• APPROVAL_DATE, APPROVAL_REQUEST_DATE — approval lifecycle dates.
• ORGANIZATION_ID, REQUESTOR_ID, APPROVAL_LIST_ID, CHANGE_ORDER_TYPE_ID, RESPONSIBLE_ORGANIZATION_ID, PROJECT_ID, TASK_ID — the underlying foreign keys retained for further joins.
• CREATED_ON, CREATED_BY, UPDATED_ON, UPDATED_BY — audit columns mapped from CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY.

Common Use Cases and Queries

Typical uses include ECO registries, change-order aging reports, cost-estimate summaries, and data extracts feeding external PLM or quality systems. The view is also convenient for ad-hoc investigation of a specific change number or a date window.

Retrieving recent ECOs with their creation date for a given organization:

• SELECT eco_name, organization_code, eco_creation_date, implementation_date FROM apps.engbv_engineering_chng_orders WHERE organization_id = :org_id AND eco_creation_date >= :from_date ORDER BY eco_creation_date DESC;

Listing open change orders by status and estimated cost:

• SELECT eco_name, description, "_LA:STATUS_TYPE" status, eng_implementation_costs FROM apps.engbv_engineering_chng_orders WHERE eco_name = :eco_name;

Because the view is read-only and includes the organization security predicate, no DML is possible through it, and results are automatically restricted to organizations accessible to the querying responsibility.