Possible scenarios that can result to errors or warnings
These scenarios before or during import may cause an error or result to a warning:
| Scenario | Possible fix |
|---|---|
| The file is not in the correct format.
For example, the file has no *FRF column. |
Make sure the file is in the correct format. Make sure that there is a *FRF column, and that column is empty. |
| The period in the file does not match the dataset's Period
Type.
For example, the dataset's Period Type is months but the file contains period that is more than 12. |
Make sure that the period in your file matches the dataset's Period Type. |
| The file contains non-standard DMP column names.
The import action will continue. The event logs will contain the non-standard column names that cannot be mapped by DMP. |
Check your import file for non-standard DMP column names.
Look at the event logs for the list of column names that cannot be mapped. |
| The file contains columns with invalid content.
For example, the column UCDEMA (Demand Forecast) should contain numbers only but your file contains letters or special characters. The entry or row in the file that contains invalid content will not be imported and will be logged in an .csverr file. This file is autogenerated for the invalid entries and this file can be found on the same path where the import file is located. |
Make sure your import file does not have columns with
invalid content.
Check the .csverr file for the list of invalid rows. |
| The chosen Transaction Type is inconsistent with the column
names in the import file.
For example, Transaction Type 34 (Demand/Calculated sales forecasts) normally has the accumulators UCDEMA, MFCFOR, MFMFOR, and MDFMADJ. |
Make sure that the chosen Transaction Type is consistent with the column names in the file. |