1. Click on "Data"
2. Click on "Data Upload"
3. Date Upload is the date and time the data was uploaded
4. Uploaded By is who uploaded the data. If the Uploaded By is Data Hub it means the load was automated.
5. File shows the files that were uploaded.
6. Completed communicates of the data was loaded completely. If no, please follow the steps documented in the article "How to Address an Upload Failure."
7. Click "Log" to view the details of the upload as documented in the following steps.
8. Click "Download" to download the complete file that was uploaded.
9. Click "Delete" to delete the uploaded file. Delete simply deletes the record in the view. It does not delete the data loaded to the data base.

Clicking 'Log" opens the detail view where you can review the upload summary and the upload for errors.

1. File: The name of the file uploaded
2. Total lines in file: The number of lines that were in the file.
3. Fixed errors: Are non critical errors that the system can fix on its own such as a field was missing and thus defaulted to a set value.
4. Not fixed errors – The main concern is with not fixed errors, which means that DemandCaster is not accepting the data because of the way the data is formatted, the data is missing, or other data needed to reference may be missing.
5. Total inserted rows:
6. Total updated rows:
7. Rows before Csv upload:
8. Rows after Csv upload:
9. Message: Communicates general issues with the file.
10. Download – You can download a txt file of the data that was intended to be uploaded.
11. Excel: To export the error type report, click the excel button.
12. To review further detail, select the file to review from the drop down.

1. To review further detail, select the file to review from the drop down.
2. Error type filter filters the data between fixed and not fixed errors
3. Search to find a specific item in the data.
4. Line # is the specific line in the uploaded file with the error
5. Error type communicates if it is a fixed or not fixed error
6. Column # is the column with the error
7. Field is the field with the error (same as column)
8. Value is the specific entity that is causing the error
9. Message communicates the specifics of the error

A BOM cycle prevents the BOM from being loaded. If your BOM's are not being loaded, please check the error log for the BOM cycle message. See image below.

In addition to reviewing the error log, here is a suggested list of values to review to ensure they match your ERP data. If any values do not match, review the data integration process to ensure there are no issues. This review is irrespective of the data being correct for planning purposes. When using any of the analytics for review, ensure they have been run to reflect the latest data load.

• Review selected items 52 weeks sales and units. Use the Classification analysis page.
• Review selected item on hand, open replenishment orders, and open customer orders. Best place to review is the item planning detail view as long as the analysis is up to date.
• Review selected items lead times in the Lead Time analysis page.
• Review selected items stocking status in the Stocking analysis page.
• Review selected items make versus buy settings in the Stocking analysis page. If your items have bills of material, they will not explode unless they are set as make items.
• If DRP is enabled, review selected items distribution and manufacturing network relationships. Best place to review is the item planning detail view as long as the analysis is up to date.

As stated in this articles introduction, errors are typically related to relational data not being included in the upload file. Please contact your IT personnel or DemandCaster support to address the issues.