The following NCPDPv5.1 to Proprietary Format DataStage/Mercator Map's Content
was created by Steven C. Howes/© Howes-IT-Going 2004-2012
The NCPDPv5.1 Type Tree was created from the National Council for
Prescription Drug Programs Telecommunication Standard Specs ver 5.1
The Proprietary PropInbound Type Tree is fictitious in nature.
The ncpdp51_test_in and ncpdp51_test_out files contain bogus information.
I created a Claims Request NCPDPv5.1 To Proprietary Map Example for you.
It’s name is ClaimNCPDP51To51Prop. To keep a standard for naming conventions I created a folder with the same naming conventions for the map and it is in the following Directory: C:\Mercator6.5\ClaimNCPDP51To51Prop\ .
Notice that all of the files that are needed for this Mercator 6.5 Map are in this one directory. This makes it easier to document and follow as a learning tool.
The NCPDPv51.mtt is the Input File Mercator Type Tree
The PropInbound.mtt is the Output File Mercator Type Tree
The .mms is the Mercator Map Source Code
The .mmc is the Mercator Map Compiled EXE
The .mtr is the Mercator Runtime Trace File
The .mme is the Mercator Map Error File
Input File that should match the NCPDPv51.mtt layout
Output File that should match the PropInbound.mtt layout
Input and Output files should always be edited with a Hex Text Editor like
Friendly Hex Editor. You can get a shareware copy of this HexEditor.
When working with the .mtt Mercator Type Trees – You access them by running the Mercator Software Type Designer. Be aware that there are big differences between Version 5.0 & 6.5 in the .mtt Type Trees (and .mms Map Source files) and you can’t open/edit a 6.5 Type Tree in the 5.0 Software. Just know that the Mercator 6.5 software is not reverse compatible with 5.0 Software.
If you make any changes to either an Input or Output Type Tree – You MUST ANALYZE the Type Tree and then save the current changes in order for the changes to be accepted by the .mms Mercator Map Source file. (You’ll be prompted by the Map Designer that there were Type Tree Changes made.) If there are errors in the Type Tree Analyze of either the Logic or Structure – You will have to correct those errors and then Analyze the Type Tree Again until there are no errors. Some Warnings are acceptable if they aren’t catastrophic and don’t cause major problems in Building the Map.
The Type Trees used in this map example are a little complicated… I don’t suggest that you make any changes to either the .mms or .mmt files unless you make a backup copy of everything first… It’s really easy to mess up a map by making a minor change to either the input or the output Type Trees.
Notice that the Main Map Name is ClaimNCPDP51To51Prop – that’s the same as Project Folder Name, Compiled Map Name .mmc, .mme, .mms. All of the F_* and other map names are Functional Maps(which are different levels of processing for fields that are repeating or special). Mercator uses these functional maps for separating Header and Detail Records Processing this way…
Highlight a specific object and then right click to either see properties or to edit specific objects. Anywhere that you see a “+” sign means that there are objects and records under that object or record.
The Main Map ClaimNCPDP51ToProp has an Input and Output card(so do all of the other Functional Maps)… Notice that the Type Tree is Referenced with a CardName, Type Tree and Type along with the FilePath name. The Input File Type Tree is the NCPDPv5.1 – NCPDPv51.mtt. I used the naming conventions “ncpdp51_test_in” for the Input File Card so that it wouldn’t be confusing. This is the only card that you would change the input file name if you wanted to map a different map.
The Main Map ClaimNCPDPToProp has an Input and Output card(so do all of the other Functional Maps)… Notice that the Type Tree is Referenced with a CardName, Type Tree and Type along with the FilePath name. The Output File Type Tree is the Proprietary – PropInbound.mtt. I used the naming conventions “ncpdp51_test_out” for the Output File Card so that it wouldn’t be confusing. This is the only card that you would change the output file name if you wanted to map a different file.
If the map build is successful you’ll get a quick completion message. If there were errors encountered you will have to look at the .mme file and figure out what error was encountered while building the compiled map. You can look at the .mme file with Wordpad.
If any errors were encountered during the run of the map – you will have to look at the .mtr run trace file and see what is causing an error. You can look at the .mtr file with Wordpad or Notepad or any text editor.