Demo 5

3 videos

#1. Quick example of database to EDI X12 837 map

  • This is full example of another map that produces EDI 837
  • We setup input via two database queries: Header and Claim
  • Tables are linked via master-detail relationship (this is covered in Demo2)
  • Map is almost done. We add "DTP Admission Date/Hour" to it using Copy and Paste
  • This is common practice - adding and modifying segments to match specific trading partner requirements

#2. Quick example of CSV to EDI X12 270 map

  • This is full example of the map that produces EDI 270
  • Our input is CSV file. We imported field names using By-Example Wizard
  • Header segment has been added to the map to filter CSV line with field names since we do not want field names in actual outgoing X12 270
  • Map is done. We inspect and run it
  • EDI 270 template has been modified to match specific trading partner requirements

#3. Quick review of important EDI to database mapping property

  • FieldType set to PrimaryKey drives INSERT. Once next value comes into field set as PrimaryKey whatever values came so far get inserted into the database table
  • In the map FieldType set to PrimaryKey does not always match to actual database primary key field
  • PrimaryKey should be set on only one field in the output side per table
  • If you do not get enough or too many records inserted into the table, move FieldType setting of PrimaryKey to another field in that table
  • Most other fields should be set to Nullable. There are more FieldType options. Please consult PDF Manual

Bonus. Pro tips

  • If your trading partners have major format differences for specific EDI message create single map template. Then copy it and modify for each partner
  • Save backup copies of the mapping file as you map. If something goes wrong you can go back to last known working state
  • Map by moving in small increments: make a change, run map to see that it still works, check data in Data tab or check output file, repeat...