The LucaNet controlling and planning suite features prominently here on the B1 blog, as it is a perfect addition to SAP ERP for SMEs thanks to its fully integrated interface to SAP Business One.
With reference to our article "Not only consolidate but plan with LucaNet", today we want to compare two technical options for transferring planning data to LucaNet:
- with LucaNet planning forms
- with Excel
The transfer with Excel can be carried out via the Excel add-in (Ctrl+B from Excel) or via a data import to LucaNet with a prepared Excel Reporting Package. We would like to take a closer look at the transfer method via the Reporting Package.
In general, it can be said that the route via Excel is more maintenance-intensive. This is partly due to the fact that LucaNet is accessed indirectly via a different medium and partly due to known Excel weaknesses such as the manual creation and maintenance of references and formulas.
In the LucaNet planning forms, on the other hand, direct reference can be made to existing actual data, which then serves as the basis for planning. Planning assistants such as the forecast assistant can be used to update the data. With the Excel solution, these references to historical data must first be created using the Excel add-in (Ctrl+Q from Excel).
On the other hand, Excel as a pre-system naturally offers possibilities to provide individual planning aspects such as the formula-based derivation of the order backlog. These options are limited in the LucaNet planning forms, as the functions are predefined and follow a row and column-orientated template.
It should also be mentioned that a LucaNet planning form is always created for each company code and then copied to other company codes if necessary. This can also mean more maintenance work if subsequent changes are made to the planning forms.
Please see the individual advantages and disadvantages in detail in the following list.
Planning forms |
Reporting Package | ||
| 1 | Year, quarters flexibly transferred | yes | technically only months possible (year, quarters via Excel formula |
| 2 | mirror movement types are to be specified separately as keywords | no (automatically via booking rules | yes |
| 3 | Comments in LucaNet per row/column | yes | no |
| 4 | Protect capture media | no | yes |
| 5 | Display previous year's values | yes | yes |
| 6 | Show calculated results | via update in the form | yes |
| 7 | Intercompany pass-through | yes, for credit planning | no |
| 8 | Calculations with more than one reference (e.g. order backlog) | no | yes |
| 9 | Planning assistants | yes | no |
| a | -Data update | yes | – |
| b | -Seasonality | yes | – |
| c | -Percentage changes | yes | – |
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
