Search Results eng_engineering_changes




The ENG_ENGINEERING_CHANGES table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 is a critical repository for managing engineering change orders (ECOs) within the Engineering module. This table serves as the foundation for tracking modifications to items, bills of materials (BOMs), and routings, ensuring controlled implementation of product design changes. Below is a detailed analysis of its structure, functionality, and integration within Oracle EBS.

Table Structure and Key Columns

The ENG_ENGINEERING_CHANGES table stores metadata for ECOs, including:
  • CHANGE_ID: Primary key uniquely identifying each ECO.
  • ORGANIZATION_ID: Links to the inventory organization where the change applies.
  • CHANGE_NOTICE: User-defined ECO number (e.g., "ECO-1001").
  • STATUS_TYPE: Tracks workflow states (Pending, Approved, Implemented, Rejected).
  • IMPLEMENTATION_DATE: Scheduled or actual date of change execution.
  • REVISION: Associated item revision affected by the change.
  • DESCRIPTION: Free-text field documenting change purpose.
  • CREATION_DATE and LAST_UPDATE_DATE: Audit timestamps.

Functional Role in Engineering Change Management

The table supports end-to-end ECO workflows:
  1. Initiation: New ECO records are created via Oracle Engineering or PLM interfaces.
  2. Approval Routing: Status transitions trigger notifications through Oracle Workflow.
  3. Impact Analysis: Child tables (ENG_CHANGE_ITEMS, ENG_CHANGE_COMPONENTS) link to affected BOMs/items.
  4. Implementation: Approved changes propagate to inventory/BOM modules via concurrent programs.

Integration with Oracle EBS Modules

Key touchpoints include:
  • Inventory: Item revisions and effectivity dates sync with MTL_SYSTEM_ITEMS_B.
  • Bills of Material: Changes cascade to BOM_BILL_OF_MATERIALS upon implementation.
  • Work in Process: WIP jobs reference ECO-controlled BOM versions.
  • Costing: Cost rollups consider ECO-driven component substitutions.

Technical Considerations

Implementation nuances in EBS 12.1.1/12.2.2:
  • Data Security: Rows are organizationally partitioned; MOAC (Multi-Org Access Control) policies apply.
  • Performance: Indexes on CHANGE_NOTICE and ORGANIZATION_ID optimize large-scale queries.
  • Upgrades: Schema remains consistent between 12.1.1 and 12.2.2, but 12.2.2 adds Oracle Fusion Middleware dependencies for workflow.

Customization and Extensions

Common enhancements include:
  • Custom statuses added via lookup types (FND_LOOKUP_VALUES).
  • Triggers on STATUS_TYPE to integrate with third-party PLM systems.
  • APEX or OAF pages built to supplement standard Oracle Engineering forms.

Best Practices

  • Leverage Oracle's ECO approval workflows instead of custom status management.
  • Maintain referential integrity with periodic validation scripts against child tables.
  • Archive implemented ECOs to historical tables for reporting performance.
This table exemplifies Oracle's integrated approach to change management, bridging engineering, manufacturing, and supply chain functions while maintaining auditability and process control.