1 / 50

EMT: Enabling the Supply Chain

EMT: Enabling the Supply Chain. Kelly Andrews March 20, 2006. What we will cover. Introduction to EMT/Ecommerce Basic Terminology Business Unit Tasks General System Set Up Differences/Similarities of Direct and Transhipment Orders Change Management (Business Unit Responsibilities)

xenos
Download Presentation

EMT: Enabling the Supply Chain

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EMT: Enabling the Supply Chain Kelly Andrews March 20, 2006

  2. What we will cover • Introduction to EMT/Ecommerce • Basic Terminology • Business Unit Tasks • General System Set Up • Differences/Similarities of Direct and Transhipment Orders • Change Management (Business Unit Responsibilities) • Basic Set Up within Ecommerce • Trouble Shooting Ecommerce and Reviewing Reports • Q & A

  3. Introduction to EMT Enterprise Material Transfer (EMT) is a process in which most aspects of material replenishment can be handled automatically for a business unit or multiple business units within the supply chain. Ecommerce in conjunction with EMT enables the passing of data between the various business units of the supply chain.

  4. Advantages of EMT • Saves time through order fulfillment process. • Handles both End Items and Configured Products • Allows for different shipment methods • Enables the movement of material across national borders

  5. Features of EMT • Integrates with standard invoicing. • Handles changes and automatically transmits them to supplier site. • Can use EMT with a single database or with multiple databases. • Can use certain features of EMT without using Ecommerce.

  6. Basic Terminology • Primary Business Unit (PBU): Organization responsible for processing the customer’s original PO and creating a sales order. • Secondary Business Unit (SBU): Organization responsible for maintaining sales orders created from PBU purchase order. • Transhipment (Transship): Movement of material from the SBU to the PBU. • Direct Shipment (Dir-ship): Movement of material from the SBU directly to the customer (drop shipment). • Trading Partner: A company you are selling to or buying from.

  7. PBU and SBU the Big Picture

  8. Interface with Sales Entry (PBU) Sales order created for EMT part PO Automatically Generated for Item

  9. More Terminology • Electronic Data Interchange (EDI): EMT uses EDI to transfer messages between the PBU and SBU. The import and export of EDI messages is steered by the Transmission Manager.

  10. Exporting and Importing for EMT • Frequency of zero indicates one entire pass through pending EMT transactions. • PBU export PO, PO changes and import files. • SBU export ASN, PO Acknowledgement and PO Change Acknowledgement.

  11. Tasks of PBU and SBU (Order Related) • PBU – Export PO to SBU (850) • SBU – Import PO from PBU (850) • SBU – Export PO Acknowledgment (855) • PBU – Import PO Acknowledgment (855) PBU 850 855 SBU

  12. SBU Order Interface

  13. Checkpoints after PO export • PBU order cannot be deleted prior to acknowledgement by SBU. • PBU order quantity and due date cannot be modified until acknowledgement sent by SBU. • PO Number cannot be changed at SBU. • Deletion of sales order cannot occur at SBU.

  14. PO Acknowledgement Control • Two control mechanisms for PO acknowledgement (manual and automatic) • Manually, orders can be acknowledged via 35.4.4 Purchase Order Ack. Maintenance • Automatically, a PO can be acknowledged by using ‘Use Inbound Ack. Status’ in 35.13.10 Trading Partner Parameter (note, map must contain status value).

  15. Tasks of PBU to SBU Changes PBU • PBU – Export PO Change to SBU (860) • SBU – Import Change from PBU (860) • SBU – Export PO Change Acknowledgement (865) • PBU – Import PO Change Acknowledgment (865) 860 865 SBU

  16. EMT Type Ship-to Supplier Order Status Quantity Ordered UM Due Date Ship-via (so_ship via) PBU Changes Queued for Export (Part 1)

  17. PBU Changes Queued for Export (Part 2) • FOB • Customer PO (PBU PO is not changed but order queued) • Header Comments • Site (Transship Orders only) • Price/Cost • Type/Location (Update of sales location and type update the purchase order, the order is not queued) • Configuration Type/Line Description • Line Comments

  18. More Terminology • Change Management Files (CMFs): A table that retains the values of the EMT sales order prior to changes made during their lifecycle. • CMF’s are created to represent changes after the original order (PO) is electronically sent. • The CMF file contains the original fields value

  19. Change Management Files • Created when order changed. • Visible within report ‘35.22.4 Change Management Report’ • Updateable within 35.22.1 Manual Ack Resolution’ • Sent as PO change (860) to SBU.

  20. SBU Change Management Files • Created when changing SBU sales order. • CMF’s are created to represent changes after the original order (SO) is electronically received. • The CMF file contains the original fields value • Sent as PO change acknowledgement (865) to PBU.

  21. SBU Changes Queued for Export • Quantity or Unit of Measure • Promise Date

  22. More Terminology • Advance Ship Notice (ASN): An electronic document derived from the shipper and sent as notification of shipment.

  23. Tasks of PBU and SBU (Shipment) PBU • SBU – Builds shipper for requirements. • SBU – Exports shipper to PBU (856) • PBU – Imports shipper (856). 856 SBU

  24. Transhipment Orders Customer • SBU Builds and ships to PBU (Invoicing PBU for Material) • PBU receives inventory. (Sales order automatically allocated) • PBU builds shipper. • PBU ships material to customer. (Invoicing Customer for Material) Product PBU Product SBU

  25. Direct Shipment Orders Customer • SBU Builds and ships to PBU. • PBU Receives Electronic ASN. • PO Receipt Occurs automatically or manually. • SO Shipment Occurs automatically • Customer receives material. Product PBU SBU

  26. Tracking the EMT Order • Orders can be tracked with EMT Tracking Report. • Status of SBU order. • Transmission status of PBU PO.

  27. 7.15.11 EMT Tracking Report • EMT Type • 02 Tranship • 03 Direct Shipment

  28. SBU Sales Status • ‘SS’ represents SBU sales status Valid SBU sales status’: P: Picklist or shipper (SBU) created with detail allocations. W: Work order released at SBU (configured ATO) S: Shipment made at SBU

  29. Transmission Status • Transmission Status represents the state of the PBU purchase order. Valid Status: 1: PO newly created 2: PO exported to SBU 3: PO acknowledged by SBU 4: Change made to PBU order 5: PO Change exported from PBU 3: PO Change acknowledgement imported by PBU

  30. Primary MFG/PRO Settings for EMT • Sales Order Control File (7.1.24) EMT Controls Frame • Purchase Order Control File (5.24) Acknowledgement Field • Customer Master (2.1.1) EMT Data Frame • Supplier Master (2.3.1) EMT Data Frame • Item and Item-Site Planning record (1.4.1 / 1.4.17) • Trading Partner Parameter Maintenance (35.13.10)

  31. Sales Order Control Frame • Use Enterprise Material Transfer must be ‘yes’ at PBU • Calculate Due Date controls due date on PBU PO • Auto Accept Supplier Changes • Allow Mod/Delete controls allowance of changes after activity occurs at SBU.

  32. Purchase Order Control Frame • Controls requirements for PO acknowledgement of Order at SBU. • Transmission status set to acknowledged (3) if set to no. • Acknowledgement required and changes cannot be made until response received from SBU (PO Acknowledgement)

  33. Customer EMT Settings • EMT Type – Default if EMT Sequence is set to ‘C’. • Shipping Lead time used for purchase order due date.

  34. Supplier EMT Settings • Price of PO and sales pricing information controlled by supplier set up. • Credit held sales orders can be exported to SBU. • Auto EMT Processing – used for TBU EMT (Tertiary Business Unit) • Automatic PO Receipt set to yes will automatically perform PO receipt and sales order issue for direct ship EMT orders.

  35. Item and Item-Site EMT Settings • Default supplier for EMT Sales Orders. • Default EMT Type if EMT Sequence is set to ‘A’ (Item-Site) or ‘B’ (Item)

  36. PBU Trading Partner Settings PBU PBU Supplier and Site Settings • PBU Exports orders and order changes to the SBU. • Send EDI PO (Parameter 6) controls both 850 and 860 documents. 860 850 SBU

  37. SBU Trading Partner Settings SBU Supplier and Site Settings PBU • SBU Exports order acknowledgements, change acknowledgements and ASN. • Send EDI PO Ack (Parameter 3) controls both 855 and 865 documents. • Send Partial PO Ack controls if one of multiple lines can be acknowledged. (Manually Controlled). • Inbound Status from document import can enable automatic sending of PO acknowledgement. 855 865 856 SBU

  38. SBU Manual Acknowledgement Manual Acknowledgement requires update of SBU Sales Order Status Valid Status: 0 Pending acknowledgement 1 Accepted in Full 2 Accepted with a change 3 Rejected

  39. SBU Automatic Acknowledgement 850 Import with Acknowledgement • Acknowledgement level hard coded during import of PO. • Level of ‘1’ will enable automatic PO acknowledgement.

  40. PBU/SBU Trading Partner Parameter Settings • Character Parameter value represents MFG/PRO Definition. • Integer Parameter value represents the MFG/PRO Definition Version. • “PO Chg Document Name” for character parameter value to export PO Changes. (MFG/PRO Eb2) • “PO Chg Document Ver” for integer parameter value to export PO Changes.

  41. Ecommerce Set Up • Trading Partner for each EMT document type • EC Subsystem for EMT Process (one or multiples can be created) • Transmission Group for outbound information. • EC Subsystem/Exchange Record

  42. Trading Partner Set Up • Documents using one TP-ID for each transmission type • Document Map (35.15.17 Transformation Definition) • Transmission Group represents details for outbound document. (35.13.13 Transmission Group Maintenance)

  43. Trading Partner Set Up PBU • Purchase Order document for outbound • Site represents Purchase order site • Address represents Supplier

  44. Trading Partner Set Up SBU • Purchase Order Import • Site represents sales order site • Address represents Customer • TP Site and TP Address should be the same in both records.

  45. EC Subsystem (Part 1) • File Extension determines EC System. • Record Code Position determines control code position.

  46. EC Subsystem (Part 2) • Trading partner tokens (tp-document-id, tp-id, tp-address and tp-site) validate against settings in Trading Partner Set Up. • Use the same settings for both inbound and outbound definition !

  47. Transmission Group • Provides outbound directory. • Links EC subsystem with Transmission group. • Required for outbound documents.

  48. EC Subsystem/Exchange • Links EC Subsystem to Exchange records. • Defines data control codes for Exchange records.

  49. Big Ecommerce Picture (Simplified – We hope!) TP Settings (EC Subsystem) File Extension (EC Subsystem) EC Subsystem/Exchange Record

  50. Questions ???

More Related