Subscribe to keep this site alive! Under new management but as always, still 100% FREE. Anyone with the IBM i is a friend of ours.
The Challenge: I am looking for an XSD file to load into the mapper that would be the xml representation of the x12 counterpart.
I need X12 204-Motor Carrier Load Tender, X12 210-Motor Carrier Freight Details and Invoice, X12 214-Shipment Status Message Transaction Set and X12 990-Response to a Load Tender for starters.
The Analysis: There is a software called EDI Notepad by Liason. You can get this for free for as long as you configure it as "Express". Open your sample: X12 204, X12 210, X12 214 and/or X12 990 using the EDI Notepad software.
When you move the cursor from one level to another, the panel on the right changes. The ISA and GS levels will always be shown in HTML.
But on the document Level, you can toggle the view by the dropdown. Choose Data(XML). Save the document as XML.
Here are the converted X12's to XML:
The Solution: The EDI Notepad gives everything as per standards.
Remove the <Interchange> and <FunctionalGroup> because routing is done differently for XML (cXML).
The next objective is to decide when to make the Element Name and/or Qualifier. Example:
for G62, the tag would simply be <Actual Pick Up Date>20110801</Actual Pick Up Date>
in the first N1 occurrence, the tag would be <Consignee Name>AA HARDWARE</Consignee Name>.
It is best to do the documents together so that you can plan the actions in #2. You might want to make <Transaction Set> variable. Hence, for a 210 it will be: <Transaction Set>210</Transaction Set>.
Do you have a new CHALLENGE? Let us know HERE.