We decided to put together a short guide on some of the most common performance issues you’ll encounter.

 

Now, it’s important to remember that the best way to address performance problems is to find and eliminate them before they affect users in the first place. One of the best tools you can have in your pocket is a good maintenance program. Develop a strategy for downtime and create redundancy and scaling plans. Think about what kind of user load you’ll need to handle over the next month, as well as the next year. And of course, test load regularly and monitor production performance continually.

 

However, no matter how careful and diligent you are, things are going to happen. So here are some of the common causes of web app performance problems and what you may be able to do to address them.

Problem 1: Slow Order recommendation report / APS

Solution: Try and narrow down the report by choosing smaller time period, excluding parameters, reduce selected number of items or select gross calculation to get a faster result.

 

For big amounts of data, you can run the calculation overnight in the background. You can set this up in Activities.

SAP PATH: Administration > Utilities > Manage Server

 

Problem 2: Slow Item structure expansion

Solution: Reduce the maximum of levels to be displayed to restrict the automatic expansion of large structures. See Configuration wizard.

SAP PATH: Administration > System Initialization > Configuration Wizard

CONFIGURATION WIZARD PATH: Master Data > Item > Display > Item Structure > Expand max.. levels

 

Problem 3: Menu loading time is very high

Many users mistakenly think this is a Beas performance issues, however, this is an identified SAP Business One issue which was documented in SAP Note: 1727485 (https://launchpad.support.sap.com/#/notes/1727485) which includes different steps on solving this problem. We have listed some on SAP’s recommendation below.

 

We would recommend you, in particularly, to look at Scenario3: Database corruption in CDPM or Scenario4: Database corruption in OCMN.

 

If the note above does not solve the issue, we strongly recommend for you to open a ticket with SAP.

 

Problem 4: Slow after program update

Remember, that hardware requirements increase with every SAP Business One version. If only Beas was updated, please check the following:

 

Step 1: Start Beas without SBO and test again.

 

Step 2:  Use the old version of Beas on the same Server / Data base.

If there is a significant difference in performance between the old and new version of Beas on the same data base with the same server, run checks on SQL level as it is explained in the following step.

 

Step 3: Check on SQL level

Beas contains a performance analysis tool that allows the user to deepens in the tasks executed in programs like SQL statements. In here, it can be detailed the complete statement, duration and table with results. To access to this information please follow the steps below:

1. Open the Beas - Debugger. This can be open by pressing: CTRL + “N” + “D” or by going to the option “View” > System Information in the upper side of the SAP window.

 

2. Start one of the slow operations.
3. In Debug screen choose Protocol all executed SQL statements are displayed with a blue background.

 

4. The result must be exported to an URL string and more details will be displayed. To export it, click on the icon:

 

In the file, after the SQL statement, there is the duration information:

 

5. If a SQL statement has a very long execution time, you can double click on it. A SQL window opens for further analysis.

 

6. Compare the SQL from Beas in SQL server with different compatibility modes.

 

Step 4: big Database size,

Solution: reduce the number of data sets. If a substantial amount of data had been registered, the database should be cleaned up.

In SAP Business One:  use the cleanup function

SAP PATH: Administration > Utilities > Data Archive Wizard

SAP PATH: Administration > Utilities > Master Data Cleanup Wizard

 

In Beas: Archive data

SAP PATH: Administration > Utilities > Database Test

 

Problem 5: Work order structure view slow

Reason: The reason for this is the Status information icons which can be viewed in the "Actual" column. If you have big databases, the server generally required a long time to get this information

Solution:

1. Open Window setting by right clicking on the Home Icon

 

2. Disable the "Extended status display

 

Problem 6: Beas: Opening the terminal takes a long time

Opening the terminal takes a long time if you choose specific resource in the personnel master data

SAP PATH: Human Resources > Personnel

In the terminal, the application Login Work Order will be very slow, for example:

Solution:

Disable the parameter Only Current Pool in the configuration wizard. This checkbox will only show production routing from the current pool.

SAP PATH: Administration > System Initialization > Configuration Wizard

CONFIGURATION WIZARD PATH: Production > FDC > Window Order Login > Only Current Pool

Problem 7: Other window / functions are slow

 

Step 1: Please answer the following check list

• since when is the window / function slow?
• Have you recently update SAP Business One / Beas / any other software?
• Are you experiencing performance issues in one station only or also in other stations?
• Does it happen only on a terminal server or also on a local installation?
• Does it happen with a superuser or regular user?
• Are you experiencing performance issues in one only function or more functions?
• Are you experiencing performance issue on a continuous basis or does it happen at random times?
• Have you already tried restarting the station / Terminal server / SQL Server?
• Is there a Customizing code implemented?

 

Step 2: Check Project folder connection

If the project folder is located on a shared server folder, check if you have a fast connection to access it.

 

You can test it with the following steps:

1. Set the local folder in the Configuration Wizard

SAP PATH: Administration > System Initialization > Configuration Wizard

CONFIGURATION WIZARD PATH: System > Server Directory f. customer-specific Extensions

 

2. Restart and test again

 

Step 3: SQL Server check list

 

• Check memory. This should be maximum 80% of the server memory. The memory settings are in the SQL server, by right clicking in the database and selecting Properties.

 

• Check the database settings, specifically the default locations. The default locations should be in a different disk than the operation system is installed. These settings are in the SQL server, by right clicking in the database and selecting Properties.

 

• Shrink the data and log files. These files are in the SQL server, by right clicking in the database and selecting Task > Shrink > Files.

  

• Are you running in a virtual machine? Mother system?
• Are there other virtual machines installed in parallel?
• Is there another active database which is used on same machine?

 

Step 4: Protocol check

 

 

• Create a debug file for the slow activity, as explained in the Problem 4: Slow after program update – Step 3: Check SQL Statements in this document (Follow sequence from 1 to 5 in the procedure)
• Check duration from SQL statements inside the protocol. If slow (> 1000ms), then we have a SQL Server problem.