Demantra init_params_table_name in forecast_history table
Experts, I had a few clarifications regarding running the Engine on Linux for different profiles—would appreciate it if you could kindly confirm the following:
- To run the Engine for different profiles, our understanding is that the commands should be structured as follows. Could you please confirm?
- For Batch or Base mode:
<COMMANDLINE>/xxxxx/demantra/Engine/bin/Start_Engine2K.sh</COMMANDLINE> - For Bookings Forecast (Engine profile ID: 100):
<COMMANDLINE>/xxxxx/demantra/Engine/bin/Start_Engine2K.sh 100</COMMANDLINE>
2. When the Engine is executed, we understand that the forecast_history table’s init_params_table_name column should be populated as follows:
Tagged:
0