Subject:Intended Use of a .sef File Author:Ronald Reiner Date:20 Jun 2013 03:55 PM
I have a quick question regarding the desired programmatic use of .sef files...
Are they designed to be created once for a given set of inputs (EDI Dialect/Version/Document) and then used to convert every document to XML that meets those criteria or are they to be created anew every time we receive those documents?
For example we received many EDI X12/Version 4010/EDI 850 documents which must be converted to XML. Can every document be processed against one .sef detailing the conversion of an 850 document or do we have to create a .sef file every time we receive an 850 document to convert it properly?
Subject:Intended Use of a .sef File Author:Ivan Pedruzzi Date:21 Jun 2013 11:44 AM
Typically you have a SEF file per type of transaction, for example one for all your 850. Notice also that the SEF file is required only if the the messages you have to process do not follow the standard.
If that't not the case, you just need to configure the appropriate converter URL parameters and you are ready to go.
Have a look at the XML Converters User's Guide for more information