Extracted EDI data

If the incoming EDI data is ASC X12, will extract each functional group from the incoming data and write it to a temporary file, which is then available as input to your map. If there is more than one functional group in the incoming transmission, will execute your map once for each incoming functional group.

If the incoming data is UN/EDIFACT, will extract each UNB - UNZ envelope from the incoming data and write it to a temporary file, which is then available as input to your map. If there is more than one UNB - UNZ interchange in the incoming transmission, will execute your map once for each interchange.

  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. Then, as described below, you must make some additional changes to this type tree to make it work with .

    • 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 steps on the ANSI-XXXX-SEGMENT category, being sure to propagate both changes to all subtypes.

    • If you are using UN/EDIFACT, go to EDIFACT-CONTROL-ENVELOPE 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 steps at category VXX_X - SEGMENT and VXX_X -SEGMENT2.

        Terminators and Delimiters

        The values specified above are required for to work. This does NOT, in the case of ASC X12, mean that these are the values your trading partner must send to you. will parse the incoming transmission from your trading partner using whatever terminators and delimiters they send.

        In the case of UN/EDIFACT, however, the values specified above for use within your map are also the required values for the UN/EDIFACT standard when using the UNOA character set, which is what we support for . Your trading partner will therefore need to send these exact values.

  2. Create Input Card 1 for extracted EDI data by selecting your EDI type tree, and then selecting one of these for your type name:

    • #855 F3010 Inbound Partner Functional Group ANSI EDI if your map is ASC X12 (substitute your document type and version for 855 and 3010)

    • Partner EDIFACT Inbound Interchange EDI if your map is UN/EDIFACT

      Sample Type Trees

    • Hc3010.mtt (ASC X12, version 003010)

      Sample Maps

    • Lo855803.mms

  3. Create Input Card 2 for EDI header data.

    This file consists of a single record containing information about the functional group or interchange being passed to your map in the EDI data file above. This information may be useful in your map:

    • Lawson Trading partner ID—This might be necessary for doing lookups on the substitution table.

    • EDI Number—This is required in some of the Lawson interface files.

    • Interchange control number—The ISA or UNB control number.

    • Functional Group control number—ASC X12 only.

      Sample Type Tree

    • EDI_hdr.mtt

      Sample Maps

    • edifactack.mms (Inbound EDIFACT ORDRSP message)

    • Lb85573i.mms (Inbound ASC X12 855 document)

  4. Create Input Card 3 for the EDI Substitution Table.

    With each execution of the mapping process (in this case, tsi_inb), the server will extract all the records from the EDI substitution database table and write them to a temporary file that is made available to your map. Your map may reference this table to look up substitution values.

    Sample Type Tree

    • edsubtbl.mtt

      Sample Maps

    • Lo855803.mms