Specifying outputs to your outbound IBM® WebSphere® Transformation Extender (WTX) map

This procedure tells you how to set up maps for the EDI-formatted data that is created by running your map.

Specify outputs from your outbound IBM® WebSphere® Transformation Extender (WTX) map

  1. Follow the instructions supplied by IBM® WebSphere® Transformation Extender (WTX) for creating your type tree by choosing an EDI standard type tree from the ones supplied with IBM® WebSphere® Transformation Extender (WTX), cloning it, and deleting those documents you do not intend to use.
  2. Perform additional changes to this type tree to make it work with Lawson EDI Professional for Supply Chain.

    • If your type tree is ASC X12, you will need to go to the ANSI-CONTROL-SEGMENT category, open the Properties dialog box, and make these changes:

      1. Change the terminator to literal with a value of <NL>.

      2. Propagate this change to all subtypes.

      3. Change the delimiter to literal with a value of ^.

      4. Propagate this change to all subtypes.

      5. Repeat these changes on the ANSI-XXXX-SEGMENT category, being sure to propagate both changes to all subtypes.

    • If you are using UN/EDIFACT, go to the EDIFACT-CONTROL-ENVELOPE category and make these changes:

      1. Change the terminator to literal with a value of ‘ (single quotation mark).

      2. Propagate this change to all subtypes.

      3. Change the delimiter to literal with a value of +.

      4. Propagate this change to all subtypes.

      5. Repeat these changes on the VXX_X - SEGMENT and VXX_X - SEGMENT2 categories.

        Terminators and Delimiters

        The values specified above are required for Lawson EDI Professional for Supply Chain to work. This does NOT, in the case of ASC X12, mean that these are the values you must send to your trading partner. The values sent to your trading partner are the ones specified on your trading partner profile, not necessarily the ones used in your map.

        This is also true in the case of UN/EDIFACT. In this case, however, the values specified for use within Lawson EDI Professional for Supply Chain are also the required values for the UN/EDIFACT standard when using the UNOA character set, which is what Lawson supports for Lawson EDI Professional for Supply Chain, so you will want to specify these values on your trading partner profile as well.

  3. Create Output Card 1 for outbound EDI data by selecting your EDI type tree, and then selecting one of these for your type name:

    • Partner X12 Outbound Interchange ED if your map is ASC X12

    • Partner EDIFACT Outbound Interchange EDI if your map is UN/EDIFACT.

      Sample Type Trees

    • Hc3020.mtt (ASC X12, version 003020)

      Sample Maps

    • Lo850803.mms

  4. Create Output Card 2 for any data that IBM® WebSphere® Transformation Extender (WTX) rejects. Lawson EDI Professional for Supply Chain will then be able to report the location of this file in its audit log.

    Sample Type Tree

    • Reject.mtt

      Sample Map

    • Lo805803.mms

Related topics