It is not possible to import data on combined flows. Forecast, events, historical data, budget and Target Sales Plan can only be imported in inventory units.
Importing forecast and history in demand plan should not be does directly into our tables, because our internal structure are quite complicated, and it is important to keep data consistent with each other. So therefore we have made a LU dedicated to do this task, it is called FORECAST_DAY_IMPORT.
The import processes is as follows:
The data is filled into the import LU(FORECAST_DAY_IMPORT)
Then the job “External Import” is stared. Which read the table and inserts the data into our tables. Ensuring consistencies, and reporting inconsistent data
Finally the job empties the table FORECAST_DAY_IMPORT
| Field | Description |
| FLOW_ID | Contains the flow id only base flows can be used |
| PART_NO | Contains the part number of the part. Part must exsist in Part Catalog |
| FORECAST_ID | Use 0 for the main forecast, others for different scenarios. If scenario ID does not exsist it will be created, allowing you to import scenario that does not exsist |
| START_DATE | The first date of the period |
| END_DATE | The last date of the period |
| FORECAST | The forecast (in inventory units), if not null then the start date and end date has to be in the current forecast range, that is coverd buy the current forecast. If forecast should not be imported then set it to NULL |
| HISTORICAL_DEMAND | The historical demand (in inventory units), allowed range for the start and end date is the entire range from the first history period to the preset period. If maximum historical lenght is set to 32 and we are using monthly period version then you can import data 3 years back. If historical demand is not to be imported then it should be set to NULL |
| ADJUSTED_DEMAND | The adjusted demand (in inventory units), allowed range for the start and end date is the entire range from the first history period to the preset period. If maximum historical lenght is set to 32 and we are using monthly period version then you can import data 3 years back. If historical demand is not to be imported then it should be set to NULL |
| EVENT | The event (in inventory units), alloed ranges for the start and end date is the entire range from the first history period to the last forecast period. If event should not be imported it should be set to NULL |
| BUDGET | The budget (in inventory units) to be imported. Allowed ranges for the start and end date is the entire range from the first history period to the last forecast period. If budget should not be imported it should set to NULL |
| TARGET_SALES_PLAN | The target sales plan (in inventory units) to be imported. Allowed ranges for the start and end date is the entire range from the first history period to the last forecast period. If target sales plan should not be imported it should set to NULL |
| STATUS | This must be “NEW” for rows that should be imported. After the import is done this field will indicate an error code if there was something wrong with the fields. Rows imported successfully are deleted |
Data migartion tool or similar can be used to fill the FOREAST_DAY_IMPORT/FORECAST_DAY_IMPORT_TAB LU/Tables.