If the conversion is from an EDI or flat file to an XML message, you can choose to use either one of the two engines. The criteria to determine which engine to use is based on the layout of the output file. If the data sequence order of the output file is identical to that of the input file, you can use the AnyToXML Converter Engine. However, if the data sequence order is different, i.e,. the data in the input file will be manipulated, mapped, reformulated, or rearranged in the output file, you will need to use the AnyToAny engine. Another difference between the two engines is that the Redix AnyToXML Format Converter Engines does not need an OFD file, whereas the Redix AnyToAny XML Converter Engine requires one.

Yes, the Redix AnyToXML Format Converter Engine supports all X12 transactions in version 3040, 4010, 4020, 4030, 5010, 5020, 5030, 5040, and 5050.

If the conversion is from an EDI or flat file to an XML message, you can choose to use either one of the two engines. The criteria to determine which engine to use is based on the layout of the output file. If the data sequence order of the output file is identical to that of the input file, you can use the AnyToXML Converter Engine. However, if the data sequence order is different, i.e,. the data in the input file will be manipulated, mapped, reformulated, or rearranged in the output file, you will need to use the AnyToAny engine. Another difference between the two engines is that the Redix AnyToXML Format Converter Engines does not need an OFD file, whereas the Redix AnyToAny XML Converter Engine requires one.

Users can define the XML tag style using one of the following styles:

• Full Description (e.g.. <PurchaseOrderDate>)
• Record/Segment Name with Sequence Number (e.g., <BEG_05>)
• Record/Segment Name with Element Number (e.g., <BEG_373>)
• RosettaNet
• Microsoft BizTalk