HiAssume that it is for the Legacy client (the separate application) since the screen shot is for this client.The remove one flow entirely, just set not on all the boxes for that flow. Then the flow should not show up in the client at all. So set no, no….., no on all for the flow you do not want to see. That should remove the flow in question.
The Time Line function will change the view of the forecast historical data and display the forecast & history in the selected Time Line periods. You can then change the forecast in this new period. Note that the historical data will not be accurate in the new Time line if the new time line is ‘smaller/shorter’ than the main period version (from Months to weeks for example. But going from Months to Quarters the historical data will be accurate). All calculations are done on the main period version (forecast calculations and seasonal profiles etc..). You should select a main period version that gives you a smooth history, for industries with little to medium number of transactions a monthly period version is usually the best (mostly used period version by manufacturing companies). With higher transaction volumes weekly period version can be considered (Retail, food and beverage companies tends to select weekly period versions). The important thing is to select a period version that
HiThis approach will not work, you cannot have multiple Demand Plan Servers running against the same environment. So you have to select one ‘mail’ period versions. You can use the Time Line functionality in Demand Planning and still be able to change and look at your forecast in different periods (Quarters, Months, week and daily/days. Just do not run 2 DP servers against the same environment it will cause errors./Ingvar
You have to connect the Demand Plan Server Setup to the running DP-Server instance. This is done in Supply Chain Planning/Demand Planning/Basic Data/Demand Plan Server When connecting the DP Server will read the connected DP Setup and will be ready usage/Ingvar
HiIn Demand Planning all parts are treated the same way serialized and no serialized, they will all have a forecast with decimal points, in the Exported Forecast (this is where demand planning puts the resulting forecast so that the other IFS components in need of a forecast can retrieve it) in this table/view all forecast are with decimals (as many as we can compute), to minimize the rounding error as mentioned in previous post.As mentioned in previous post the Import to MS job/MS can round the numbers. I am not all that familiar with the Import Demand Planning Forecast job to MS/MS and how it works in detail, try to post a question in a Master Scheduling tread and you should get a answer how rounding is done in MS.
These yellow and red are numbers indicate historical periods that are between 1-2 Standard Derivations = Yellow and outside 2 Standard Derivations = Red. Note that this statistically is OK, the red ones are just a bit unlikely / rare (about 4% likelihood) . Default Demand Planning will automatically adjust demand periods that are outside 3 standard derivations and set the number to 3 standard derivations (this is still a very high number), this cleansing you can turn off.
There is no way to round the forecast numbers from demand planning. You can set the main Demand Planning client to have 0 decimals in the Forecast Table, but when adjusting the forecast from aggregated levels the resulting forecast will be with decimal points, so will the forecast be when it’s calculated. The reason for this is that it is not smart to round the forecast, is that the forecast is used for further calculations in MS/MRP/IPR and its never vice to round the number in the middle of an calculation (it introduces rounding errors), you should round at the end for the calculation.Example: Say the forecast in 0.5 per period, in MS you choose to add together 4 periods as the lot/batch size. This will give you a lot size of 2 units, but if you round the forecast before MS the lot size will become 4 which is a huge difference.I am not an expert in all details in MS but I think that you can setup decimal rules in there so that you don’t show any decimals.
Try to restart the DP/IPR Server, that should do the trick /Ingvar
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.