The LucaNet? controlling and planning suite features prominently here on the B1 blog, as it is a perfect complement to SAP ERP for SMEs via a 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 take place via the Excel Add-in (Ctrl+B from Excel) or via a data import to LucaNet with a prepared Excel Reporting Package. We will take a closer look at the transfer path via the Reporting Package here.
In general, it can be said that the way via Excel is more maintenance-intensive. On the one hand, this is due to the fact that LucaNet is accessed indirectly through another medium and, on the other hand, to known Excel weaknesses such as the manual creation and maintenance of references and formulas.
With 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 for the data update. With the Excel solution, these references to historical data must first be created via 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 formulaic derivation of the order backlog. In the LucaNet planning forms, these possibilities are limited because the functions are fixed and follow a row and column-oriented template.
It should also be mentioned that a LucaNet planning form is always created per company code and then copied to other company codes if necessary. This can also mean a higher maintenance effort in the case of subsequent changes to the planning forms.
Please see the individual advantages and disadvantages in detail in the following list.
|1||Year, quarters transferred flexibly||yes||technically only months possible (year, quarters via Excel formula)|
|2||mirror movement types are to be indicated 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|