Executing EDIOUT

EDIOUT can be executed from the command line or as a system call, by executing:

  • <perldirectory> / perl $LAWDIR/applicationproductline/edi/bin/ediout/applicationproductline <process type> <application file path/name> <edi number> <starting location,length> (UNIX)

  • <perldirectory> \ perl %LAWDIR%\applicationproductline\edi\bin\ediout applicationproductline <process type> <application file path/name> <edi number> <starting location,length> (Windows)

  • <perldirectory> / perl LAWDIR/applicationproductline/edi/bin/ediout applicationproductline <process type> <application file path/name> <edi number> <starting location,length> (System i)

The position and length numbers for EDI NUMBER are 32, 15.

Most healthcare users, however, will use ED501 to run outbound EDI from the Lawson job scheduler.

Process type

These values are supported for outbound process_type:

Value Function
tran_send Translate application data to EDI and transmit.
tran_only Translate application data to EDI but do not transmit - instead write EDI data to a temp file. This option would most often be used for testing.
send_only Transmit a file already in EDI format. This option would be used most often for re-transmission after a communications session has failed.

App file/path name

If send_only option, this is the path/name of the EDI file you want to transmit, NOT an application file.

EDICONFIG table

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

Translation

The translation server executes whatever translation process is specified on the trading partner record under "process," passing the parameters that are needed by the translation process. These parameters are included:

  • Map

    The name of the map the translation process will use, for example, 72X_850_OUT for laws_outb.

  • Outbdata

    The path/name of the temporary file containing extracted application data for one EDINUMBER with an EDI header at the beginning. The EDI header is a comma-delimited record containing:

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

    • ISA sender qual

    • ISA sender ID

    • ISA receiver qual

    • ISA receiver ID

    • ISA version

    • ISA control number

    • Ack expected (0 or 1)

    • Prod or test flag ("P" or "T")

    • GS functional ID (for example. "PO" for 850s)

    • GS sender ID

    • GS receiver ID

    • GS control number

    • GS version

    • VALID_EDIOUT

    • The path/name of file where translation process should put valid EDI data to transmit.

    • REJECT_NAME

    • The path/name of file where translation process should put rejected EDI data.

    • EDSUBTBL

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

After the translation process completes, the translation server retrieves data from VALID_EDIOUT, REJECT_NAME and EDSUBTBL and processes it accordingly.

Process status and logs

This information is captured in the and tables. It will also be passed back to whatever process calls EDIOUT, such as Execute Outbound EDI (ED501). Cleo logs and monitor files, because of their size, will not be captured in the database tables, but are saved to logan/edi_logs.