For a better overview, a central location for the higher-level logging has now been created under "Planning protocols". First of all, some changes (creating, moving, deleting) to folders and scenarios have been summarized there, others will be integrated here later.
In the logs / messages after executing the "BI deployment" in the scenario or from the planning monitor, the number of data records is now formatted with a thousand separator.
In the search function (called via CTRL + F), the default setting is that all reports in the scenario are searched and not just in the sheet that is currently open. The previous function is retained and can be used further via "Search: Sheet" and "Search in: Formulas".
In order to enable the hierarchical display of scenario and folder structures without any problems, the backslash ("\") should be dispensed with in the designation in future. The text field is marked in red as you enter it.
In SAL, IC and CNT formulas, an account list can now be specified instead of a single account. To do this, enter the accounts in your formula in round brackets and separated by semicolons, e.g. SAL (('54210'; '54230'); '03.2020'; 'F4'). The result is then the sum of the formula applied to the individual accounts. The sign results from the D / C indicator and the lowest BilGuV indicator of the specified accounts. In the same way, an item list can be specified in POS formulas. Account lists are not possible for MSAL and MIC formulas.
In the scenario you can now activate display of cost of sales method with a switch. All reports with the "C" indicator can then be selected. If the accounts are created for such a report, the controlling indicator of the POSKTO assignment is evaluated by IDL.KONSIS. If one is available, an additional (cost of sales method) account with the designation "<Account no> _ <ControllingObjectID>" is created under the item for each controlling object with this indicator. The controlling balance of the account or the controlling object is then located here. In line with this, only the balances that have been assigned to the corresponding controlling object are loaded for "I" accounts. When balances are written, the account balances of the additional accounts are saved as controlling balances, the "IC" balances are saved with the associated controlling object. The total of the balances of all additional accounts derived from the same account is saved as the account balance.
The additional accounts are treated in the same way as other accounts in rules etc. (except: balance import and export). In the balance deviation display, the deviations with regard to the additional accounts are displayed as if they were regular accounts from IDL.KONSIS. "Update / write account balances" therefore also updates / writes the (according to IDL.KONSIS interpretation) controlling balances, because they are managed as account balances in IDL.FORECAST.
Please note the following restrictions: The display of cost of sales method cannot be activated at the same time as controlling. Because the IC counter planning (ICGP) does not evaluate any reports and therefore cannot create additional accounts, it cannot be used together with the cost of sales method support. Only one controlling dimension can be activated for each account for which the additional accounts are to be generated. The additional accounts must not be included in the scenario together with their original account from which they were derived. There is no link between such pairs of accounts to ensure that they remain consistent. They would then possibly be added twice to the result.
The plausibility check when executing rules has been extended. The message "Total not equal to 100%" is given if e.g. parameters or statistical accounts that are used to split a balance do not add up to 100 percent. The message is also displayed if e.g. payment terms <100% can be determined and until this release only a warning has been displayed when creating the rule in the wizard.
The message "Invalid value" is issued if a parameter or statistical accounts assume values during rule execution that would be incorrect when the rule was created in the wizard (e.g. empty).
In certain cases there is no need to report a plausibility check, e.g. if the BilGuV indicator differs (1/2 or 3/4), if there are only expense and income accounts. The simplification applies to the following rules: expense rule, material rule, sales rule, revenue rule, personnel rule, provision rule, tax rule.
When the rule wizard is opened, the interface is now locked until the wizard has been fully loaded and the corresponding Windows animation of the mouse pointer is displayed.
When entering percentage values for all rules with conditions of termination / payment, the cursor will now automatically jump to a second new line, if a percentage <100 has been entered beforehand. In this way, the next percentage value can be entered directly. The suggestion is the difference to 100%.
The planning monitor has been expanded and redesigned. It now contains two tabs, the planning monitor with information about the status of the scenario and the new tab "Process" with the process and parameter settings.
With the new execution groups, a flexible instrument for automation has been added. A so-called execution group (new) can now be created on the top level in the Process tab. Here you can easily assign the required companies, the process and the parameters to be used. You can also define several run-time groups. A company can be entered in several run-time groups (with the same or different parameters). The entire run-time groups can be set independently of the scenario (across the board). When you start a run-time group, the run is processed in the order entered.
During the migration, a runtime group is automatically created for each existing scenario and the previous process / parameters for the corresponding companies are stored there.
An additional selection option has been created in the planning monitor in order to be able to select the period and data type of the group structure.
In order to avoid accidentally starting unwanted actions, the message "Scenario may not be up-to-date" is now displayed in the planning monitor after changing a scenario. Actions are only released again after an update.