In EDI Expert Video Series 3.0, IDEA's B2B EDI Solutions Manager Tom Guzik continues to explore the ins and outs of EDI. Intended as a guide to small IT teams making big decisions and changes, this series answers the questions about various aspects of EDI implementation, integration, and maintenance. In this episode, we analyze when to code company business rules into an EDI map, and when to have the company ERP system deploy the rules.
Q: When does it make sense to code company business rules into an EDI map versus having the company ERP system deploy the rules?
A: The first thought that comes to my mind is that it never makes sense. However, I know that in the real world there are examples of when this does happen. The reason I say it doesn’t make sense to use mapping to do your business rules is because you’re basically taking on somewhat of a legal responsibility by putting those rules in your map. And then any time some of those rules may change, or you may need to actually add additional fields or cross references, you’d have to take the map out of production, modify it, save it, and make sure that the map still works. But if your system doesn’t readily facilitate the handling of these business rules or cross reference tables, then I could see why it might make sense to add that into the map. But, as a general rule of thumb, the more you can do in your ERP system for supporting and enforcing your business rules, the better off you are, the less tinkering you’ll have to do on maps, and the less likely you are to go over and impact another one of your trading partners by adding a change to a map that is being used for multiple partners.