Process and Response

This section deals with the EDI server responses when your file is checked, validated prior to adding to the system. These are designed for customers of the warehouse to be advised of an issue with their EDI document.
If you are using the API then there are other responses you will receive prior to this which are API responses and not covered in this section.

As is normal industry practise we validate information we are sent to ensure that it meets the requirements, we have a multi tier approach

API validation (only if using the API)
Initial Message validation - failure at this point would have the message completely rejected.
Item validation - failure of something within the file which means the item will have to be manually dealt with.

It is not possible to code for every possible issue an inbound file may cause and sometimes error messages are not helpful, but they should be sent to the warehouse customer services to deal with further.

Noitifications are available during this process as follows

Initial receipt of the file notification (this is optional)
Notification of any issues within the file (you will always be sent this)

Once the file is loaded into the warehouse system you can then request an orders processed report which confirmed what the orders received were and what was processed on them.

Examples of emails you may receive

Example Email

Confirmation of Receiving.

This is just our system saying we have something to process.

At this point we have not checked or validated the information in the file.

File Failure

This is a complete failure of the file. The file will not be processed and is usually due to a complete failure of the information in the file.

You should not resend, but contact the warehouse for assistance however most of the time you have to speak to your own developer to resolve this.

Item Failure

There is a problem with a line on your order or some details of the order header are incorrect.

This section deals with the EDI server responses when your file is checked, validated prior to adding to the system. These are designed for customers of the warehouse to be advised of an issue with their EDI document.
If you are using the API then there are other responses you will receive prior to this which are API responses and not covered in this section.

Introduction
As is normal with most advanced web services, incoming submissions go through several stages of validation and various responses can be received should the submission fail at any of these stages. First the file itself is validated Second the elements (Sales Orders, Purchase Orders, Products etc) are validated. As part of the approval process, we add approved accounts into a control table where we can control a number of settings and permissions, this process is carried out by Ontech / Vision support after testing. The warehouse operator has the ability to maintain the email address for this approval as well as the sending of file receipt messages, but they have no other abilities to control other aspects of this control.
File receipt confirmation:
Depending on your setup, you can be configured to receive this email confirmation or not. This email only confirms that the file has been received and nothing more, this is before any validation takes place. The message body will look similar to below:
Stage 1 - File level validation:
Incoming files are queued and validated. The initial validation checks that submitted files: Are constructed correctly as per their file type (valid CSV / valid XML). Meet our expected file format. Contain the correct data types for each element. Should the submission fail, an email will be sent to you with a message body similar to below: In this instance, the entire file has failed and none of the contents will be processed.
Stage 2 - Item level validation:
Should your submission pass the first stage of validation, it will move on to the second Stage. Here we're checking the individual records within the file submitted. If you've sent in a Sales Order file, then we're checking each individual Sales Order within. If it's a Product file, then each individual product, and so on.... The validations which occurs here are specific to each file type, but to give a basic idea of what occurs: We're performing the more advanced checks to ensure what has been sent in is logical (e.g. a Sales Order sent in for delivery, but with no delivery address). That the data submitted exists in our system (where necessary. For example: A Purchase Order sent in with values and currencies, but the currency code submitted is invalid and does not exist in our system. Should the submission fail these checks, you will receive an email with a message body similar to below: In this instance, some of the items within the file could have failed validation and others passed. Any that failed will not stop the ones that have passed from being processed, but the failed ones will be held until corrected.