© 2008 Eaton Corporation. All rights reserved. This is a photographic template – your photograph should fit precisely within this rectangle. Eaton Corporation - EMT and EDI Rachael Thompson September 2011

2 2 Introduction – Rachael Thompson IT Manager of EDI Integration - Eaton Corporation Team responsible for EDI implementations and support activities for all Industrial Sector facilities (Hydraulic, Aerospace, and Vehicle) around the world which utilize MFG/PRO EDI is currently implemented in more than 40 Databases (Version 7.4, 8.6, 9.0, eB, eB2, and eB2.1), 25 Domains, and 100 Sites EMT is currently implemented in more than 10 Databases, 5 Domains, and 25 Sites. Bachelor’s Degree Business Administration, Tiffin University

3 3 Agenda Eaton’s EMT / EDI evolvement What exactly is EMT and EDI Eaton’s customized solutions Questions?

4 4 Eaton – Overview of EMT/EDI Evolvement Boston Weatherhead Acquisition Customers ordered similar products from Cleveland, TN or Vanwert, OH Vanwert (7.4) did not have standard EMT or EDI Customized Multi-Channel process (like EMT) EC Bridges Solution to export/import EDI Sterling Gentran to translate EDI SwissCo Model Customers ordered products from US locations US (PBU) and MX (SBU) locations in same Database (eB) Utilized “canned” EMT EDI (progress programs) Synflex Acquisition Similar to SwissCo but Aurora (eB2.1) did not have “canned” EMT EDI Could implement IC Model (Ecommerce-Gentran-Ecommerce) Transformations SNF-SNF reduces processing time and resources Implementations quick and consistent

5 5 Acronyms - EMT and EDI EMT = Enterprise Material Transfer EDI = Electronic Data Interchange PBU = Primary Business Unit SBU = Secondary Business Unit DIR-SHIP = Shipment from SBU directly to Customer TRANSHIP = Shipment from SBU to PBU SO = Sales Order PO = Purchase Order (EDI 850) POA = PO Acknowledgement (EDI 855) POC = PO Change (EDI 860) PCA = POC Acknowledgement (EDI 865) ASN = Advanced Shipping Notice (EDI 856) PS = Planning Schedule (EDI 830)

6 6 Definitions of EMT and EDI Enterprise Material Transfer (EMT) enables you to automatically translate a Sales Order into a Purchase Order which can then be transmitted to your supplier. Electronic Data Interchange (EDI) enables you to electronically export, send, receive, and import business documents thus eliminating manual entry. PBU SO PBU PO SBU SO PBU SO PSO456 PBU SO PSO456 PBU PO PPO789 PBU PO PPO789 SBU SO SSO789 SBU SO SSO789 EMTEDI

7 7 Manual Intervention Comparison NO EMT or EDI ACTIONPBUSBU 7.1.1X 5.7X CONTACTXX X EMT ONLY ACTIONPBUSBU 7.1.1X 5.7 CONTACTXX X EMT and EDI ACTIONPBUSBU 7.1.1X 5.7 CONTACT 7.1.1

8 8 Creating an EMT Order PBU Location – SO created (either manually or electronic import) 5.7 – PO automatically created if item is setup as EMT – PO electronically exported SBU Location 35.1 – PO electronically imported – SO automatically created and confirmed – POA electronically exported from SBU PBU Location 35.1 – POA electronically imported into PBU

9 9 Modifying an EMT Order PBU Location – SO manually modified 5.7 – PO automatically modified – POC electronically exported SBU Location 35.1 – POC electronically imported – SO automatically modified – PCA electronically exported PBU Location 35.1 – PCA electronically imported

10 Picking/Shipping an EMT Order SBU Location (Picking) 7.9.1/2 – SO Shipper manually created – PCA electronically exported PBU Location 35.1 – PCA electronically imported – SO automatically updated as “picked” SBU Location (Shipping) – SO Shipper confirmed – ASN electronically exported PBU Location 35.1 – ASN electronically imported – PO Shipper automatically created

11 Receiving an EMT Order PBU Location (TRANSHIP) – PO Shipper manually received 7.9.1/2 – SO Shipper manually created – SO Shipper manually confirmed PBU Location (DIR-SHIP) – PO Shipper automatically received 7.9.1/2 – SO Shipper automatically created – SO Shipper automatically confirmed

12 Behind the Scenes (po_xmit, trq_mstr, cmf_mstr) Whenever EMT POs are created, changed, exported, and/or acknowledged, the po_mstr.po_xmit is updated to reflect the status of the PO as follows: 1 – EMT PO Created 2 – EMT PO Exported 3 – EMT PO Acknowledged 4 – EMT PO Changed 5 – EMT POC Exported Whenever EMT POs are created, changed, exported, acknowledged, or shipped a trq_mstr record is created to indicate a respective EDI transaction can be exported as follows: ORDERS – EMT PO (850) ORDCHG – EMT PO Change (860) ORDRSP-I – EMT PO Acknowledgement (855) ORDRSP-C – EMT PO Change Acknowledgement (865) ORDRSP-S – EMT PO Change Acknowledgement (865) ASN – Advanced Shipping Notice (856) Whenever EMT POs are changed, a cmf_mstr record is created to indicate an EDI transaction can be exported. They get deleted from SBU after EDI transaction (ex. 865 or 856) is exported. They get deleted from the PBU only after an EDI PCA (865) is imported.

13 EDI Import ERROR Examples EDI Import ERRORs occur for a variety of reasons. ERRORs during EDI Import of 860 into SBU: ERROR: Purchase Order does not exist PO ERROR: SO SO12345 Line 1 Picked qty 123. ERROR: Change not allowed. Line(s) already picked. ERROR: PO change not loaded. CMF acknowledgement exists. ERRORs during EDI Import of 856 or 865 into PBU: ERROR: PO is closed P /25/11. ERROR: Line is closed or canceled for PO PO12345 IT1234 S1. ERROR: Order not for this supplier PO ERROR: Changes exist for PO12345.

14 Eaton Corporation Customizations Stranded trq_mstr records happen for a variety of reasons and as the number increases then the EDI processing times also increase exponentially. Eaton has designed a customized program to automatically delete stranded trq_mstr records to run on a daily basis. Stranded cmf_mstr records also happen for a variety of reasons and prevent future updates or processing of the corresponding SO/PO. Eaton is currently designing a customized program to automatically delete stranded cmf_mstr records to run after the 860 export.

15 Eaton Corporation Customizations Eaton currently s EDI Import ERRORs to respective employees who can take immediate action. However, sometimes the action is delayed or there is simply no immediate action which can be taken. Therefore, Eaton has designed a customized program to create an EMT Audit Report. A program is first executed on the SBU Database to export all of the EMT SO information. Another program is then executed on the PBU Database to compare that SBU information to all of the EMT SO/PO information available in the PBU Database. The discrepancies are then output to another file and ed to the respective employee who can perform the remaining actions to fix them. Eaton customized an EMT process to automatically copy PBU Customer Schedule header/detail information into PBU Supplier Schedules and transfer that information down to the SBU automatically creating Customer Schedules. Standard EDI then transfers the demand from the PBU to the SBU.

16 Standard EMT Setup Programs/Menus MENUDESCRIPTIONPBUSBUNOTES 2.3.1Supplier MaintenanceX Site MaintenanceXX 2.12Company Address Maintenance X 2.1.1Customer Maintenance X 1.4.1Item MasterXXEMT Type (NON-EMT, TRANSHIP, DIR-SHIP) Item-Site Planning MaintenanceOO 1.16Customer Item Maintenance X 1.19Supplier Item MaintenanceX Sales Order ControlXX 5.24Purchasing ControlX Require Acknowledgement?

17 Standard EDI Setup Programs/Menus ProgramDescriptionMenu 9.0 eBMenu eB2Menu eB2.1 eddmnmt.pDomain Cross Reference Maint edssmt.pEC Subsystem Definition Maint edcpm.pECommerce Control edtpload.pTrading Partner Library Load edsxxmt.pEC Subsystem/Exchange Maint edtgmt.pTransmission Group Maintenance edtrptmt.pTrading Partner Maintenance edtppmmt.pTrading Partner Parameter Maint

18 TP Maintenance – PBU 850/860 Outbound

19 TP Maintenance – SBU 850/860 Inbound

20 TP Maintenance – SBU 855/865/856 Outbound

21 TP Maintenance – PBU 855/856/865 Inbound

22 Questions and Answers

23