Generated map files

During map development, the program places map files in a <project name>/<map name> directory structure. When the map files are transferred to the production server, this same directory structure can be kept or the user can specify a different location. The program uses the fully qualified path to the generated map file as part of a required runtime parameter/ switch for inbound and outbound processing. The ECRTP uses this information to dynamically switch maps at runtime, based on the trading partner search option specified by the user at runtime.

Non-ODBC users have two trading partner lookup options:

Table 1-1: Non-ODBC trading partner search criteria and parameters

Trading partner search criteria

Switch/parameter

group sender

default

reverse - group receiver

-er

ODBC users have fifteen trading partner lookup options:

Table 1-2: ODBC trading partner search criteria and parameters

Trading partner search criteria

Switch/parameter

group sender

default

interchange sender

-e5

group and interchange sender

-e2

interchange receiver

-e6

group and interchange receiver

-e4

group sender and receiver

-e1

interchange sender and receiver

-e7

group and interchange sender and receiver

-e3

reverse - group receiver code

-er

reverse - interchange receiver

-e10

reverse - group and interchange receiver

-e13

reverse - interchange sender

-e11

reverse - group and interchange sender

-e12

reverse - interchange sender and receiver

-e8

reverse - group and interchange sender and receiver

-e9