EDI X12 Standard Rules Breakage Examples and Corresponded Failures
EDI X12 standard rules and guidelines are quite strict and that is why they are not always compliant with real-world implementations.
Despite EDI X12 standard implementation scenarios subject to the set package of indications, some parties consider them too complicated and try to break them. Due to such rules breakage they can experience failures that not always can be fixed. Today we will give you some examples of EDI X12 standard rules breakage, failures and imperfections.
Not all of the listed examples mean rules breakage, however they can negatively influence EDI operation.
- The incoming EDI file is broken in lines of 80 characters. This can be fixed by removing carriage return and line feed. This should be done before data is downloaded into translator.
- EDI files sizes – no predefined limits. Usually EDI file sizes vary from 5Kbt to 5Mbt. If you send 1Gbt document, you are not breaking standard rules. However, the process will be very slow. Sending multiple smaller documents will make the process faster. Also, when such situation occurs in some software packages, the system will be run out of memory and will take it from other processes. This will negatively influence the operation of programs in general.
- Segments ISA, GS, ST, SE, GE, IEA are obligatory to use. Some companies develop EDI documentation for trading partners without mentioning these segments (they consider that they are assumed by everyone and do not have to be mentioned). However, the listed segments may not be used only within the bound of company internal turnaround. In partnership with other parties, segments ISA, GS, ST, SE, GE, IEA must be mandatory because partner systems will process the file mentioning these segments. Many software packages will not be able to work with files that lack these segments. In this case EDI data will be considered invalid.
Successful EDI implementation requires from you to learn EDI X12 standard rules and trading partner guidelines before testing. Only after all rules and requirements are carefully studied you can rely on smooth tests and easy production.