Executing EDIIN

Execute Inbound EDI (ED502) is just one method of executing EDIIN. EDIIN could be executed from a command line, or as a system call, by executing:

  • <perldirectory>/perl $LAWDIR/logan/applicationproductline/edi/bin/ediin applicationproductline <process type> <carrier> (UNIX)

  • <perldirectory>\perl %LAWDIR%\applicationproductline\edi\bin\ediin applicationproductline <process type> <carrier> (Windows)

  • <perldirectory>/perl LAWDIR/applicationproductline/edi/bin/ediin applicationproductline <process type> <carrier> (System i)

Most healthcare users, however, will use Execute Inbound EDI (ED502) to run inbound EDI from the Lawson job scheduler.

An example of a command line might look similar to this:

/usr/bin/perl /apps/applicationproductline/edi/bin/ediin applicationproductline

Process type

These values are supported for the inbound process_type.

Value Function
recv_tran Retrieve data from specified carrier and translate
tran_only Translate EDI data already received to application format, no communications


For the tran_only option, this is the path/name of the EDI file you want to translate, NOT a carrier name.


EDIOUT will access the EDICONFIG table to find out hostnames and port numbers for connecting to the translation and communication servers.


The translation server executes whatever translation process is specified on the trading partner record under "map," passing the parameters that will be needed by the translation process. These include these parameters:

  • MAP

    The name of the map the translation process will use, for example, 72X_810_IN for laws_inb.


    Path/filename of file containing EDI data for one functional group.

    If an inbound functional group contains more than one type of transaction, the translation server will extract all sets of a type and execute the translation process for each type.


    Path/filename of a file containing one comma-delimited record with this data:

    • Lawson trading partner ID - (for example, LB for BURROWS)

    • EDI Number

    • ISA control number

    • GS control number


    Path/name of the file where the translation process should put valid application data.


    Path/name of the file where the translation process should put rejected EDI data.


    Path/filename where extracted data resides. The translation process can read and/or update this file. After the translation process completes, the translation server will update the EDSUBTBL database accordingly.

    After the translation process completes, the translation server will retrieve data from VALID_APPDATA, REJECT_NAME and EDSUBTBL and process it accordingly.

Process status and logs

This information is captured in the and tables. It will also be passed back to whatever process calls EDIIN, such as Execute Inbound EDI (ED502).