What Components Should EDI Software Have?1834371

From Mu Origin Wiki
Jump to: navigation, search

Since EDI began to get popular it has been many years and throughout all this time, there were many EDI Software packages out there permitting companies to use EDI effortlessly.

In an EDI Software there are a couple of elements that are crucial to the success of the EDI Software solution in the organization. In this post I'll focus on some on the main components that each EDI software package must have in order to provide the user a positive experience and actually be used by company EDI Administrator or one of the company advanced user who is in charge of the EDI transactions, sending and getting and the whole procedure involved in it.

- Mapping - Translation - Validation - Import/Export - Reporting - Documents Turn About

EDI Mapping

When we talk about EDI Mapping we talk about pointing on different components in the EDI file as a source data and setting their corresponding location objects. Destination objects can be fields in a text file, columns in an Excel file or what ever file structure you choose to use.

EDI Translation

EDI Translation is the option to read one worth and set another worth as outcome of some translation setting we used throughout the software installation or later. For example a user can determine that every time that he see Qualifier ID 08 and then Qualifier value then he desires to set that Qualifier worth as DUNS number.

EDI Validation

EDI Validation is the process of making sure that all the data in the EDI file are correct, sitting in the suitable place, that mandatory components are not missing and that element that are from a list of feasible value for that specific dictionary id, are right.

The file in the right format and follow the guidelines of the EDI Version and regular.

EDI Import and EDI Export

EDI Import and EDI Export is the process of importing data from a text file/excel file or any other file format used by the organization into EDI file structure, export is the same but the other way about. This option is important in case the user require some interface with his/her ERP software an many of those ERP software packages have Import/Export routing, so in order to integrate between the two software packages, the user can import and export data in between the ERP and the EDI software packages.

EDI Reporting

EDI Reporting is the option to view reports on the transactions activity on a given time frame. That way an EDI Administrator can see how many EDI Transactions went via, how many of each document type, how many were with errors and more...

Each EDI software has its personal set of EDI Reports, but the primary point is that it has to give the EDI Administrator some tools to look at the EDI Activity in the organization so he can figure out on what type of action to take in different scenario, for example if he receive too many transactions with errors.

EDI Documents Turn About

EDI Documents Turn About is the part when user take an EDI document like Buy Order (850, 875) and creates an Invoice of it, saving the user time and typing errors.

replace edi