Make sure you have exported the sample data files.
Use the Enterprise Designer’s Export feature to export the sample data files to a specified location, for example:
cd /d C:\temp\eXchange\Sample\HIPAA\Data\Atlanta |
Change directories to the subdirectory of the location where you exported the sample data files.
Use a text editor open the following file:
270-SendingOutbound.dat.~in
You see text that resembles the following text:
<?xml version="1.0" encoding="UTF-8"?> <!--Sample XML file generated by XMLSPY v2004 rel. 3 U (http://www.xmlspy.com)--><TestInput xmlns:xsi= "http://www.w3.org/2001/XMLSchema-instance" xsi: noNamespaceSchemaLocation="C:\HIPAASample\xsd\ServiceInput.xsd"> <dir>path</dir> <filename>270.dat</filename> <tradingPartner>Berlin</tradingPartner> <service>Eligibility_AG_Profile</service> <action>270</action> <createnumberofmsgs>1</createnumberofmsgs> </TestInput> |
The lines preceding the last line </TestInput> have the following meaning:
The <dir>…</dir> line supplies the path of the directory that holds the payload data file to be processed.
The <filename>…</filename> line supplies the file name of the payload data file for the current transaction.
The <tradingpartner>…</tradingpartner> line supplies the name of the current TP.
The <service>…</service> line supplies the name of the Transaction Profile Group of the current TP; used in ePM.
The <action>…</action> line supplies the transaction number, in this case, 270.
The <createnumberofmsgs>…</ createnumberofmsgs> line supplies the number of messages to be created, in this case, one.
If necessary, in the line <dir>path</dir> (shown in the previous example), change the string represented by <path>, to the actual path of the directory that holds your local copy of the 270.dat file.
For example:
<dir>C:\temp\eXchange\Sample\HIPAA\Data\Atlanta</dir> |
Or:
<dir>/~myname/eXchange/Sample/HIPAA/Data/Atlanta</dir> |
If you have already run the sample and you want to experiment with other changes (such as using a payload file with a different file name, or using a TP with a different name), be sure they are also reflected here.
When you are finished, save your changes and exit the text editor.
You must make sure that the Berlin HIPAA_dlg_270_In_Atlanta_270_In.xml file is updated to reflect the appropriate Berlin data path location. You may do this operation using a text editor.