Configuring Lawson applications

You must configure your Lawson applications to enable some EDI transactions.

820 Remittance and Payment Transaction

There are several things you must know in order to successfully configure your Lawson application and EDI system for sending the 820 transaction:


AP Vendor setup
You may send payments to multiple vendors through a given bank. In EDI terms, the bank is your trading partner because that is where the 820 is sent. Therefore, if you are sending payment to multiple vendors via Bank A, then you must set up one trading partner record in EDI. For this example, you choose an EDI number value of "BANKA". Then, in your Lawson Accounts Payable application, you must specify an EDI number of "BANKA" for all vendors who will receive your payment through the 820's that you sent to Bank A.


AP161 Run options
EDI supports sending the 820 for combined payment and remittance only. It does not support sending the 820 for payment only or remittance only. AP161 is the Lawson accounts payable interface program that creates the flat file, which will serve as input to your outbound EDI job. There are options to run AP161 in a variety of ways, but the only option that EDI supports is for combining payment and remittance in the same file.


ED501 setup
When you set up your outbound EDI job for the 820, look for the EDI Number Start Pos field, and specify 820 for the value. For length, specify 15.

824 Application Advice Transaction

Because there is no Lawson application interface that corresponds to the 824, EDI support is limited to a generic mapping. The mapping removes the element delimiters from the incoming segments and writes them as records to a csv file. Segments ST through SE are captured for each 824 received. In addition to the fields from the segment, the EDI system will prepend the EDI number of the trading partner to each record. In this example, an 824 received in EDI format:

ISA*00*          *00*          *ZZ*BANK           *ZZ*MYCOMPANY      *021028*095
9*U*00401*000004777*0*T*:
GS*AG*BANK*MYCOMPANY*20021028*095948*047770001*X*004010
ST*824*0001
BGN*11*000000010*20021028
OTI*TR*TN*1*****10*0001
DTM*007*20021025
TED*806*REQUIRED DATA IS MISSING OR INVALID; BPR07 FOR ACH*****1234
TED*806*REQUIRED DATA IS MISSING OR INVALID; BPR13 FOR ACH*****1234
OTI*GR*ZZ*NV*****10
AMT*OP*99999.99
AMT*BT*99999.99
AMT*NP*0
QTY*53*1
QTY*54*1
QTY*55*0
SE*14*0001
GE*1*047770001
IEA*1*000004777

Will result in this flat file if the EDI number of the inbound trading partner is BANK824:

BANK824,ST,824,0001
BANK824,BGN,11,000000010,20021028
BANK824,OTI,TR,TN,1,,,,,10,0001
BANK824,DTM,007,20021025
BANK824,TED,806,REQUIRED DATA IS MISSING OR INVALID; BPR07 FORACH,,,,,1234
BANK824,TED,806,REQUIRED DATA IS MISSING OR INVALID; BPR13
FOR ACH,,,,,1234
BANK824,OTI,GR,ZZ,NV,,,,,10
BANK824,AMT,OP,99999.99
BANK824,AMT,BT,99999.99
BANK824,AMT,NP,0
BANK824,QTY,53,1
BANK824,QTY,54,1
BANK824,QTY,55,0
BANK824,SE,14,0001

867 Product Transfer and Resale Report

You may refer to the Inventory Control User Guide for information on setting up the Product Transfer and Resale Report (IC153). If the EDI option is selected for the output, then a file is created:

for Windows: %LAWDIR/productline/edi/out
for UNIX: $LAWDIR/productline/edi/out
for System i: $LAWDIR/productline/edi/out

Note: For all three EDI output options, the file will be called XFREDI.

As with any other trading partner, you must set up a Trading Partner (ED10) with the appropriate details such as map and process names. Consider these fields:

EDI Nbr

For outbound, this value identifies the trading partner or transaction record that you are setting up. This value must match the value in the EDINUMBER field in the application flat file from Lawson.

For inbound, you must write this value to the EDINUMBER field in the application flat file.

Direction

O for outbound or I for inbound.

Carrier

This identifies the carrier for this trading partner. A carrier record must exist for the carrier named here.

Tpid

Lawson trading partner ID.

Trans Type

This identifies the ASC X12 transaction set type.

Std Version

Standard version for this trading partner transaction.

Ack Request

1 indicates that 997 is expected by this trading partner and that the system will generate and send 997. 0 or null indicates that no 997 is expected.

Process

This field identifies the translation process that the translation server will execute. If your organization is using the Lawson translator,then the outbound process name varies by Lawson release.

Map

This field identifies the map that the translation process named above will use.

Isa Control Nbr

For outbound, the system will increment the value in this field by one for each outbound ISA header.

For inbound, the system updates with the most recently received ISA control number for this trading partner.

Gs Control Nbr

For outbound, the system will increment the value in this field by one for each outbound GS header.

For inbound, the system updates with the most recently received GS control number for this trading partner.

Isa Id Qual

Both yours and your partners’. Used in outbound ISA field 05.

Isa Id

Both yours and your partners’. Used in outbound ISA field 06.

Gs Id

Both yours and your partners’. GS sender ID, element GS.02 in the outbound GS header.

Gs Func Id

Outbound GS.01 element. Specify inPOlu for purchase orders.

Prod/Test

Indicates whether this is production or test. Used in the outbound ISA header.

Sub Elm Sep

Character to use as the delimiter within composite data elements.

Elm Separator

Character to use as the data element delimiter.

Seg Terminator

Character to use as the segment terminator. (To use a newline, specify NL, although using newlines is not recommended).

To send the file, you must create an outbound job. Consider these fields:


Field	Value
Application File	for Windows: %LAWDIR/productline/edi/out/XFREDI for UNIX: $LAWDIR/productline/edi/out/XFREDI for System i: $LAWDIR/productline/edi/out/XFREDI
EDI Number Start Pos	1
EDI Number Length	15