Last week I had the pleasure of speaking at the recent local ASUG chapter meeting at the SAP HQ offices in Newtown Square, PHL. It was a great day and I met some incredibly nice and open people who came together to partake in some awesome discussions around SAP, IoT and social media. When Derek Loranca contacted me and asked for my title I settled on the concept of “Bringing IoT back to reality”.
I’ll get to the topic of actually moving to S/4HANA later but for now I wanted to address the topic of skill set requirements after/during the move to S/4HANA as it really is one of the most common questions that comes up when I talk to customers about their S/4HANA implementation. Questions like: “Will it all be in ABAP?” “Do I need any extra skill sets?” “What infrastructure will I need outside of HANA?” “How do I approach my SAP development projects?”
Just over a month ago SAP announced the release of SAP HANA Vora, their answer to the “Big Data” versus “Enterprise Data” question. But what is it and is it really worth considering in a world full of big data game-changers like SAP HANA and Hadoop?
As a veteran of many Sybase Unwired and SAP Mobility platform implementations using Mobile Business Objects or MBOs I am frequently faced with the question of whether to use MBOs or not for new projects. While my knee jerk reaction is a resounding no, the answer is a bit more complex than that. So let’s explore it a bit more: