@Tim: While I understand the need, the current situation should not be a showstopper for not using the Fiori Cockpit. Their Process Flows are not customizable either so you customer should have the same options with our current offerings

Our customer will be very happy to see if they are able to customize the process flows. I believe this is something many customers will love to see this feature as they can't edit the B1 process flows.

Thanks Rasmus. Indeed a wonderful news. I am sure our customer will be very excited about it. BTW, we have a challenge to use the process flow. it is slow if compare to the Fiori cockpit. Is it normal?

Could you please elaborate what you mean by that (in what way are they slow?)... During startup they take a second or two to render visually but beyond that the only real thing they do is to press menu-items on your behalf so they should be just as fast/slow as Pressing the menuitems in the main menu.

Hi Rasmus, The dashboard loading is slow. Basically, anything to do with the dashboard is slow e.g. click the dashboard menu items are slow. I have installed on my local machine which is running on SQL and it is reasonable fast. The customer that I am testing is using HANA. Occasionally, I am getting the following error. And also, I noted some of B1Up configurations are slow in HANA if compare to SQL. Do you have any customers who are using HANA reported the B1Up is slow for some of configurations. The dashboard is just real slow. You can remotely take a look if you wish as to show you how slow it is.

It is a known fact that in pure performance then HANA is slower than MSSQL (MSSQL having a 15+ year in optimizing the database engine). Where HANA shine is in not having as many database locks so more people at the same time can work without deadlocks.

When it comes to dashboards there are 3 steps in loading them:

Step 1: Initialization

This step is a load of DLL files into memory. The dashboard has some fairly big DLL files (200mb) so it takes some time to load this (HDD speed and CPU being the factor that impacts how fast it can be done). But on 2 identically machines; one running MSSQL and one running HANA this time should be 100% the same

Step 2: Data Retrieval

This is the step that will take longer on HANA. HANA requires more hardware to be as fast as MSSQL and in your test-case you get the data from a local source taking the Network out of the equation. In this step we are not really doing anything so the speed here are purely determined by HANA and Network.

Step 3: Data Visualization

This is the step we turn the data into charts and pie-elements. This is done 100% the same on both HANA and MSSQL so no difference there.

***

When it comes to UI-API the system is also 100% the same (there is a tiny bit of database communication but not much) so the speed of pressing a common function or a process flow should be exactly the same speed as if you did it from the SAP Main Menu (UI-API have a tiny overhead, but normally measured in milliseconds)

So base on what you have sent it sounds like is the HANA system is slow that it perhaps is under dimensions Hardwarevice and other operations like add Invoices etc. are also slower than on your local machine.

***

As for the error message, It is no and error we have seen before, and looking at the code I can't see a logical reason how this error can happen, but I've adjusted the code to not throw the error should it happen anyway as it is a non-critical operation that fails.

***

But we can't fix that HANA, in general, is slower than MSSQL. That is for SAP to fix...

Thanks Rasmus for clarifying it. Every developer is telling me the same thing. Thank you for breaking down and well explained.

And also, we noted one thing that is very strange. Saving B1Up UF is slow. It will take 3-5 seconds. Saving B1 documents will take only 1-2 seconds. Is there anything that you can suggest where we can look it as why saving B1Up configuration (UF) is slow?

If you make a such and share the files with me I can see what takes time while our code run.

If it shows slowness in getting the data from the screen (UI-API) it is poor Client machine performance (bad CPU)

If it shows slowness in getting/saving data to the database it is poor HANA performance / bad network performance (but we will not be able to tell you which of the two)

If it shows slowness in the Boyum Logic Code it indicates that we have poorly written code

It tends to be (2) in most HANA cases and (1) in almost other cases... In rare cases it is (3).

***

Another "good test" is the "Make new DB test"... Simply go to the database selection screen and create a new empty database. In good systems that operation take 2-3 min... In poor systems it take much longer.... This test test the pure SAP Performance when it comes to HANA and Network

Thanks Rasmus for the suggestion. I have tried to create a new empty database and it is taking about 7 mins. I guess it is pretty bad if you are talking about 2-3 mins for good systems. It takes a long time to create a UDF as well.

I can go back to talk to them by mentioning 2-3 mins for good systems.

The 2-3 min tests I've done was on MSSQL. Never had a production HANA system where I've tested myself so do not know is 7 min is good or bad (only that I've tested on small internal test-systems and there an new HANA db takes 20 min so 7 min is at least not super terrible I guess)

But try and create the Performance Profiling... That will give the most accurate measurement in terms of B1UP

Tim Wong Sorry for the delay in checking ticket 93618... I can see the Profiling the was the execution of Dynamic Code and Execute of UFs... So they can't really tell why you Dashboards are slow...

So could you please make a profile that is using the Process Flow (Start Profiler > Click on a single Process Flow Entry to open a screen > Stop the profiler and send it to us (give it ticket number 999991)). Then reply back here so I know it has been uploaded.

Our customer's dev server is reasonable powerful as the following server spec. The SAP B1 client is running reasonable quick for updating and adding. As for the dynamic code UFs, it is running reasonable fast in SQL environment. It is slow when we run it in our customer's dev server with Hana DB. I noted it is even slower when your UF calling a few UFs to do something. For example, in your UF, you call another macro to do something. Within the macro, you call the .Net to return something. Each calling will slow down the performance.

I don't really know how to help. As Mention SAP Business One is just by definition slower than MSSQL and Windows servers running SAP Business One is also by definition slower than working on desktop machines... I've been asking SAP for years why that is and they can't give the answer... And the profile shows that it is not the B1UP logic that is the contributing factor to the slowness; it always comes down to the UI-API and DI-API calls and there we can't be faster than SAP allows

I'm not sure what testing you refer to... Internally Boyum curremtly have 3 main HANA systems. One on 9.3 PL10, one on 9.3 PL13 and one on 10.0 PL01... But they are all tests system and are not used for production so they are all quite underpowered compared to the amount of users so they can't be compared to Live systems

Thanks Rasmus. Our development server is pretty powerful. One part that I don't understand is loading standard B1 form with data is relatively quick (less than a second) but when we open B1Up UF is slow in loading the data. For example, go to B1 Validation Configuration Screen and click UF golden arrow key. It will take around 7-8 seconds to get UF screen with data. The UF screen pop-up very quickly then it will take 7-8 seconds to load the data. Saving the UF is about 4 secs. Any ideas why B1Up is slow in loading and saving?