This is a photographic template – your
photograph should fit precisely within this rectangle.
Eaton Corporation - EMT and EDI
Rachael Thompson
September 2011
© 2008 Eaton Corporation. All rights reserved.
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
2
2
Agenda
• Eaton’s EMT / EDI evolvement
• What exactly is EMT and EDI
• Eaton’s customized solutions
• Questions?
3
3
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
4
4
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)
5
5
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 <EMT> PBU PO <EDI> SBU SO
PBU SO
PBU PO
SBU SO
PSO456
PPO789
SSO789
EMT
EDI
6
6
Manual Intervention Comparison
NO EMT or EDI
ACTION PBU SBU
7.1.1
X
5.7
X
CONTACT X
X
7.1.1
X
EMT ONLY
ACTION PBU SBU
7.1.1
X
5.7
CONTACT X
X
7.1.1
X
EMT and EDI
ACTION PBU SBU
7.1.1
X
5.7
CONTACT
7.1.1
7
7
Creating an EMT Order
• PBU Location
• 7.1.1 – SO created (either manually or electronic import)
• 5.7 – PO automatically created if item is setup as EMT
• 35.4.9 – PO electronically exported
• SBU Location
• 35.1 – PO electronically imported
• 7.1.1 – SO automatically created and confirmed
• 35.4.5 – POA electronically exported from SBU
• PBU Location
• 35.1 – POA electronically imported into PBU
8
8
Modifying an EMT Order
• PBU Location
• 7.1.1 – SO manually modified
• 5.7 – PO automatically modified
• 35.22.16 – POC electronically exported
• SBU Location
• 35.1 – POC electronically imported
• 7.1.1 – SO automatically modified
• 35.22.15 – PCA electronically exported
• PBU Location
• 35.1 – PCA electronically imported
9
9
Picking/Shipping an EMT Order
• SBU Location (Picking)
• 7.9.1/2 – SO Shipper manually created
• 35.22.15 – PCA electronically exported
• PBU Location
• 35.1 – PCA electronically imported
• 7.1.1 – SO automatically updated as “picked”
• SBU Location (Shipping)
• 7.9.5 – SO Shipper confirmed
• 35.4.1 – ASN electronically exported
• PBU Location
• 35.1 – ASN electronically imported
• 5.5.5.6 – PO Shipper automatically created
10
10
Receiving an EMT Order
• PBU Location (TRANSHIP)
• 5.13.20 – PO Shipper manually received
• 7.9.1/2 – SO Shipper manually created
• 7.9.5 – SO Shipper manually confirmed
• PBU Location (DIR-SHIP)
• 5.13.20 – PO Shipper automatically received
• 7.9.1/2 – SO Shipper automatically created
• 7.9.5 – SO Shipper automatically confirmed
11
11
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.
12
12
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 PO12345.
• 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 P1234509/25/11.
• ERROR: Line is closed or canceled for PO PO12345 IT1234 S1.
• ERROR: Order not for this supplier PO12345.
• ERROR: Changes exist for PO12345.
13
13
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.
14
14
Eaton Corporation Customizations
• Eaton currently emails 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 emailed 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.
15
15
Standard EMT Setup Programs/Menus
MENU
2.3.1
1.1.13
2.12
2.1.1
1.4.1
1.4.17
1.16
1.19
7.1.24
5.24
DESCRIPTION
Supplier Maintenance
Site Maintenance
Company Address Maintenance
Customer Maintenance
Item Master
Item-Site Planning Maintenance
Customer Item Maintenance
Supplier Item Maintenance
Sales Order Control
Purchasing Control
PBU SBU
X
X
X
X
X
X
X
O
O
X
X
X
X
X
NOTES
EMT Type (NON-EMT, TRANSHIP, DIR-SHIP)
Require Acknowledgement?
16
16
Standard EDI Setup Programs/Menus
Program
eddmnmt.p
edssmt.p
edcpm.p
edtpload.p
edsxxmt.p
edtgmt.p
edtrptmt.p
edtppmmt.p
Description
Domain Cross Reference Maint
EC Subsystem Definition Maint
ECommerce Control
Trading Partner Library Load
EC Subsystem/Exchange Maint
Transmission Group Maintenance
Trading Partner Maintenance
Trading Partner Parameter Maint
Menu 9.0 eB
Menu eB2
35.21.13.1
35.21.13.24
35.21.17.7
35.21.13.4
35.21.13.13
35.21.13.7
35.21.13.10
35.13.1
35.13.24
35.17.7
35.13.3
35.13.13
35.13.7
35.13.10
17
Menu eB2.1
35.11.1
35.13.1
35.13.24
35.17.7
35.13.3
35.13.13
35.13.7
35.13.10
17
TP Maintenance – PBU 850/860 Outbound
18
18
TP Maintenance – SBU 850/860 Inbound
19
19
TP Maintenance – SBU 855/865/856 Outbound
20
20
TP Maintenance – PBU 855/856/865 Inbound
21
21
Questions and Answers
22
22
23
23