...
...
...
...
...
...
...
...
...
...
This page lists the common iHub errors that are returned on file Load. This includes API responses, FTP XML response files and Activity monitor details.
For FTP XML When the XML file itself is invalid and cannot be parsed, the entire file will fail.. I.e. the date format is invalid. Example response file:
XMLExampleDateFormat.xml_29-07-20-052626_response.xml
XML FTP example response file when the first order in a file of two, has missing mandatory fields. Multiple responses are wrapped in <Responses> tags:
XmlExampleMissingFields.xml_29-07-20-052838_response.xml
For FTP CSV orders, if you receive the “File is not valid” error, the whole file failed to upload. For example, if this was a CSV file for 10 different sales order numbers, all 10 orders failed and would not be uploaded into SupplyStream. This is commonly caused by a missing mandatory field. The sales order number causing the error would need to be omitted and the file would then need to be re-uploaded. For CSV Manual uploads, a file missing mandatory fields would also fail the structural check on upload.
All errors listed below will fail on an entity basis (i.e. per sales order number).
...