SAP made a big deal of In-Memory Databases (IMDB) at SAPPHIRE NOW this year. And, it is a big deal - this technology transfers the database from disk into main memory, which frees it from time-consuming disk actions while also enabling more sophisticated database structures. The gain in performance and flexibility will transform how business data are used for all sorts of processes.
So what does this mean for customers using SAP HR (or HCM, take your pick)? Maybe you have BW, Business Objects or both. Maybe you are considering using them in the near future - how are those technologies impacted? Or perhaps you are looking at creating more event-enabled processes in SAP HR - something that IMDB is supposed to be really good at. What does IMDB mean for the current data framework in HR - infotypes and clusters?
At this time there are many more questions than answers. SAP is releasing an IMDB appliance (also called HANA - High-Performance Analytic Appliance) that will work in conjunction with the R3 system; it's a quick-fix approach designed to get customers using and familiar with the concept. But aside from that, there are not many details on what will be released and when it wil be available.
One thing is certain, in my opinion: Integration of SAP HR with IMDB will lag the rest of the modules. Three points lead me to this conclusion.
First, HR has lagged in every new technology released by SAP. When most other modules had switched to transparent tables, HR was still using PCL1 clusters for infotypes (yes, I've been around that long; and that cluster legacy still persists deep in the infotype processing). When most other modules were using ALV for operational reporting, HR still had plain text lists. When other modules had substantial BW content, HR was just getting started.
Second, the implementation of the data model for SAP HR is so entrenched in the system that transforming it to IMDB is going to be a huge effort. The current HR module is based primarily on Infotypes and Clusters. Under the hood, HR is still using all sorts of old programming methods for accessing and processing data. When was the last time you programmed a macro in TRMAC or used a straight database import to read transactional data? Those methods are still around in HR, along with function modules and classes/methods. The technical transformation is certanly feasible, but daunting.
Third, and finally, many HR departments don't think in terms of what IMDB can do for them so the business demand for IMDB development resources will be overshadowed by Logistics, MM, SD, FI and the other modules. HR business processes, and even more important, HR department philosophy, are mostly blind to what features like event-based triggers and real-time decision-making can do for them. Many HR groups are doing well to take a few, tentative steps into simple business analytics. Maybe if they push hard, in three or four years' time they would be ready to take on the benefits IMDB can provide, but by far the majority of HR departments are nowhere near ready for that.
So I believe it will be at least three years before we see meaningful, substantive and production-ready IMDB functionality for SAP HR. The IMDB appliance will make some HR functionality available prior to that, which is useful for early adopters and those who are interested in prototyping the functionality. IMDB certainly is one of the most significant changes in SAP technology; it deserves a good deal of respect and inspection because of the impact it will have on SAP and its customers. We will keep an eye on it and advise our clients to do the same.