Setting up trading partners

Use Trading Partner Setup (ED10.1) to establish information about your trading partner(s).

A trading partner record must exist for each trading partner/transaction set combination. For example, if you are sending purchase orders (850) to Baxter and receiving purchase order acknowledgments (855) from Baxter, you would have two trading partner records: one for the 850 and another for the 855.

Note: When you set up your outbound EDI job for the 820, in the field called "EDI Number Start Pos", specify the value "820". For length, specify "15".

You can also set up a trading partner record for functional acknowledgment processing. Setting up acknowledgment processing: ASC X12 997s

Set up trading partners

  1. Access Trading Partner Setup (ED10.1).
  2. Specify this information that applies to this trading partner for both outbound and inbound processing. The values that you specify are different depending on whether you are using ASC X12 or UN/EDIFACT standards. (UN/EDIFACT is supported by Lawson EDI Professional for Supply Chain only.)

    ASC X12 and UN/EDIFACT standards Separate field descriptions are given below for ASC X12 and UN/EDIFACT.

    For ASC X12:

    Field Outbound Inbound
    EDI Nbr Required. This value identifies the trading partner/transaction record that you are setting up. This value must match the value in the EDINUMBER field in the application flat file from Lawson. Required. This value is written to the EDINUMBER field in the application flat file.
    Organization Id This field will eventually tie the trading partner record to the Lawson Resource Management application. For now, just specify any number. Same
    Direction O I
    Carrier Required. This identifies the carrier for this trading partner. A carrier record must exist for the carrier named here. Same
    Tpid Required. Lawson trading partner ID. (See theLawson EDI for Supply Chain Management Trading Partner List for a list of trading partners and their IDs.) Same
    Trans Type Required. This identifies the ASC X12 transaction set type. Same
    Std Version Required. Standard version for this trading partner transaction. (See the Lawson EDI for Supply Chain Management Trading Partner List for a list of trading partners with versions supported for each partner.) Same
    Ack Request 1 specifies that 997 is expected. 0 zero or null specifies that no 997 is expected. 1 specifies that 997 is expected by this trading partner and that the system will generate and send 997. "0" or null specifies that no 997 is expected.
    Process

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

    See the Lawson EDI for Supply Chain Management Trading Partner List for information on maps and map names.

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

    See the Lawson EDI for Supply Chain Management Trading Partner List for information on maps and map names.
    Map

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

    If using the Lawson translator, the map name varies by Lawson release.

    See the Lawson EDI for Supply Chain Management Trading Partner List for information on maps and map names.

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

    If using the Lawson translator, the map names vary by Lawson release.
    Isa Control Nbr The system will increment the value in this field by one for each outbound ISA header. The system updates with the most recently received ISA control number for this trading partner.
    Gs Control Nbr The system will increment the value in this field by one for each outbound GS header. The system updates with the most recently received GS control number for this trading partner.

    For UN/EDIFACT:

    Field Outbound Inbound
    EDI Nbr Required. This value identifies the trading partner/transaction record that you are setting up. This value must match the value in the EDINUMBER field in the application flat file from Lawson. Required. This value is written to the EDINUMBER field in the application flat file.
    Organization Id This field will eventually tie the trading partner record to the Lawson Resource Management application. For now, just specify any number. Same
    Direction O I
    Carrier Required. This identifies the carrier for this trading partner. A carrier record must exist for the carrier named here. Same
    Tpid Required. Lawson trading partner ID. (See the Lawson EDI for Supply Chain Management Trading Partner List for a list of trading partners and their IDs.) Same
    Trans Type Required. The UN/EDIFACT message name, for example, ORDERS. Same
    Std Version Required but not used by Lawson EDI for UN/EDIFACT. You are responsible for mapping the version correctly in your IBM® WebSphere® Transformation Extendor (WTX) map. Trading Partner Setup (ED10.1), however, requires a value in this field, so specify any value to meet this edit requirement. Same
    Ack Request Leave blank. Acknowledgments are not supported for UN/EDIFACT 1 specifies that 997 is expected by trading partner and that the system will generate and send 997. 0 or null specifies that no 997 is expected.
    Process Required. Specify this value: wtx_out. Required. Specify this value: wtx_in.
    Map Required. Name of your IBM® WebSphere® Transformation Extender (WTX) map. Required. Name of your IBM® WebSphere® Transformation Extender (WTX) map.
    Isa Control Nbr The system will increment the value in this field by one for each outbound UNB header. The system updates with the most recently received UNB control number for this trading partner.
    Gs Control Nbr Not applicable. Functional groups are not supported by Lawson EDI for UN/EDIFACT. Not applicable. Functional groups are not supported by Lawson EDI for UN/EDIFACT.
  3. On the Outbound page, specify the information that applies only to outbound EDI processing for this trading partner. The values that you specify are different depending on whether you are using ASC X12 or UN/EDIFACT standards. Separate field descriptions are given below for ASC X12 and UN/EDIFACT.

    For ASC X12:

    Field Description
    Your Isa Id Qual Required. Used in outbound ISA field 05.
    Your Isa Id Required. Used in outbound ISA field 06.
    Partners Isa Qual Required. Used in outbound ISA field 07.
    Partners Isa Id Required. Used in outbound ISA field 08.
    Your Gs Id Required. GS sender ID, element GS.02 in the outbound GS header.
    Partners Gs Id Required. GS receiver ID, element GS.03 in GS header.
    Gs Functional Id Required. Outbound GS.01 element. Specify "PO" for purchase orders.
    Prod/Test Specifies whether this is production or test. Used in the outbound ISA header.
    Elm Sep Character to use as the data element delimiter.
    Sub Elm Sep Character to use as the delimiter within composite data elements.
    Seg Term Character to use as the segment terminator. (To use a newline, specify NL, although using newlines is not recommended).

    For UN/EDIFACT:

    Field Description
    Your Isa Id Qual Not used.
    Your Isa Id Required. Your UNB interchange ID.
    Partners Isa Qual Not used.
    Partners Isa Id Required. Partner's UNB interchange ID.
    Your Gs Id Required but not used. Specify any value to get past the screen edit.
    Partners Gs Id Required but not used. Specify any value to get past the screen edit.
    Gs Functional Id Not used. Leave blank.
    Prod/Test Specifies whether this is P (production) or T (test). Used in the outbound ISA header. If you wish to use this field in your IBM® WebSphere® Transformation Extender (WTX) map, you will need to convert the P or T from the EDI header record to the corresponding UN/EDIFACT value in your map.
    Elm Sep + (plus sign)
    Sub Elm Sep : (colon)
    Seg Term ‘ (single quotation mark)
  4. Access the Inbound page.
  5. On the Inbound page, specify the information that applies to inbound processing for this trading partner. The values that you specify are different depending on whether you are using ASC X12 or UN/EDIFACT standards. Separate field descriptions are given below for ASC X12 and UN/EDIFACT.
    Field Description
    Your Isa Id Required. Used in inbound ISA field 08.
    Partners Isa Id Required. Used in inbound ISA field 06.
    Your Gs Id Required. GS sender ID. Element GS.03 in the inbound GS header.
    Partners Gs Id Required. GS receiver ID. Element GS.02 in GS header.
    Path Path/filename where inbound application data should be written (appends to existing file content, if any).
    Your Isa Id Required. Your UNB interchange ID.
    Partners Isa Id Required. The trading partner's UNB interchange ID.
    Your Gs Id Required but not used. Specify any value to get past the screen edit.
    Partners Gs Id Required but not used. Specify any value to get past the screen edit.
    Path Path/filename where inbound application data should be written (appends to existing file content, if any).
  6. Add the record to save your work.
Related topics