Mapping Excersizes: EDI Invoice to Open Office Tables (part Three)
Finish The Paper Map
Today we will finish the three part series mapping exercise. If you haven’t gotten a chance to read the first two posts in this exercise you may want to start with them, or to review them before moving on to the conclusion. (read part One or read part Two)
In last post, we began mapping an EDI Invoice to invoice tables in an Open Office Database. I chose these as Open Office is free and anyone can get a copy to repeat this exercise, and because Invoices are common documents that need to be handled in an e-commerce and supply chain scenario. (more…)
Thursday, July 30th, 2009
When setting up a supply chain integration, there is a lot of information that is exchanged. One thing that should be explored is what the supplier will do if they can’t process the order. This should be explored by making a list of all the errors that you can conceive of. This is the beginning of your test plan. Then having the Vendor respond with what they will do. (this doesn’t have to be actual transfer of erroring files, it can just be filing out a form with what will happen when said error is sent. But of course, actually sending bad files to and from your test systems is a good idea when possible.) In the end you will have an idea of what will happen and what to expect when something goes wrong. However, sometimes this doesn’t cover all the bases.
To paraphrase a quote from Frank Herbert’s Dune, “The Data must flow.” And in the same sense that spice was the life blood of Arakis, the flow of data is the life blood of any e-commerce integration. In the past I have talked about how
Continuing Mapping Exercise
Today at Spend Matters, Jason Busch posted the first in a series of articles about the gap between finance, and procurement in today’s business; “
This is a mapping exercise that will go through the process of creating a paper map, or mapping document. We will start with an empty paper map that you can get
In the news,