In inbound processing, the fully qualified path including the EDI input file name is the first required parameter passed to the ECRTP.
The input EDI file can be written to stdin, instead of to disk, using the -mi switch at runtime. (In ECMap, this information is entered in the Standard Input pane on the I/O Redirect tab of the Run Inbound Map screen.)
The input EDI file can be written to a specified memory address, instead of to disk, using the -mp switch at runtime. (In ECMap, this information is entered in the Internal Memory pane on the I/O Redirect tab of the Run Inbound Map screen.)
Using the trading partner and trade agreement mailbox switches, output EDI data can be routed to different locations:
If the trading partner mailbox is not ignored (-it switch is not set), inbound EDI data can be routed to the following mailboxes - IN (-ri switch), OUT (-ro switch), GOOD (-rg switch), BAD (-rb switch), or OTHER (-rt switch) - by passing in the appropriate Route EDI Type switch to the ECRTP. (The entry in the Route EDI Type textbox on the Option 1 tab of the Run Inbound Map screen.)
If the trading partner mailbox is not ignored (-it switch is not set) and either there is no trade agreement mailbox or a trade agreement mailbox exists and is ignored (-o switch is set), the inbound EDI data is routed to the IN mailbox of the trading partner directory when no Route EDI Type switch has been passed in to the ECRTP.
If the trading partner mailbox is ignored (-it switch is set) and either there is no trade agreement mailbox or a trade agreement mailbox exists and is ignored (-o switch is set), the inbound EDI data is not routed.
If the trade agreement mailbox is not ignored (the -o switch is not set), the EDI input is routed to the IN mailbox of the trade agreement mailbox if it exists, or to the IN mailbox of the trading partner mailbox if the trade agreement mailbox does not exist.
If the trading partner mailbox is ignored (-it switch is set) and the trade agreement mailbox is not ignored (-o switches is not set), the inbound EDI data is routed to the IN mailbox of the trade agreement mailbox if it exists, and not routed if the trade agreement mailbox does not exist.