A calculation unit represents a financial/business unit on which Financial Closing and Analysis can be performed independently (for example, Claim, Asset, Insurance, and so on).
A calculation unit is a container function. It specifies which fields are relevant for lower-level business functions, which business functions are relevant for execution, and which business functions are relevant for analysis. It is a collection of objects, such as fields and functions.
An environment (link) is necessary for creation of a calculation unit
A calculation unit is an important tool that helps you to organize the execution and analysis of financial activities within a Financial Organization Unit.
This function supports the following functions:
Organize a field catalog that is necessary for all functions within a calculation unit. This catalog represents a superset of all fields that will be used by each and every function modeled beneath the calculation unit
Define an input template. An input template is a template hierarchy of parameters that a Financial Analyst (business user) can use to analyze business content within a calculation unit. This template consists of parameters and data editors.
The parameters influence the behavior of, or filter the results of functions below the calculation unit at runtime. For example: Consider the business case to analyze the profitability of an organization unit every quarter. For such a scenario, a business model can be designed by the ‘System Controller/Modeller’ (expert user) on the basis of a parameter ‘Period’. This parameter value can be specified by the financial analyst (business user) in the runtime environment without the need to regenerate the models.
The data editor enables the financial analyst (business user) to plug in different sources of data for a Model at runtime and analyze the application for varied inputs.
Define an output template. An output template is a template hierarchy that contains a list of functions that are relevant for ‘analysis’ by the financial controller (business user). There are certain functions that are primarily used for reporting and analysis. The ‘System Controller/Modeller’ (expert user) can choose which of the functions is relevant for analysis by business user through the hierarchy of such functions.
Define a run template. A run template is a template hierarchy that contains a list of functions that are relevant for execution by the financial controller (business user). The ‘System Controller/Modeller’ (expert user) can enumerate the list of functions that can be analyzed by the financial analyst (business user) in the runtime environment. For example. The ‘System Controller/Modeller’ (expert user) can design certain ‘intermediate/technical’ functions to accommodate effective reuse of the function for various use cases. Once the performance management environment is modeled, the ‘System Controller/Modeller’ (expert user) can choose which of the functions is relevant for execution by the business user. This ensures separation of responsibility and ensures a clean end user interface based on the nature of the end user.
Select Add Rule in the Function Hierarchy of the environment
Choose the function type Calculation Unit and choose OK.
The details screen consists of four roadmap steps:
Roadmap Step 1 - Fields
Choose Add fields and select the list of fields that are available in the parent environment or calculation unit. Only these fields would be visible for functions within this calculation unit
In the dialog box, select the fields from the Parent Environment and Calculation Unit.
Click OK to add the fields to the current calculation unit
Once the fields have been added to the current calculation unit, they are available for use by the underlying functions
Roadmap Step 2 - Input Template
Choose Add fields to choose the list of fields and parameters that are relevant for input in the runtime environment, These are the parameters that can be entered by the financial controller
The dialog box shows the list of fields mentioned in Roadmap Step 1. The fields can be selected.
Click OK to add the fields to the input template
Choose Add Nodes to create a logical grouping of the fields.
Roadmap Step 3 - Output Template
Choose Add to choose the list of functions that are relevant for output that can be used by financial controller
Choose Add to choose the list of functions to be analyzed by the financial controller
In the dialog box, choose the list of functions that are relevant for execution in the analysis environment
Click OK to add the functions to the output template
Roadmap Step 4 - Run Template
Choose Add to choose the list of functions that be executed by the financial controller.
In the dialog box, choose the list of functions that are relevant for execution in the runtime/execution environment.
Click OK to add the functions to the run template