What To Do Once Template Setup is Complete?

Template mapping is required in order to make a template accessible in the Planning Control Panel. Specifically, templates must be related or mapped, to budget entities, approval roles, and scenarios to be accessed. 

Templates are initially created and designed at the default scenario level. After creating the template, it is mapped to Budget Entities and assigned to Approval Roles. The templates in the Default scenario are considered master templates, so they are the latest version of the template, which can then be mapped to working scenarios for data input by users. It is best practice to map the template to budget entities prior to mapping to a working scenario, as it will ensure the appropriate budget entity mapping is always copied over to the working scenario. 

• Budget Entity mapping makes a template available for the selected budget entities. Only the budget entities mapped will have the template linked to, or available, for either input or review. 
• Approval Roles define what the user can do within the template – view, input, mark complete, or mark not complete. Individual users are assigned an approval role within User & Role Management before mapping to a working scenario, as it will ensure the appropriate budget entity mapping is always copied or in the template setup. Three pre-defined approval roles are available by default in applications. 
• Template Mapping to a working scenario is done after the Budget Entity and Approval Role have been mapped. This is the final step to provide template access within the Planning Control Panel. The Default Scenario template is considered the Master Template and by mapping the template to a working scenario you have essentially created a copy that users will be able to access through the budget entity within their security permissions in the Planning Control Panel.

Once templates and scenarios are created, access must still be provided to individual users for them to be able to view and plan. In regard to Structured Planning specifically, users must be granted access to scenarios, templates, and entities. 

• Scenario access ensures that the user will see the scenario available to them within the Planning Control Panel drop down. You can grant users access to one, many, or all scenarios. T
• Approval Role Setup grants both template and entity access. The approval role setup consists of two components – levels and role. The number of levels will be determined by the number of rollup levels within the budget hierarchy. Access can be granted at any level within the budget hierarchy, from the entire hierarchy to just one budget entity. Multiple lines can be added if users need access to multiple entities. The level assigned will determine what budget entities the end user has available to them. The role is where specific approval roles will be assigned to users for each level of access. The approval role will determine what level of template access the user has for that specific level.