laitimes

How to summarize EDI file processing failures?

author:Su Yuewei

When the EDI system runs automatically in the background, it sometimes encounters the failure to process files, and there are many reasons for failure, and some customers want to summarize the failed files to facilitate the analysis of the cause of the failure, reduce similar errors in the future, and also facilitate later troubleshooting, correct the error and reissue.

In order to summarize the files that failed to be processed by the EDI system, we first need to understand the file port of the EDI system.

File port

The File port is a file port whose main function is to pull files from an external directory into the Zhixing EDI system workflow, or write files from the Zhixing EDI system workflow to an external directory. We can use the File port here to put the files that failed to process into the specified folder.

path

The path part in the port is the external path of the port to get the file or push the file.

How to summarize EDI file processing failures?

authentication

The authentication section in the port that specifies the users who have access to the configured path. When we want to read the files under the corresponding path, but we do not have permission to access the folder in the path, we need to configure the user account, password, and domain of the specified user here. Configuration is only required if the Bridge EDI system does not have access to the configured path.

How to summarize EDI file processing failures?

reception

Here we can set the type of file received and whether it is necessary to delete the file that has already been read under the path.

How to summarize EDI file processing failures?

In addition to the File port, there is another important function - showing the wrong path.

Error path

The port is dedicated to routing the path of the error file, and the file that fails to be processed by the port can be routed to other ports through this path for further processing.

The error path is hidden by default, we need to select the port where we want to show the error path, right-click on "Show error path".

How to summarize EDI file processing failures?

After understanding the File port and display error path function of Zhixing Bridge, it is very simple to summarize the failed files and put them into the specified directory.

For example, when an enterprise uses the Zhixing Bridge EDI system for data processing, it wants to summarize the files that failed in the Excel port processing in the workflow into a specified folder. We can configure it by following these steps.

Step 1: Drag and drop the File port and Excel port in the workspace (here can be any port, here the Excel port is used as an example).

Step 2: Write the path to the file port where you want to store the failed file. We need to write the path we want to read or write to the file in the path section.

Step 3: Display the error path of the Excel port and connect it to the File port (note here: the routing line of the error path is a red dashed line)

How to summarize EDI file processing failures?

At this point, our configuration is all over, if there is a file that has not been processed successfully on the Excel port, we can view the file that failed to be processed under the path entered on the File port.

For example, we configure the path of the routing error file in the File port, as shown in the figure:

How to summarize EDI file processing failures?

We upload a mismatched test file file on the Excel port and can see that the Excel port file processing fails.

How to summarize EDI file processing failures?

Open the input interface of the File port to see that the file is successfully routed to the specified path.

How to summarize EDI file processing failures?

We open the specified path of the File port, and we can see the file that the Excel port failed to process.

How to summarize EDI file processing failures?

Aggregating the files that fail to process port automation into a specified folder can facilitate customers to better troubleshoot the cause of the failure, and greatly reduce the workload of later error correction.