Enter the following on the Required tab of the Build Acknowledgement window:
Map Name – the name of the 997 map being run. ECMap includes four different 997 maps on the installation CD. If you used the default installation directory, these maps are located in c:\Program Files\Sybase\ECMap. The names of the four maps are listed below, with a brief description of when you use each map:
997ODBCT – Run this map when you are using an ODBC-compliant log database and want to lookup on a specific trading partner
997ODBCA – Run this map when you are using an ODBC-compliant log database and want to lookup on the ALL Trade Partner
997XLGTP – Run this map when you are using an expanded text log file and want to lookup on a specific trading partner
997XLGA – Run this map when you are using an expanded text log file and want to lookup on the ALL Trade Partner
Transaction Name – 997, and the Code is FA (Functional Acknowledgement). The program automatically enters this information.
Output EDI File – the full path file name of the Functional Acknowledgement that is created by the 997 map. Rather than using routing, you would generally specifically choose the destination folder for your Functional Acknowledgement and enter it in this text box. You can enter the full path or Browse for it.
Map Directory – the full path name of the directory containing the 997 map you are running. If you used the default directory when you installed the maps, the entry in this text box is c:\Program Files\Sybase\ECMap. Otherwise, it is the directory structure that you chose and set up. You can Browse for this.
Functional Acknowledgement – while the program is creating this, it places information into a log file. You have three choices for Log Type – Text Log, No Log or Expanded Text Log. For Functional Acknowledgements, Text Log, is generally used during development. (See ECRTP Reference Guide for formats of these log files.)
Non-ODBC Trading Partner – select to run the RTP against a dBase III trading partner file. You must click this button if you didn't set up an ODBC-compliant trading partner database, but you may also click it if you set up an ODBC database, but prefer to run the RTP against a dBase III file. Users sometimes choose the latter option because the RTP runs faster with the dBase III file and is portable to other platforms that do not support ODBC drivers.
Trading Partner Directory – enter if you selected Non-ODBC Trading Partner. This is the same directory that you used in the inbound map that created the input to this 997 map. This directory contains your dBase III trading partner (customer.dbf) and trade agreement (tradstat.dbf) files. You can enter the directory path or Browse for it.
RTP – if you run this against an ODBC-compliant trading partner database, enter the DSN for that database in the Trading Partner Connection text box. This is the same DSN that you used in the inbound map that created the input to this 997 map. (This option is not available if you selected Non ODBC Trading Partner.) You can enter the DSN or Browse for it.
Log Connection text box – not active for Functional Acknowledgements.
