1 / 54

Extreme Ecommerce

Extreme Ecommerce. The EDI Warehouse Makeover Edition. Agenda. Introduction Breaking down broker EDI Building a warehouse example Extreme warehouse example Q & A. Introduction – Terry Magovern. Terry Magovern ECbridges Product Development Manager. Part I Brokers & EDI. Brokers.

tana
Télécharger la présentation

Extreme Ecommerce

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. Extreme Ecommerce The EDI Warehouse Makeover Edition

  2. Agenda • Introduction • Breaking down broker EDI • Building a warehouse example • Extreme warehouse example • Q & A

  3. Introduction – Terry Magovern Terry Magovern ECbridges Product Development Manager

  4. Part IBrokers & EDI

  5. Brokers • Commissioned salesperson • Many suppliers, many functions • Marketing & data gathering

  6. Broker Supplier QAD ERP Customer Broker EDI players • 3 parties involved

  7. Broker Supplier Customer Broker EDI PO 850 875 or

  8. ERP & Ecommerce / EDI SYSTEM Supplier Create SO Create SO ERP’s SO 850

  9. ERP & Ecommerce / EDI SYSTEM Supplier Confirm SO Confirm SO ERP’s SO 850

  10. ERP & Ecommerce / EDI SYSTEM Supplier Convert SO to PO Ack. ERP’s SO ERP’s SO 855 850

  11. Broker Supplier Customer Transmit PO Ack. 855

  12. Broker Supplier Customer Transmit Advance Ship Notice 856

  13. Broker Supplier Customer Ship goods

  14. Broker Supplier Customer Transmit Invoice 810 Paper Invoice

  15. Broker PO(850)(875) PO Ack (855) PO(850)(875) Supplier QAD ERP Invoice (810)(880) PO Ack (855) Customer Ecommerce / EDI Customer Order Flow Review

  16. Broker EDI ID 875 message – Inbound PO ISA*00* *00* *08*054635834 *08*1283490000 *050112*071 7*U00303*0000000651*0*P*> GS*OG*925141CORP*1283490000*980302*0717*148*T*003060UCS ST*875*148001 G50*N*50112*PO156999 N9*AN*15699800 G61*BD*JOAN KENNEY*TE*6329921949 G62*02*980316 G66*PP*M****04 N1*ST*SUPER VALUE STORES-MPLS DIV*9*6226552160020 N3*101 MAIN ST N4*ANYTOWN*NJ*29873 N1*VN*JONES & SONS*9*1283490000 G68*120*CA**009012315360***PI*0460417 G70*12*6.50Z*****015008 G68*84*CA**007060005200***PI0460449 G70*12*16*OX*****014003 G72*5*02***-.97 G76*446*CA*4210*LB*191*CF SE*24*148001 GE*1*148 IEA*0001*0000651 N1ST04 “Ship-to”

  17. Inbound order setup 850 875

  18. Inbound order setup: the broker challenge • Typical non-broker situation: Trading partner identified in ISA is the company needing product • Broker situation: Trading partner identified in ISA is not the company needing product (customer)

  19. Inbound order setup: solution summary • Create SO for customer from EDI PO • Yet: indicate “broker order” • How: Use order salesperson field for broker

  20. STEP 1 Inbound order setup In MFG/PRO • In MFG/PRO Salesperson Maint. • Salesperson = broker • Indicate commission %

  21. STEP 2 Inbound order setup In MFG/PRO • In MFG/PRO Customer Address Maint. • Default salesperson = broker

  22. STEP 3 Softshare In EDI Translator Inbound order setup Create EDI translator map based on broker specs

  23. STEP 4 Inbound order setup In Ecomm. Module In the ECommerce Transformation Mapper, create the Order Transformation Map

  24. STEP 5 Inbound order setup In Ecomm. Module • Update transformation map to set customer ID equal to the order customer instead of Broker • This is done by: • Setup of a cross reference table • Translate to get customer’s EDI code • Map broker code Show me…

  25. STEP 5 a Inbound order setup In Ecomm. Module a) Setup cross reference of EDI Ship-To’s to their Customer EDI Code

  26. STEP 5 b Inbound order setup In Ecomm. Module • Translate the EDI Ship-to code (N1*ST 04) to update the customer EDI ID code (Hdr.TP EDI ID)

  27. STEP 5 c Inbound order setup In Ecomm. Module • Map broker code to order character field (Hdr.SOchar1) for reporting

  28. Outbound setup (PO Ack / Invoice) 855 810 880

  29. Outbound setup: the broker challenge • Typical non-broker situation: EDI transaction is sent to order/Invoice customer • Broker situation: EDI transaction must go to both customer & broker

  30. Softshare Outbound setup • Overview: Tasks to perform • Transformation mapping & setup in Ecommerce Module • EDI translator mapping

  31. STEP 1 Outbound setup In Ecomm. Module Create a customer transformation map for the Invoice & PO Ack.

  32. STEP 2 Outbound setup In Ecomm. Module • In Ecommerce Transformation Mapper: Set the Invoice salesperson 1 field to Header-Extended.MiscValue1 field

  33. STEP 3 In EDI Translator Outbound setup • In EDI translator: Using existing map for this customer: • Build a cross reference table from salesperson/broker code to the broker EDI ID • Check [Header-Extended.MiscValue1] field with this cross reference table. If found, run a “carbon copy” (cc) script cc script…

  34. STEP 4 In EDI Translator Outbound setup • Create a CC script which duplicates SNF file but changes customer ID to broker’s ID in 2nd file by passing these EDI ID’s and filenames to this script. • Unix Example: sed ’s/customer-ID/BrokerID/g’ cust.snf>broker.snf

  35. STEP 5 Softshare In EDI Translator Outbound setup • Create EDI translator 810/855 maps for the broker. The cc ‘d file will process with these maps.

  36. This is your seminar... Please ask questions !

  37. Part IIBuilding a warehouse:Goods & EDI flow

  38. Public Warehouse • Warehouse Logistics drive effective distribution • Manage with site inventory control in MFG/PRO • EDI, XML, & RFID

  39. Customer or broker sends 850 PO to supplier Warehouse Supplier QAD ERP Customer 850 PO 850

  40. Order is confirmed & 855 PO Ack sent back Warehouse Supplier QAD ERP Customer 855 PO Ack. 855

  41. Order is allocated (inventory assigned) & 940 is exported and sent to warehouse Warehouse Supplier QAD ERP Customer 940 Warehouse Shipping Order 940 - warehouse picklist - lists shipping info 940

  42. 940’s won’t export because: • Credit hold status is not blank • Order not confirmed • No allocated order lines • Not discrete (for scheduled orders) • Partial qty flag is no & order is not fully allocated • If all SO lines are memo only • User criteria not met (site code / due date etc. • Already updated with batch ID (already exported)

  43. From warehouse to customer (unless pickup arrangements) Warehouse Supplier QAD ERP Customer Goods shipped

  44. 945 sent from Warehouse to ERP system Warehouse Supplier QAD ERP Customer 945 Shipping Advice 945 -completed pick list - Receipts in the shipment information 945

  45. There are no backorders in the food & beverage So, 1 shipment per customer PO Did you know?

  46. 856 from warehouse or ERP’s EDI System Warehouse Supplier QAD ERP Customer 856 Advanced Ship Notice 856 -Sent by warehouse or ERP/EDI System (after 945) 856

  47. 810 or 880 sent from ERP / EDI System to Customer Warehouse Supplier QAD ERP Customer 810 / 880 Invoice 810 880 or

  48. Customer may send 820 to ERP/EDI system Warehouse Supplier QAD ERP Customer 820 Remittance Advice 820

  49. Customers not sending 820’s may instead mail a remittance list Like a check stub 820 associated with wire transfer, check, or movement of funds Ex. Lockbox info. from bank 820 : Did you know?

  50. Warehouse WH Ship Order (940) ASN (856) Goods ASN (856) PO(850)(875) Supplier QAD ERP Invoice (810)(880) Remit Advice(820) PO Ack (855) Customer Warehouse EDI/Ecommerce FlowReview WH Shipping Advice (945)

More Related