LucaNet has already been presented here on the SAP Business One blog a time or two. We often find that LucaNet is used mainly as a Consolidation tool is seen. But it is also a powerful planning tool.
Reason enough to take a closer look at the planning functions.
Any number of data levels for planning
LucaNet as multidimensional system offers a ready-made data model with a fixed number of dimensions. This includes the dimension Data level. In addition to actual values, any number of data levels such as Base Case, Best Case, Worst Case and Forecast 1-4 etc. can be created. Depending on when these planning data levels start on a time line, they automatically mirror the accumulated actual data (purely mathematical forecast). This automatism exists in many OLAP-databases - please see >Forecasting below.
Intercompany planning for countries and regions
Furthermore offers LucaNet with the dimension ?partner? the possibility of predominantly having a Intercompany planning to be depicted. However, the dimension can also include, among other things Regions or countries can be created as a characteristic. This is then used to break down and plan turnover plans accordingly. With LucaNet version 10 (since the beginning of this year) it is now also possible to create groupings or hierarchies (for example, "Asia" as the upper group of "China, Japan and Korea" as a subgroup).
P&L, financial and balance sheet planning
In addition, the planning is in a closed loop from an economic point of view. Calculation cycle from P&L, financial and balance sheet planning are available. In addition, only a few planning rules have to be defined, for example, that a certain account 'sales revenue' is accrued to the balance sheet account 'trade receivables'. Furthermore, investments with AfA rules and Loans with exact interest and repayment be planned. In this way, a budgeted balance sheet (with a balanced balance sheet total) is always automatically included - please see below for >Debtor planning.
[rev_slider Lucanet_Plan]
Planning forms and/or Excel integration
The planning data can be stored in LucaNet itself in Planning forms are recorded or from any pre-systems be played in. This of course includes, in particular MS Excel by means of a comfortable Add-ins. Since Excel is used by many companies as a basis for planning, existing planning data is often transferred to LucaNet with the add-in. However, we ourselves also consider the planning forms to be an excellent alternative.
Practical assistants
In the planning forms, you will find a forecast or a Data Update Wizardwhich - for example - refers to the accumulated actual values and then updates the data (with percentage adjustments, if necessary) until the end of the planning period. Furthermore, there is a Seasonal assistantswhich distributes planned values on an annual basis to the months according to a key (this key can be adjusted graphically in a bar chart).
Planned use of goods
Other planning functions in LucaNet and part of the planning forms are, for example, the possibility to determine certain variables such as the Calculate the cost of sales (as a percentage proportionate to turnover). This can also include, for example, the Automatic calculation of income taxes be. These dependencies can be manifold and can, for example, also occur in the intercompany-The planning process should be based on the leader-follower principle.
Personnel planning
One Personnel planning can be carried out in such a way that average values are stored, which result in a planned personnel expenditure. The expenses can be planned individually for each employee. Contribution assessment bases can also be taken into account.
Comfortable forcasting
That forecasting is quite simple in LucaNet because, as mentioned above, the actual data is always "taken along" during the year. This means that the data level Forecast (among others April-December) is created by copying the base plan. Up to the current reporting month March the actual data are thus mirrored. For the remaining months of the plan, "old" plan values can now be adjusted beyond a purely mathematical forecast. plan values can be adjusted. The system also supports rolling forecast scenarios.
Plan-actual comparisons at all levels
Planned/actual comparisons are quite simple in LucaNet by integrating several data levels (e.g. plan and actual) into an existing P&L (an absolute and percentage deviation column is created as a column for this purpose). In this way, every existing evaluation can be created as a plan/actual comparison. In this way 3-way comparisons possible quickly, i.e. 'previous-year-plan-actual'.
Top-down planning
In principle, LucaNet considers the data at account level (the data from the actual system is initially leading). For planning purposes, however, a more or less Top-down planning be made. This means that the Plan values at condensed level The costs must be recorded or entered in the "Personnel expenses" cost type group, for example, and not in the "Expenses for wages and salaries" account.
Cost centre accuracy in all freedom
Furthermore, in LucaNet accurate to the cost centre be planned. Deviating from the existing actual model, further structural elements can be created in the company organisation. Therefore, there does not necessarily have to be agreement between actual and planned structures.
Debtors in a statistical area
Another new feature in LucaNet version 10 is that payment targets can be set not only for accounts but also for previously created accounts. accounts receivable can be planned in a statistical area. The planning data from this sub-ledger is then transferred to the trade receivables in the balance sheet transferred.
Plan all statistical data
In LucaNet, all statistical data such as staff numbers, quantities or room sizes can be stored in sub-ledgers (with or without transfer into the ledger) can be planned. This enables the mapping of metrics (turnover per employee) as well as other planning steps such as apportionments, allocations and all other planning logics.
Legally consolidate planning data level
If a business plan is finally available, it can then also be legally consolidated at the plan data level. The consolidation logic does not have to be "reinvented" because it is already used for the actual data. What is important here is that partner-related or at the Intercompany accounts was planned.
Other aspects of planning in LucaNet are:
- Simulation possibility due to Exchange rate changes
- Turnover planning can be done through quantity and price calculation
- assistant-supported interest on current account
- direct liquidity planning
Budgets in SAP Business One
Optimisation of the integrated financial system
Financial consolidation with SAP Business One
Return rates – on the trail of returns
More key figures transparency in the ERP system
