Demo 3

Total of 6 videos on this page.

#1. Setup EDI input side using template

  • We setup EDI message on the input side using template
  • Template sets default DataPath property for the input file
  • This is good enough for basic execution of the map
  • But "Runtime Properties" are much more flexible way of setting up paths
  • We set input path and check EDI segments
  • One important property for EDI segments is StartTag. It is what EDI parser uses to extract segments from input files

#2. Setup XML output side using By-Example Wizard

  • We setup XML message on the output side using By-Example Wizard
  • We have sample input XML file. By-Example Wizard reads XML tags and creates initial map structure for us
  • Few modifications will be required to make XML output the way we want but that's a start
  • XML tags have StartTag properties setup based on sample input file

#3. Modify XML side

  • Our sample XML file did not have all the XML tags that might be present in outgoing XML file
  • We add additional XML tags to the output side using Add-Segment popup menu
  • We also create first mappings and test if output is produced

#4. Complete EDI to XML map

  • There is complete map. We mapped all required XML tags
  • We also added 'Empty (No Start Tag)' element that has empty StartTag
  • Elements with empty StartTag are not produced in the output. They are used to create XML looping based on specific requirements
  • Based on your requirements you may or may not need them
  • In this particular case we map element to ST element 1 on the input side. That way 'InventoryTransaction' XML tag repeats as many times as 'ST'
  • One way of thinking about it is that 'InventoryTransaction' is synchronized with 'ST' on the input side
  • This is basic way to guarantee certain ordering of output

#5. Additional tools to run translations

  • XTranslator Map Editor is translation development and testing tool
  • We also have tools for day-to-day processing
  • There is simpler map runner. It runs maps and does not allow accidental unintended modification of the map
  • There is also command line runner for semi-automated or automated processing
  • Set PATH environment variable in order to run translator command line tool from any directory on the computer
  • We recommend use of XT Server for even better automation
  • Please check documentation for more detailed use of these tools. Video only shows basic use case

#6. Update license key

  • Use XTranslator Map Editor to update license key
  • If you use XT Server or run maps via command line then license should be supplied directly in those tools

Bonus. Pro tips

  • If you have control over XML format design it to match EDI message. That way XML loops will match EDI loops and major 'looping issues' can be avoided
  • Most EDI formats only have 2 or 3 major loops. Something that can be called Header, Detail and Subdetail
  • Try to avoid creating lots of XML tags to represent EDI in your XML. Deep nested XML structures are hard to work with