Run Inbound Map

To run an inbound map with incoming data, follow these steps:

Click the Run Map icon to open the Run Map module.
From the menu that is displayed, select Run Inbound Map. The Run Inbound Map window is opened with default showing the Required tab window.

In the Required tab window, insert the appropriate values as listed in this table:

Field	Description
Inbound EDI File	The path and file name of the EDI data file to be translated by the map. The full directory path, file name, and file extension are required. Use the Browse button for convenience to locate and insert the file.
Map Directory	The full directory path of the generated map file. Use the Browse button for convenience to locate and insert the directory where the map file is located. By default, the field is populated with the defined map directory listed under System module properties. The typical input is <drive>:\ECEDIGS\Map
Log Type	While the translator is processing, it will place information into a log file. Select the type of file the log will be written to. The choice of selection is (1) ODBC Log (written to the ODBC connection listed under the System module, ODBC tab, System Log), (2) Text Log (a text file), (3) Expanded Text Log (a text file) or (4) No Log (for a log not to be recorded).
Compliance Check	When checked, the translator will perform a compliance check. The map must be generated as a compliance map. Compliance checking is the comparison of EDI data being sent or received with the applicable EDI standard. The purpose of the map must be set as CMP within the Trade Status tab of the Trade Agreement window
PrintEDI	When checked, the translator will process the map as a print map. The purpose of the map must be set as PRT within the Trade Status tab of the Trade Agreement window
Non ODBC Trading Partner	This option is left blank by default. This means the user will be using an ODBC Trading Partner and will access the tables named as TP, TRADSTAT, and WIXSET. When checked, the user will be using a non-ODBC Trading Partner and will be using the tables named as customer.dbf and tradstat.dbf, as well as the flat-file wixset.dat
Trading Partner Directory	If not using an ODBC Trading Partner database and Non ODBC Trading Partner is checked, insert the directory path that contains the Trade Partner files
Store RunTimeTrade Partner Data	If not using an ODBC Trading Partner, this button allows the user the option to store the Trade Partner files in the Trading Partner directory above. The Trading Partner directory path is required
Retrieve RunTime Trade Partner Data	If not using an ODBC Trading Partner database to store your trading partner files, this button allows the user the option to retrieve trading partner files from the Trading Partner directory. The Trading Partner directory path is required

In the Option 1 tab window, insert the appropriate values as listed in this table:

Field	Description
All Trading Partner Default	When checked, the ALL trading partner and trade agreement will be utilized.
Ignore Trading Partner Mailbox	This check box should be checked because you are explicitly defining the file in the Inbound EDI File text box (Required tab).
ST03 (X12)	Enables the use of the Implementation Convention Reference. This is an optional element of X12 Standard beginning with version 4030.
Overwrite Output User Files	When this is checked, the output overwrites any existing user files. If this is not checked, the output is appended to any existing user files.
Ignore TradeStat Mailbox	This check box should be checked.
Validate Control Number Sequence	Tells ECRTP to check the received control numbers. This check confirms that the numbers have been incremented by one from the previous number received.
Trace Type	Short Trace, Long Trace, or No Trace.Long Trace provides a complete map trace. This is recommended for development. Once a mapping process has migrated to production, Short Trace should be selected. Short Trace only writes errors into the trace file. No Trace provides no diagnostic information from the map run
Route EDI Type	Options include No Routing, Route In, Route Out, Route Good, Route Bad, and Route Other. Routing allows you to pass the EDI transactions directly into the Trade Partner mailboxes without performing actual translation
Run Inbound Map	Enter the file name of the map here without the .map extension to run this specific map. Although you are still required to enter a Trading Partner Directory on the Required tab and Company Identification on this tab, neither trading partner or company information is referenced when the map is run. The system will automatically run this map and not do a trading partner lookup to find a map.
Company Identification	This item allows a specific company profile to be associated with this map. Enter a record number or browse the company ID table to select the record number for the company ID record for this run. Clicking the Browse button without specifying an Inbound EDI file (under the Required tab) will result in an error message, Inbound EDI File is required! Clicking the Browse button after specifying an Inbound EDI file will take the user to the Company Identification window.
Max Memory Cross Reference	The maximum allowable cross-reference table entries for memory lookups. If tables exceed the size of this parameter, then the table lookups will go to disk. The default size is 10,000 entries.
Number of Maps in Memory	Enter the number of maps in memory. The default value is 0. There is no fixed upper limit to this number
Create Batch File	An option to create a batch command file to automatically run with your switch and options settings. After specifying Inbound EDI and Company Identification file, a pop-up menu appears for Batch File Name. (This option is not normally used.)
Archive Trans Log	Clicking this button will take the user to the Archive window. From the Archive window, clicking the Browse button will take the user to the Select a Directory window. (This does not apply to the ODBC log.)
Delete Trans Log	Allows you to delete the transaction log. (This does not apply to the ODBC log.)

In the Option 2 tab window, insert the appropriate values as listed in this table

Field	Description
Zero Fill EDI Non-Null Numbers	Zero-fill inbound numeric elements that are not blank. (-z switch in a batch file).
Output the Elapsed Time	The check box is blank by default. Outputs the elapsed time of the run into a trace file. (Usually used with short trace.).
Create Bad Transaction Log	Creates a Bad Transaction log that contains incoming transactions that cannot be processed. (Utilized with compliance maps.).
Trading Partner Search Option	How the EC Gateway looks up Trade Partner data. The following are options for this field: Group Sender – default – routing to mailboxes based on the department-level sender’s identification Group Receiver – routing to mailboxes based on the department-level receiver’s identification Group Sender and Receiver – routing to mailboxes based on the department-level sender and receiver’s identification Full Interchange – Sender – map selection and routing to mailboxes based on the company and department-level sender’s identificationFull Interchange – Sender and Receiver – map selection and routing to mailboxes based on the company and . department-level sender and receiver’s identification Full Interchange – Receiver - map selection and routing to mailboxes based on the company and department-level receiver’s identification Outer Interchange – Sender Only – map selection and routing to mailboxes based on the company-level sender’s identification. Outer Envelope – Receiver – map selection and routing to mailboxes based on the company-level receiver’s identification Outer Envelope – Sender/Receiver – map selection and routing to mailboxes based on the company-level identification for sender and receiver Reverse – Outer Envelope – Sender/Receiver – compliance checking of outbound EDI using sending and receiving company-level identification for map selection Reverse – Full Interchange – Sender/Receiver - compliance checking of outbound EDI using sending and receiving company and department-level identification for map selection Reverse – Receiver Against Main – compliance checking of outbound EDI using company-level receiver’s identification for map selection Reverse – Outer Sender Against Override – compliance checking of outbound EDI using company-level sender’s identification for map selection Reverse – All Sender Against Override – compliance checking of outbound EDI using company-level and department-level sender’s identification for map selectionReverse – All Receiver Against Main – compliance checking of outbound EDI using company-level and department-level receiver’s identification for map selection
Substitute Output Filename	Overrides the name of the output application file. This should not be used if you are creating multiple output files.
Substitute User File Directory	Changes the name and location of the user file directory. This overrides the location of the output files. This option may be used for creating multiple output files.
Substitute Map and TP Directory	Changes the names and location of the map and the Trading Partner directory. This provides a single location for the trading partner files and map files and overwrites the map and trading partner directories specified on the Required tab
Temporary Files Directory	This is the directory where temporary files are placed by ECRTP. The default is the root directory of the drive where ECRTP is located. The user should have file write access to the root directory. This allows you to specify the location of the temporary split files that are created when the Multiple Files option is selected.
Start Processsing at Byte Count	Begins processing the incoming file at a specific character (byte).
End Processsing at Byte Count	Ends processing the incoming file at a specific character (byte)..

(Optional) Select File Alias tab.

The alias allows the user to change directories and file names. This allows the user to adapt the map between machines and different platforms without recompiling the map.

Field	Description
Source (Files inside Map)	File name and location that is called from the map. Clicking the Add button will cause a window to appear. The user can then select the desired file. The Edit and Delete buttons are available once a source has been chosen. If the Edit button is chosen, a window appears with the field already populated. Clicking the Delete button will delete the highlighted file. The arrow button displays a window allowing the choice of a file. This defines the entry placed in the destination panel.
Destination (Files during Run Time)	File name and location of the file that will be used by the map at runtime. An Edit button is available if a source file has been added to the destination panel. When the Edit button is clicked, a window opens.

Field

Description

Source (Files inside Map)

File name and location that is called from the map. Clicking the Add button will cause a window to appear. The user can then select the desired file. The Edit and Delete buttons are available once a source has been chosen. If the Edit button is chosen, a window appears with the field already populated. Clicking the Delete button will delete the highlighted file. The arrow button displays a window allowing the choice of a file. This defines the entry placed in the destination panel.

Destination (Files during Run Time)

File name and location of the file that will be used by the map at runtime. An Edit button is available if a source file has been added to the destination panel. When the Edit button is clicked, a window opens.

(Optional) Select ODBC Alias tab.

The alias allows the user to change directories and file names. This allows the user to adapt the map between machines and different platforms without recompiling the map.

Field	Description
Source (ODBC Connection Strings inside Map)	Connection string that will be used by the map at runtime. Clicking the Add button will cause a window to open. Enter a string in the text box. If the Edit button is chosen, a window displays with the field already populated. Click the Delete button to delete the highlighted string. The arrow button displays a window allowing entry of a string. This defines the entry placed in the destination panel.
Destination (ODBC Connection Strings during Run Time)	Destination string that was called from the map. An Edit button is available if a destination string has been added to the destination panel. When the Edit button is clicked, a window opens. The field is populated with a current string from the destination panel..

Field

Description

Source (ODBC Connection Strings inside Map)

Connection string that will be used by the map at runtime. Clicking the Add button will cause a window to open. Enter a string in the text box. If the Edit button is chosen, a window displays with the field already populated. Click the Delete button to delete the highlighted string. The arrow button displays a window allowing entry of a string. This defines the entry placed in the destination panel.

Destination (ODBC Connection Strings during Run Time)

Destination string that was called from the map. An Edit button is available if a destination string has been added to the destination panel. When the Edit button is clicked, a window opens. The field is populated with a current string from the destination panel..

(Optional) Select Parameters tab.

Field	Description
Parameter Names	Select the name of the parameter that is to be passed to ECRTP. Clicking the arrow button will cause a window to open. Enter a parameter value. This defines the entry placed in the destination panel.
Parameter Values Passed at Run Time	The value of the parameter that is to be passed to ECRTP. An Edit button is available if the destination panel has been populated with one or more strings. When the Edit button is clicked, a window opens. The user can enter a new value for the parameter. The Delete button can be used to delete a selected parameter value.