What the Hana/SolMan community is discussing...

Has the new IT infrastructure with Intel Xeon and Linux arrived and been accepted in the SAP community?

Matthias Kneissl: Yes, Intel and Linux are no longer questioned in the SAP world! The required support usually extends through all phases, from conception to implementation and operation. It usually starts with the sizing of the architecture.

What is the significance of Hana on IBM Power?

Kneissl: Unfortunately, it is currently of little significance on the market. However, the concept offers many advantages. If the purchase price of the hardware is comparable to Intel, we are talking about a very valid alternative.

The advantages here are particularly evident for CRM and ERP in the scale-up process. A TDI can be optimized by better tailoring of the LPARs.

Does Q-Partners already have HoP projects?

Guido Hoepfner: Yes, in various phases. We have proof-of-concept projects in the lab for demo and testing purposes, but we are also in the implementation phase of initial projects. However, these are not yet live.

All users have always operated Power architectures - AIX or iSeries or AS/400 - and appreciate the flexibility and performance of the large Power machines, which can be tailored as required using LPARs. In addition, the Power architecture has always been characterized by high availability.

There are few innovative graph and neural network solutions based on Hana Predictive Analysis Library, PAL: Can the Hana platform do more than the ERP and IT scene needs?

Hoepfner: Neural networks or libraries for support vector machines are certainly interesting, but not necessarily for the classic ERP user.

This is particularly exciting if Hana is used as a platform for implementing solutions outside the ERP scene. These are likely to be primarily cloud solutions.

What can existing SAP customers expect from the new SolMan 7.2?

Kneissl: SolMan supports the customer in all disciplines of the lifecycle. The new solution documentation comes just in time for S/4.

If the customer wants to carry out the release change sensibly, he finally has a tool in which he can document his processes before the change and build a meaningful test documentation and a test plan on this.

Of course, this requires preparatory work, but this should be tackled right now with 7.2. If it is five to twelve and the release change has to be carried out, everyone is suddenly surprised at the urgency and nobody has time to document processes for S/4.

You can read a detailed interview with Matthias "SolMan" Kneissl about SAP Solution Manager 7.2 in the May 2016 issue of E-3.