Photo appears courtesy of R/DV/RS. This blog was written by Kristen Kearns, Aurora's EDI Manager. Ping! You hear your email and there’s another one of those “New Requirements” emails from one of your trading partners, Perfection Construction. Yeah, yeah, I’ll look at it later. You never get to it because you have Evan in Sales breathing down your neck about getting ABC Company up and running for EDI ASAP so they can place orders. Wait a minute! Did Evan put you in contact with ABC Company’s EDI department to get the specs? Do we even know if we can do all of their documents and if we can meet their requirements? Here comes Mary Jane from Accounts Receivable– what does she want? She needs you to research Best Hardware as they are not paying their invoices. Let me work on that now before the CFO starts yelling about lack of payments.
This week's blog was written by Art Douglas.
This blog was written by Kristen Kearns, Aurora's EDI Manager. You might think this blog is a stretch – how can EDI, a very technical concept, be anything like Community Theatre, a very arts-based activity? I’m going to tell you how.
Photo appears courtesy of Wendy. This week's blog was written by Karen Blood from Aurora EDI Alliance partner, GraceBlood LLC out of Baltimore, MD. Amazon recently announced a new type of chargeback that will initially impact Hardlines’ Vendor Central suppliers. While this might not seem to apply to you or your other trading relationships today, Amazon more and more (like Walmart in the past) is a bellwether when it comes to making demands on suppliers. The never ceasing effort to bring customers robust selection at competitive prices in a hurry puts the responsibility squarely on distributors and manufacturers to fill orders and maintain proper levels of inventory to support demand.
Photo appears courtesy of Phill Dolby. I spend a lot of time each summer trying to streamline and automate as many of our processes and procedures as I can. It saves time and, if done correctly, makes our data more accurate and timely. I feel taking the time to do this is well worth the effort and it makes us more profitable in the long run as it frees me up to do other things.
Picture appears courtesy of mjaaaae. This week's blog was written by Michael Barnhouse of McAna EDI, an Aurora EDI Alliance parnter. Companies of all sizes are engaged in a renewed commitment to further improve their supply chain in the effort to deliver the highly elusive perfect order. An order that arrives on time, is complete, in full compliance with all vendor rules and covenants, damage free, with accurate shipment notification and invoicing.
I started my journey with EDI (electronic data interchange) 27 years ago working on Telex machines, yes the things of ticker tape parades. My assignment, through a relation with Western Union, was to connect pre-internet, pre-eMail, and even pre-FAX computers, still relatively uncommon compared to today, to the Telex network. The end game was to allow companies to send domestic and international registered messages easily, without using the cumbersome, slow and heavy ticker tape driven iron Telex machines.
Photo appears courtesy of Nikki Tysoe. This blog was written by Kristen Kearns, Manager of EDI Services for Aurora Technologies. EDI Documentation - the one thing we love to hate, but MUST do. How do you run the inbound 850 process once the data is mapped? What are common issues that prevent 850s from automatically creating orders? What do you do if an 810 fails? What if an 856 fails?
This week's blog was written by a member of our amazing tech support team, David Aird. SDQ (Ship Destination Quantity) purchase orders are also referred to as spreadsheet or explosion orders. These types of EDI orders can create efficiency gains by eliminating redundant data that would need to be sent on multiple non-SDQ orders. This reduction of data is accomplished by sending the header data only once as opposed to sending it multiple times on multiple orders. SDQ orders also need a way to send multiple locations for the items being ordered. This is where the SDQ segment comes into play. The SDQ segment is essentially a set of grouped fields that contain a location number and an order quantity for that location. This allows one SDQ order to potentially be expanded into multiple orders.