EDI Message Map form

Administration EDI Message Types Message Types view EDI Message Type form Message Map tab EDI Message Map form

The EDI Message Map form enables you to add and edit an EDI message map and link a mapping file and data dictionary file with it. The EDI message map controls data transformation between the EDI file and N4 during the mapping process. For more information on EDI processes, see Processes tab (on page 1).

N4 provides a standard set of mapping files and data dictionary files that you can customize for individual clients using the GoXML mapping utility licensed from Navis.

You can edit a mapping file to receive and send data for unit flex fields in an EDI message. The following schema files support flex fields:

To export the schema files, see EDI Message Type form (on page 1).

To add or update all of the supported EDI message types and respective standard EDI message maps, see Set-up Database view.

To add an EDI message map:

  1. In the Map Id field, enter a name that uniquely identifies the EDI message map.

You can create multiple maps for an EDI message as trading partners may use different implementations of the EDI message.

  1. From the Direction list, select the direction of the EDI message.

  2. To import the data dictionary file that defines the EDI message structure, click Import DIC.

  3. In the Import XML Configuration dialog box, select the data dictionary file and click Open.

XML data dictionary files have the extension .dic and flat text dictionary files have the extension .fxd.

The EDI Message Map Dictionary File field displays --loaded-- in the text box to indicate that a data dictionary file is linked with the EDI message map.

  1. To import the mapping file that defines the EDI map, click Import MGT.

  2. In the Import XML Configuration dialog box, select the mapping file and click Open.

Mapping files have the extension .mgt.

The EDI Message Map File field displays --loaded-- in the text box to indicate that a mapping file is linked with the EDI message map.

  1. Optionally, in the Description field, enter a description of the map.

  2. Click Save.

To remove a loaded file, click Clear.

To edit a custom EDI message map:

  1. To export a custom or standard data dictionary file, click Export DIC.

  1. In the Export XML Configuration dialog box, specify a name for the data dictionary file and click Save.

To save an XML data dictionary file, you must enter a name and the extension (.dic).

To save a flat text dictionary file for a FLATFILE EDI message, you must enter a name and the extension (.fxd).

  1. To export a custom or standard mapping file, click Export MGT.

  2. In the Export XML Configuration dialog box, specify a name for the mapping file and click Save.

To save a mapping file, you must enter a name and the extension (.mgt).

  1. Edit and save the mapping file and data dictionary file as needed using the GoXML mapping utility.

You cannot import an edited mapping file or data dictionary file for a standard or built-in EDI message map.

  1. If you edited the data dictionary file, to import your edited data dictionary file, click Import DIC.

If you do not import an edited data dictionary file, N4 uses the standard data dictionary file for the selected EDI message type, if available.

  1. In the Import XML Configuration dialog box, select the edited data dictionary file and click Open.

  2. To import the edited mapping file, click Import MGT.

  3. In the Import XML Configuration dialog box, select the edited mapping file and click Open.

  4. Click Save.

If you select a standard or built-in EDI message map, N4 does not display the Save button.

To remap an EDI interchange:

  1. Make the necessary changes to correct the processing errors in the EDI mapping file.

For more information, see EDI Message Map (on page 1).

  1. Click Remap.

  2. Click Repost.

If the Auto Post option is selected for the EDI session, the EDI interchange is automatically posted after you edit a segment and Remap the EDI interchange.