Sequence of automatic EDI processing of received messages

<< Click to Display Table of Contents >>

Navigation:  Automation > EDI > Export received EDI data >

Sequence of automatic EDI processing of received messages

1.A file was received and processed (eg. decrypted) by one of !MC5s communication modules (eg. via OFTP2).

2.The file gets passed to the Module EDI if EDI processing is activated for the partner (Partner settings / EDI / Enable EDI processing) from which the file was received and if the file matches the file pattern specified in the partner settings (Partner settings / EDI / File mask).

3.The data gets converted from EBCDIC to ASCII character set, if EBCDIC is selected as character set in Partner settings / EDI / Character set or if ASCII + VDA EBCDIC is selected and the file contains one or more VDA messages using EBCDIC character set.

4.If a filter is selected in Partner settings / EDI / Filter that filter is applied to the data. A filter can reject, accept or change data.

a.If the filter blocks the data (filterRes = fiAbort), the processing is cancelled.

b.If the filter accepts the data (filterRes = fiUseInput), the original data is processed.

c.If the filter changes the data (filterRes = fiUseOutput), the changed data is processed.

d.If an error occurs during execution of the filter (either is a fatal error occurs or if filterRes is set to fiError), processing gets cancelled.

5.!MC5 tries to identify the contained message(s). If identification fails or the identified message type isn't licensed, processing is cancelled.

6.The message is added to the inbox and message archive.

7.The message gets printed, if the option print messages (or equivalent) is enabled for the identified message type (Settings / EDI / Message types / ...).

8.All export rules are tested if they match the received message. Each matching rule (the rule is enabled and both message type and partner match) then gets applied to the data:

a.!MC5 tests if the target directory for the export exists or can be created (see f) and if it is writeable. If this fails, processing of this export rule is cancelled.

b.If a pre-filter is specified in the export rule, then it will be applied to the data. A filter can block, reject or modify data. If the filter rejects the data, the processing of this export rule is aborted. If the data is changed, the processing continues with the changed data in the following.

c.The data gets converted, if the option Convert data is enabled and a valid conversion is selected.

d.(Only VDA messages) If the option insert CR/LF after each record is enabled for the message type (the target type of the conversion, if Convert data is enabled) in Settings / EDI / Messages types / ... / Export options a carriage return and line feed get inserted after each 128 byte record.

e.The selected filter is applied, if one is selected. This filter too can accept, reject or change the data. If the filter rejects the data, the processing of this export rule is aborted.

f.The data gets converted to EBCDIC, if Convert data from ASCII to EBCDIC is enabled.

g.The data gets saved to the export file. File name and target directory for the exported file are are created using the Export file name settings of the rule, which may contain different placeholders (see Reference / Settings / Automatiion / Export received EDI data for further details).

h.Steps a to f will be repeated for each matching export rule.

Inbox export status when using multiple export rules

The export status shown in the inbox only reflects the status of the last export. So if more than one export rules are applied to one message during EDI processing, only the result of the last applied rule is seen here. For detailed information about EDI processing always refer to the protocol.

9.Steps 7 and 8 are repeated for each message contained in the data.

10.EDI processing is finished.