FAQs

What happens if certain entity/template combinations are mapped to a Simulation Engine process, but new entities are added to the application?

The simulation engine only processes the entity / template combinations defined. It is possible to map parent level Budget Entities to the process. In this case, new Budget Entities of that parent will be included. For the Simulation Engine to process a Budget Entity / Template combination that combination must be a valid mapped combination at the template level.

What happens if a template is marked “complete” and/or the entity has been forwarded?

If you manually go to those entity templates you cannot make any changes without sending the entity back and marking the template “not complete”. Even reference accounts are not updated unless you mark the template “Not complete”.

I would like to use the scheduling feature log of simulation engine. How I can open it?

1. Navigate to Maintenance, Admin, User Management and select the Navigation Role tab.

2. Select the role in the list and then click on Navigation Access.

3. Expand the hierarchy until you see the Schedule Manager link under Maintenance, Admin.

4. Check against Schedule Manager and then click on save.

5. Refresh the Planful application window by using F5 (Function F5 key in your keyboard) or re-login in to the application to view the link under Maintenance, Admin.

What is the limit of business entities that can be set up in a scheduled simulation engine?

There is no limit to the number of template-entity combinations you can process in a single scheduled Simulation process for all templates types.

Generating a high number of template-entity combinations in a single schedule may not be as effective as creating several individual Simulation processes when it comes to the overall turnaround of the process and eventual report delivery.

What do it I do if a Simulation Engine task has a very slow run time and/or crashes Internet Explorer?
It is important to ensure that you have deleted your temporary Internet files/cache.

Why, after seeding a scenario no data is showing for the new scenario in reports?

When seeding data from one scenario to another scenario, as soon as a template is opened the seeded data is pulled into the template, but will not be available for reporting until the template is saved. Once the template has been saved, the seeded data that was populated from the original scenario will be available for reporting.

Do summary templates need to be saved and the scenario processed before the seeded data can be viewed in reporting?

If the data is spread across multiple entity/template combinations the Simulation Engine can be used to automatically save the template for specific scenario & for selected budget entities. To do this, navigate to Maintenance, Rules, Simulation Engine and create a new process for the relevant entity/template combinations. Run the process and then process the reporting cube for the selected scenario. With these steps completed the data will be available in reports.

Can I use the same simulation process for multiple scenarios?
Setting up your processes within the Default scenario allows you to map the process to multiple scenarios. To map a process from the default scenario, select the scenario you wish to map it to from the drop down box within the Process List. Click the "Copy from Default Scenario" button. In the pop-up box choose the processes that you wish to copy from the Default scenario and click save.

If I am in edit or setup mode and save my template containing data for a scenario, will my data save to the destinations mapped?

No, saving the template in this mode will only save the structure. To write the data to the mappings you have created, you will need to save the template while in Input mode in the Planning Control Panel or run a Simulation Engine process for the template, scenario and entity combination(s).

How do I know if my Simulation Engine process has successfully completed?

• Process Log – the Process Log is available for Processes run locally

• Notifications – can be setup to provide email alerts for both successful and failed scheduled processes. By default, the user creating the process is notified, but other users can be added.