LucaNet has already been presented here in the SAP Business One blog a few times. We often realise that LucaNet is mainly used 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 Intercompany planning to be mapped. However, the dimension can also include Regions or countries can be created as a characteristic. This is then used to drill down and plan sales planning 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 a super-group of "China, Japan and Korea" as a sub-group).
P&L, financial and balance sheet planning
In addition, the planning is in a closed business context. Calculation cycle from P&L, financial and balance sheet planning are available. In addition, only a few planning rules need to be defined, for example, that a certain "sales revenue" account is deferred to the trade receivables balance sheet account. Furthermore, investments with AfA rules and Loans with exact interest and repayment are planned. In this way, a budgeted balance sheet (with a balanced balance sheet total) is always automatically included - please see >Debit planning below.
[rev_slider Lucanet_Plan]
Planning forms and/or Excel integration
The planning data can be entered in LucaNet itself in Planning forms are recorded or from any pre-systems be recorded. This naturally includes, in particular MS Excel by means of a comfortable Add-ins. As Excel is used by many companies as a basis for planning, existing planning data is often transferred to LucaNet using 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 until the end of the planning period (with percentage adjustments if necessary). There is also a Seasonality assistantswhich distributes the values planned 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 include the option of setting certain parameters such as the Calculate the cost of sales (as a percentage proportional to sales). This can also include, for example, the Automatic calculation of income taxes be. These dependencies can be manifold and can also occur, for example, 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 expense. The expenses can be planned individually for each employee. Contribution assessment bases can also be taken into account.
Comfortable forcasting
That forecasting is very 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 is thus mirrored. For the remaining planned months, "old" planned values can now be adjusted beyond a purely mathematical forecast. 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 quickly possible, i.e. "previous year-plan-actual".
Top-down planning
In principle, LucaNet analyses the data at account level (the data from the actual system is initially leading). For planning purposes, however, a certain Top-down planning be made. This means that the Plan values at condensed level The cost type group "Personnel expenses" and not the account "Expenses for wages & salaries", for example.
Cost centre accuracy in all freedom
In addition, in LucaNet accurate to the cost centre be planned. Deviating from the existing actual model, additional structural elements can be created in the company organisation. There does not necessarily have to be a match 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 subledger is then transferred to the trade receivables in the balance sheet transferred.
Plan all statistical data
In general, all statistical data such as personnel figures, quantities or room sizes in sub-ledgers (with or without transfer to 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
Once corporate planning has been finalised, it can be legally consolidated at the planning 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 Intercompany accounts was planned.
Other aspects of planning in LucaNet are:
- Simulation option due to Exchange rate changes
- Turnover planning can be done through quantity and price calculation
- Assistant-supported interest on current accounts
- Direct liquidity planning
Secure liquidity with SAP Business One
Budgets in SAP Business One
Optimisation of the integrated financial system
Financial consolidation with SAP Business One
Return rates - on the trail of returns
