Sybase ECMap NSF1.03 To NSF3.01 Any2Any EDI Mapping Example

I have had several successful contract engagements(over the years) that have required writing applications and using various Electronic Data Interchange (EDI) software packages. One of the premier EDI packages that I've used has been PaperFree Systems WinMap and ECMap. This software package has changed owners a few times: Neon Soft Inc. and now Sybase Inc.

The ECMap has had a HIPAA Compliant Tool since 1998 and is excellent for creating X12 837 Transaction Set Maps. The example NSF version 1.03 To NSF version 3.01 EDI Map was created for EDS and Medicaid of Colorado to convert NSF ver 1.03 HCFA 1500 and UB 92 Health Insurance Claims data 837 X12 to NSF ver 3.01. The Business Rules for Field to Field EDI Mapping were created in a spreadsheet NSF v103 to NSF v301.xls.

For the sake of this example I created a D:\ ECMAP_EXAMPLE \ NSF103 folder. The X12 837 test data content is fictitious in nature. As always, I can provide copies of the source code NSF103.map file, Microsoft Access 2000 database tables, nsfv103 and nsfv301 records layouts.

Step 1: D:\ ECMAP_EXAMPLE \ NSF103 folder.

Notice below, that I created D:\ ECMAP_EXAMPLE \ NSF103 folder. This will be the directory referenced in the ECMAP Project and Map Objects and will hold the Proprietary ECMAP Access Databases and Tables.

Created D:\ ECMAP_EXAMPLE \ NSF103 folder.  This will be the directory referenced in the ECMAP Project and Map Objects and will hold the Proprietary ECMAP Access Databases and Tables.

Step 2: Run ECMap Software and Create a Project and Map.

Run ECMap Software to navigate through application.

ECMap Project NSF103.

ECMap Project NSF103 Properties.

project.txt

ECMap Project NSF103 Map NSF103.

ECMap Project NSF103 Map NSF103 Properties.

ECMap Project NSF103 Map NSF103 Properties.

Step 3: Run ECMap Software and Create Project/Map/Directory.

ECMap Project NSF103 Map NSF103 Directory.

Step 4: Run ECMap Software and Create Project/Map/Directory/Files/Databases.

ECMap Project NSF103 Map NSF103 Files/Databases.

Step 5: Run ECMap Software and Create Project/Map/Directory/Files/Databases/Records.

ECMap Project NSF103 Map NSF103 Records.

recsum.txt

Step 6: Run ECMap Software and Create Project/Map Memory Variables.

ECMap Project NSF103 Map NSF103  Memory Variables.

memvar.txt

Step 7: Run ECMap Software and Create Project/Map Input Output Rule Definitions.

ECMap Project NSF103 Map NSF103  Input Output Rule Definitions.

rulelist.txt, ruletext.txt

Step 8: Run ECMap Software and Create Project/Map Any2Any Mapping Definitions.

ECMap Project NSF103 Map NSF103  Any2Any Mapping Definitions.

Step 9: Run ECMap Software and Create Project/Map Any2Any Map Flow Definitions.

ECMap Project NSF103 Map NSF103  Any2Any Map Flow Definitions.

outflow.txt, outlevel.txt

Step 10: Run ECMap Software and Create Project/Map Any2Any Map Cross Reference Tables.

ECMap Project NSF103 Map NSF103  Any2Any Map Cross Reference Tables.

Step 11: Run ECMap Software and Copy Map Function.

ECMap Project NSF103 Map NSF103  Any2Any Copy Map Function.

Step 12: Run ECMap Software and Run Generate Map Function.

ECMap Project NSF103 Map NSF103  Generate Map Function.

View 9 Warnings. All Warnings Should Be Corrected via NSF103_Generate_Map_Log.txt.

Step 13: Run ECMap Software and Run Map Function.

ECMap Project NSF103 Map NSF103 Run Map Function.

Step 14: Run ECMap Software and Run Map Reports Functions.

You can Export Reports to *.html, *.rtf, *.txt, *.xls and *.xml file types. I exported the NSF103 Map Example Reports to the following *.txt files.

project.txt, memvar.txt, outflow.txt, outlevel.txt, recsum.txt, rflowout.txt, rulelist.txt, ruletext.txt, sysvar.txt, userlist.txt.

Go Back to:
http://Howes-IT-Going.com

This Webpage and Contents Created by Steven C. Howes © Howes-IT-Going 2003-2012 All rights reserved.

Steven C. Howes and Howes-IT-Going are NOT Responsible for Usage or Reproduction.
This Web Page, ECMap Microsoft Access Databases and Microsoft Excel Spreadsheet were for Educational and Discussion Purposes ONLY. Terms of use.