SAP Analytics
Thought Leadership

Bad performance can make even a well-designed EPM system unusable, and if you’ve got more aggressive expectations like those required for an xP&A solution...even suboptimal performance can be a total block to realizing your goals. Performance issues have got to be attacked quickly and decisively.

Many users feel a poorly performing system is a fatal condition and they blame the software, as if the system is working as expected when the user experience is slowed. This is not only a false belief, but it can also be a very costly one. If there’s nothing that can be done to improve an unworkable software product, then replacing it is the only option. However, poor performance is an indicator of your solution working, but it must not be tolerated. That’s right, more users adding more data to an expanding EPM or xP&A solution will eventually create poor performance. The trouble begins when you don’t know what to do about this eventuality. Don’t react rashly, instead follow the practical steps below to get a grip on the root cause of the degraded performance...in this case, for SAP BPC for NetWeaver.

If you're a support team member or power user of SAP BPC for NetWeaver, you probably know there are many standard SAP BW layer housekeeping jobs that are provided by SAP.  Most of these generate system information required for analyzing SAP BPC performance, system/error logs retention, completed job logs, etc. and are run at their default frequency. These can be scheduled in SM36, though you can't stop here. 

Keep reading to find out how to avoid poor performance by following the 6 steps below.

Description:
Critical vulnerability identified for SAP Systems based on SAP JAVA Stack.
The RECON (Remotely Exploitable Code On NetWeaver) vulnerability has a CVSS score of 10 out of 10 (the most severe)

Symptom:
LM Configuration Wizard of SAP NetWeaver AS JAVA, does not perform an authentication check which allows an attacker without prior authentication, to execute configuration tasks to perform critical actions against the SAP Java system, including the ability to create an administrative user, and therefore compromising Confidentiality, Integrity and Availability of the system.

Performance of a system is crucial to every implementation. System monitoring and administration help towards efficiently running a SAP system. Performing some proactive monitoring and configuration can help in avoiding SAP system issues. Let’s talk about a few approaches to troubleshoot performance issues while working on SAP BPC 10.0 for NetWeaver system.