Ok, I work at a small company who has recently been asked to implement EDI to receive and confirm orders for 1 customer for 2 documents.
Background:
We package and distribute salsa/sauces etc..
We have a basic homebrew WMS/ERP system and our customers send us a order in .csv file with formats we set up based on their needs. They e-mail us the orders, our system slurps them in from e-mail, processes them, and return mails a confirmation .csv from the info (ie 2 bottles shipped on X date via ups etc...)
Now as I understand it EDI is the exact same process, but with a different framework (ie Standards between businesses security, VANs etc..)
So lets say I get an edi document (we'll use 940's and 945's as examples. And I'm a moderately intelligent guy so I look at the map and think, (And here's where you can set me right)
I think ,..Heck. I can script the import of this file, pull the values from the fields, dump them into a .csv and have them dropped into my system like normal. (basically write some batches to pull and ignore varialbles from the EDI 940 document. Then do the exact opposite with my confirms.
What is the value,..underlying story etc.. of EDI that I'm not getting here? Why don't I just SCP files back and forth with all my buyers/sellers based on a published file format standard??
I mean if I was dealing with thousands of clients, I can see where the standards would come in handy (though from what I understand *everyone* uses completely different pieces of those standards) but all this mapping, and translating etc.. seems both painstaking, expensive, and redundant.
But again,..this is a whole new world to me so, clue me in ok?
Background:
We package and distribute salsa/sauces etc..
We have a basic homebrew WMS/ERP system and our customers send us a order in .csv file with formats we set up based on their needs. They e-mail us the orders, our system slurps them in from e-mail, processes them, and return mails a confirmation .csv from the info (ie 2 bottles shipped on X date via ups etc...)
Now as I understand it EDI is the exact same process, but with a different framework (ie Standards between businesses security, VANs etc..)
So lets say I get an edi document (we'll use 940's and 945's as examples. And I'm a moderately intelligent guy so I look at the map and think, (And here's where you can set me right)
I think ,..Heck. I can script the import of this file, pull the values from the fields, dump them into a .csv and have them dropped into my system like normal. (basically write some batches to pull and ignore varialbles from the EDI 940 document. Then do the exact opposite with my confirms.
What is the value,..underlying story etc.. of EDI that I'm not getting here? Why don't I just SCP files back and forth with all my buyers/sellers based on a published file format standard??
I mean if I was dealing with thousands of clients, I can see where the standards would come in handy (though from what I understand *everyone* uses completely different pieces of those standards) but all this mapping, and translating etc.. seems both painstaking, expensive, and redundant.
But again,..this is a whole new world to me so, clue me in ok?