Use registry parameters to set the Demand Plan Server to function in different ways. Some of these settings can be set from setup dialogs, while others can only be changed directly in the registry. Note that these parameters are stored in registry on the computer where the Demand Plan Server is running. The default values will be written into the registry the first time the demand server is started and ended on the server PC. Note that all these registry settings MUST be changed with care. Do not change unless you are absolutely sure of the changes. The default key values are written to registry after the Demand Server has been started and closed for the first time.
Note that the default values are based on the server running on MONTHLY PERIOD VERSION. If the server is intended to run on other period versions then you should consider changing some of the values in the registry. The parameters should then be changed to:
The best fit search limits for the different forecast models should be changed to represent the new selected period version.
Note that the Demand Plan Server must not be running while you are changing the parameters.
There exists more parameters than the ones described in this document, these parameters should not be changed without discussion with an an IFS consultant.
Note that if you are running the 32 bit version of the Demand Plan Server on a 64 bit system the registry key is a little different that mention under it will be HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IFS\ForecastServer\3.0\.. instead of HKEY_LOCAL_MACHINE\SOFTWARE\IFS\ForecastServer\3.0\.. Note that there exists an 64 bit version of the Demand Plan Server if you use this you get the same registry keys as described under.
Used to store Applet data. This is set from the Demand Plan Server setup dialog.
Used to store Approval data. This is set from the Demand Plan Server setup dialog.
For Demand Plan Server internal use. This is used to manage backups, and keep track of where the most recent backup is. Do not Change.
Used to store limits for some of the different demand classes that the different parts are divided into. See Part Classification.
Used to store Demand Plan Server & Demand Plan Client communication details. This is set from the Demand Plan Server setup dialog.
Stores everything about the communication between the Demand Plan Server and the Oracle database. Most parameters are set from the Demand Plan Server setup dialog. The parameters not set in this dialog are :
InventoryValue: Used for compatibility with older IFS Applications versions e.g. IFS App 99. If left empty, the Demand Planning Server will use the INVENTORY_PART_API.Get_Inventory_Value_By_Method(CONTRACT, PART_NO) function for reading inventory values, this function was created in IFS App 2000b and newer. If you want to use some other function then type in the wanted function / field in this key. E.g. INVENTORY_PART_COST_API.Get_Total_Standard(CONTRACT, PART_NO, 1) is used to retrieve inventory value in IFS App 99. Default value is empty. This is a flexible solution that allows easier loading of different numbers into Demand Planning.
WeightValue: Used for Flexible loading of the weight number. If left empty the Demand Planning Server will use the INVENTORY_PART_API.Get_Weight_Net(CONTRACT, PART_NO) function for reading weight values. If you want to use some other function then type in the wanted function / field in this key. E.g. INVENTORY_PART_COST_API.Some_Function(CONTRACT, PART_NO, 1) . Default value is empty.
SalesPriceValue: Used for Flexible loading of the weight number. If left empty the Demand Planning Server will use this and then read the cost set that is defined by the SalesPrice_CostingSet. If you want to use some other function then type in the wanted function / field in this key. E.g. INVENTORY_PART_COST_API.Some_Function(CONTRACT, PART_NO, 1) is used to retrieve inventory value in IFS App 99. Default value is empty.
Note that none for the 3 functions above (InventoryValue, WeightValue, SalesPriceValue) needs to be prefixed with the appowner user the DP serve will do this automatically.
SalesPrice_CostingSet: Used to set a cost set that will be used as sales price in Demand Planning. Simply state the cost set to be used e.g. 7. Default value is empty. Only active if SalesPriceValue is empty.
NumberOfRecordsReadInAgg-Qual: Read buffer size when aggregating and qualifying parts. default 100.
ReadFlowByFlow: Reads parts flow by flow instead of reading all forecast parts at once. default false (0). Reading flow by flow will reduce the rollback segment size.
Used to store Demand Plan Server Help files, language files and log file directory, that is set from the Demand Plan Server setup dialog.
Used to store the different fonts used in Demand Plan Server. Needs to be changed if you are translating the server to Japanese or other languages including signs instead of letters. See Release notes for more details.
Used to store all the different limits for the best fit forecast parameter search. Note that if you are using another period version than monthly, you should consider this when changing these parameters. See Forecast Models for details. It is important to UNDERSTAND how the models work BEFORE you make any adjustments to the default values.
BayesianInitPeriods: How many periods of history do the part need to have before the bayesian forecast model starts to run, Moving average (over all periods) is used as forecast model before this limit is reached. Default value is 0.
CleansingMethod: 0=No data cleansing, 1=clean data according to the Standard derivation method. See Data Cleansing for details.
MSRCleansingMethod: 0=No data cleansing, 1=clean data according to the Standard derivation method when computing MS. See Data Cleansing/Forecast Accuracy for details.
SystemProfileAlpa: Default value 0.2, alpha value used for period profile and weekly profile making, it is the smoothing constant used when adding/smoothing the new profiles to the old profile after the create forecast job is ran. The adding is a EWMA process with this alpha.
Used to store Demand Plan Server mail communication details, is set from the Demand Plan Server setup dialog.
Used to store all the different limits for the automatic season profile & the Automatic season profile generation algorithm See Season Indexes for details.
DatabaseTreads_LoadIPR: Tells the Demand Plan Server how many database sessions (Treads) that it is allowed to use during the load IPR data session. Generally the more sessions the DP server is allowed to use the faster will the total job process run. NOTE: Running multiple treads come with a cost for all the other database jobs running on the Data Base server. Default is 1. Note there is no point having more threads that you have sites that should be calculated by the IPR Engine.
DatabaseTreads_Demand: Tells the Demand Plan Server how many database sessions (Treads) that it is allowed to use during the loading of Demand Planning data. Generally the more sessions the DP server is allowed to use the faster will the total job process run. NOTE: Running multiple treads come with a cost for all the other database jobs running on the Data Base server. Default is 1. Note there is no point having more threads that you have base flows in you Demand Plan setup.
DatabaseTreads_UpLoad: Tells the Demand Plan Server how many database sessions (Treads) that it is allowed to use during write back of data from the Demand Planning Server. Generally the more sessions the DP server is allowed to use the faster will the total job process run. NOTE: Running multiple treads come with a cost for all the other database jobs running on the Data Base server. Default is 1.
MaxWritebackBuffer: Tells the Demand Plan Server how many records that is the max limit for the write back buffer, to put a limit on this buffer will reduce the amount of memory needed by the Demand Plan Server. But it will increase the running times of the Demand Plan Server jobs. Default setting is 0 which means that no limit is set on this buffer.
EnableJobRunner: Used to turn on and off the job execution. When 0, no scheduled jobs will be executed. If set to 1 then all scheduled jobs are executed normally. This is useful when looking at backup files from customers and when you don't want scheduled jobs to be started, so as to avoid updating the customers database or to avoid error messages because you don't have access to the customer database. Default is 1 (TRUE).
FixedDate: Used to get the Demand Plan Server to always think it is this date regardless of the date time of the Data Base server and the system time of the machine it is running on. Nice to use to freeze the time when using demo data sets etc. Default is empty, then it will look at the UseTime variable to determine the date/time. NOTE During line operations this fields should ALWAYS be EMPTY!
Mode: Internal DP Server layout variable, should never be changed.
IPRLoadRecordCount: Internal DP Server layout variable, should never be changed.
LoadRecordCount: Internal DP Server layout variable, should never be changed.
OutlinerSmoother: Used to smooth (EWMA this is the alpha value in the model) outlier values to create an sorted outlier list. See Sort By Toolbar. Default is 0,25. Must be an value between (0 - 1.0).
LogLevel: Defines how detailed the server log file should be. 0-All messages are logged, 1-Moderate and Severe messages are logged, 2-Only severe messages are logged.
UseTime: TRUE or 1 if you want the server to use the Server PC time and date, FALSE or 0 if you want to use the Oracle time as time variable. Default is FALSE 0.
LoadInventoryHistory: TRUE or 1 if you want the server to load historical transactions when running IPR. This will historical data will turn up in the IPR Excel sheet. Default is FALSE 0.
LeadTimeMethod: Tells how the server should treat the parts lead time. The lead time can determine when you start saving the parts historical forecast, so that the forecast error measures (MAE, MAPE...) are measured how well you forecast the parts demand one lead time into the future instead of measuring the next forecast period only.
Default is value 0.
TraceLevel: For IFS Internal use only. Used to give out different performance measures. DO NOT CHANGE!
Trace: For IFS Internal use only. Used to give out different performance measures. DO NOT CHANGE!
OnlyLoadSite: When specified the IPR Module will only load data for this site. Default is empty which means that it will load all sites.
SimulationBackOrders: .When set to 1 the simulation run will accumulate negative demand when the simulated inventory on hand gets below 0. When set to 0 The simulated inventory on hand stops on 0 and does not go negative. Default setting is 1 = backorders activated.
SimulationLengthYears: Defines how many years the simulation should last. Default is 5 = 5 years.