Tag Archives: SAP

SuccessConnect 2023 – Expectations met and exceeded

After a bit of a journey to get to SuccessConnect, I have to say my conference has been pretty great. (Couple of highlights in the pics above, seeing a cool AI use case and chatting to Amy and Aaron.)

I promised Jon Reed that I’d do a recap blog post on how what I’d seen about SuccessConnect that matched with, underwhelmed or exceeded my expectation – as I’d laid out in my prior post. So here goes!

AI… was there any mention of AI, OMG, you couldn’t stop hearing about it. The keynote was AI, every sessions had a reference to AI, current or future plans, it was everywhere except the Tuesday night party. Meg Bear did make a good point – expecting to not hear about AI at a tech conference would be more remarkable.

However, I did see a demo of using generative AI to put together a performance goal that really did wow me. (first photo in this post) A simple use case, but it took my prompt for a goal of “create an SAP BTP SuccessFactors extension application” and turned it into a SMART goal, added a bunch of very relevant steps, and SAP will be happy, even suggested I add it to the SAP Store. All with a set of reasonable date and details for each step. I was impressed, there are very few people I know who could have come up with a better representation of that idea as a performance goal.

My only worry, now, is that creating goals is going to be far to easy and fun for my team if they were to use this (we use SAP SuccessFactors internally at Discovery) and I’m going to end up reviewing a stupid number of goals, but at least they would all be SMART ones! But to that point, my next thoughts were around how is this going to be paid for, because it can’t be “free”! Generative AI costs money to run. This took a little more digging into, but I was happy to find an answer that made sense to me.

SAP, after realising that building their own LLM tooling was silly and that others do it better, have chosen not to only go with the one LLM/AI/ML platform but instead are using multiple. The SAP-wide chat agent “Joule” being powered by IBM Watson, the goal setting piece that wow’d me being powered by Microsoft. In the end the customer shouldn’t really care which underlying engine does the processing, as long as it doesn’t leak personal or company data (and I’m pretty sure that SAP are making sure that doesn’t happen.) But on the other-hand, customers shouldn’t have to purchase subscriptions for each piece of AI logic they use. And this, is what I’m told will happen – a single SAP-wide subscription to AI services that can be used on perhaps a pay-as-you-use basis – that bit apparently not 100% sorted yet – but the single subscription model sounds great.

I had some great conversations with a few people about the potential for vendor lock-in coming from AI – or at the very least the need to provide much more historic data in any system migration to “train” your AIs on your company’s data (with the associated up tick in migration costs meaning that there will need to be some really compelling reasons to migrate.)

This will be more relevant for some areas than others. Whilst Holger assured me that technically import/export of trained models will be possible, I’m not seeing that will happen. No vendor is going to let you bring your AI training with you when you leave the platform, you’re going to have to re-train, and that is going to mean migrating LOTS of data. There may be scope for data load that isn’t “in-system” just for training of AIs – think this is a new problem that hasn’t happened yet, but there may some benefits for first movers in this space – let’s see what happens.

Opportunity Marketplace – Yeah, was mentioned quite a lot, references to is from pretty much all tracks apart from payroll. I should have made that one a drinking game. But customer stories on how it had benefited them, I didn’t hear too many of. The one customer I was hoping to hear from had pulled back from implementing due to desire to reset all the Talent Intelligence Hub links and skills and competency model in their organisation. So I’m still looking for those stories that can help me justify the implementation to a new customer. I still think it’s a great tool and I like it, but just because I like it doesn’t mean it solves a problem for a customer well enough that they will buy it. I think the problem here might be with so much new cool stuff happening in Talent Intelligence Hub, customers are struggling to figure out how to get their houses in order to benefit. They all know they will benefit, but deciding on which skills your organisation uses, that’s not as easy a task as you might think it could be!

Recruitment – well I can tell you they heard LOUD and clear the feedback about removing the drag and drop in the new recruiter experience. The new experience is here and aligns with Horizon theming in rest of platform. Some cool use cases for AI in allowing detection of skills in candidate CVs and allowing comparison of candidates by skills alignment with role. Think we will be entering into the new war of AIs – with AIs generating candidate CVs to make them as attractive as possible to the AI that are pulling the details out of them. This is going to be a space to watch.

Learning – No surprises here, the new experience looks great, lots of discussion about how this will work with new skills and competencies. I think biggest thing to come here (apart from the new experience) is the offline mobile experience for Android. That will make a difference for many, especially the “deskless” workers.

Talent Intelligence Hub – again, nothing unexpected. Great news is that it seems the SAP teams responsible for the product are as genuinely excited about handling the difference between employment level info and person level info – looks like we are aligned on this one. Now just looking to see how to ensure it happens. i hope we see some significant customer adoption of this solution as pretty much ever new non-payroll enhancement to the suite appears to be based off it.

Concurrent Employment/Temporary Assignments/Higher Duties – Okay, it wasn’t as hidden as I thought it might be, but it certainly didn’t get the exposure it deserves. Great thing is I met with Farah Gonzalez who is the VP, Global Product Management for Public Sector. Kicking myself for not having taken a photo of the two of us, but here’s her LI profile shot – given the effort gone to here, seems a shame not to share!

Anyway, I have found someone to share all my hopes, dreams, expectations and disappointments for this area of the product and we’re setting up a meeting to discuss, I’m very much looking forward to that (once I get over the jetlag and backlog of customer stuff from being at #SuccessConnect.) I still think these solution are very relevant for organisations that aren’t public sector and very much play into the #FutureOfWork type discussions. But making connections with people like Farah is exactly why going to SuccessConnect in person is so valuable for me (and my customers!)

Payroll – Well, this is interesting. Next Gen Payroll has a new name – SAP SuccessFactors Payroll and will be in early adopter (as in productive usage!) for some customers implementing in UK this year for hopefully go lives next year. US version to follow, with Germany, Canada and Australia, to follow some undetermined time later. Likely target market for near future will be smaller organisation with payrolls of less than 1000 emps, so not really your legacy SAP payroll or ECP customers yet. Hoping that means my company might be a possibility when Australian push happens, we have both S/4HANA (public cloud) and SAPSF… ( hint, hint any SAP people reading this!) A LOT of discussion around customers needing more certainty on timelines and SAP not being able to give this, which I found a little frustrating (not that SAP couldn’t communicate a timeline, but that we spent so long discussing it. but it is worthwhile that SAP knows how frustrating that is. So I guess I can handle a little frustration for the global good.)

APIs/Third Party Cookies deprecation handling/Audit logging – really enjoyed a couple of sessions around the more “techy” areas of SAP SuccessFactors. There is probably enough there that I could fill an entire post by itself – so I probably will. But highlights/call outs:

  • The poor guy running the main tech roadmap session hadn’t been pre-briefed on who I was (evil grin) and probably let me ask too many questions,
  • Had multiple customers come up to me afterwards and thank me for asking those same questions!
  • Very surprised that SAP didn’t use the conference as an opportunity to pre-brief customers on upcoming URL changes to ALL SAPSF instances and IAS/IPS instances.
  • We’re moving away from OData! seems that SAP isn’t pushing CAP into it’s own products, because SAPSF going to move to a REST based API and away from OData. The things I heard about streaming/websocket APIs are apparently not going to happen (boooooo), But good news is that new framework for API development should be MUCH simpler for SAP to implement internally, so getting an external API to new functionality, should be much faster and simpler. Think there will be a lot to play out in this space.
  • Finally Audit and access reporting functionality coming back. Audit logging will be using the SAP BTP Audit logging functionality – thus ensuring compliance with all those tricksy global compliance legislations. Access log reports will also be available shortly (if not this coming release – I honestly can’t remember, but will be checking release notes and the slide decks when I get them.

Overall

Thanks to the amazing Liliana Zolt who helped make the whole experience so smooth over the three days of the conference, huge appreciation. Was wonderful to catch up with the undeniable brains-trust of the SAP SuccessFactors consulting world, all the interactions with everyone were fantastic and the people we spoke to on the SAP side were all amazing and so willing to make the time to chat to us. Was amazing to be there. Really looking forward to next year in Lisbon (now just to figure out how to convince the company to pay for an even longer flight!)

  • *Updated to note SAP SuccessFactors Payroll expected to be live for some limited initial customers *next* year, not this year, just implementation this year! Still very exciting though!

SuccessConnect 2023 – expectations

Okay, just arrived at SuccessConnect, bumped into Eric, AJ and Aaron so far and met Nagesh.

Before the real thrust of SuccessConnect starts and I get the real info some thoughts about what we will see this week.

My Predictions

AI. Yes there will be AI mentioned, I think I will need a new t-shirt with

But I think I’ll have to work on getting it a bit more snappy.

Yes we will have more AI, some of it will even be provided to customers without additional charge, but for most use cases, especially generative AI there will be a charge. Will be interesting to see how Joule fits into the SAP SuccessFactors landscape.

There will be one or two new use cases for AI that I hadn’t thought of which will make me smile, but in general, I doubt I’m going to see these as “game changing” in the near future.

Opportunity Marketplace, there will be more discussion and hopefully some updates from customers that have been playing with the tool. I’m hoping to hear some numbers about ROI that

Recruitment finally the refresh we’ve been waiting for, but not without it’s challenges, why on earth did we loose the drag and drop. We’ll see a bit about this.

Learning – looking forwards to demos of new learning experience and understanding if and how there will be opportunities to extend it.

Talent Intelligence Hub – the bit I am looking forward to understanding more about, how can we best integrate all the components of the suite to provide a go to solution. I’m really excited about bringing in of licences and education into this model and away from custom MDFs, but see this also as a big challenge for many organisations, especially for those that are using concurrent employment.

Concurrent Employment/Higher Duties/Temporary assignments – we _should_ hear more about this, but honestly doubt we will. It addresses a real need in the market, but seems not so many people seeing this.

Okay, that’s all for now, will update afterwards with what I got right and wrong.

What is “table stakes” for API functionality?

What is “table stakes” for product development these days? Do you believe that we should be following an “API first” development strategy?

I recently (well it was a year or so ago) came across some cool SAP SuccessFactors functionality which allows for a person to be put temporarily into another position, returning to their substantive position after a fixed period. Many of you will know this as “Higher Duties” or “Temporary Assignment” functionality. The problem I found (more recently) was that whilst most of the information about the temporary assignment was available via API, one key piece of information (very important information), the end date of the assignment, was NOT available via the standard SAP SuccessFactors OData API. ☹

Surprisingly, and luckily, the information is available via the old SFAPI (a SOAP based API, and we all know how much developers love SOAP!) So I can work around this for the moment.

This said, to my thoughts, new(ish) functionality, like HD/TA for SAP SuccessFactors should always allow for the data that can be seen in the frontend application to be available via the OData API. That should be “table stakes”. A modern HRIS must be supported by a secure, open, documented and complete API. I often ask potential customers during sales presentations, to compare SAP SuccessFactors with the other products they are considering to Google “name of HRIS solution” + “API” and see what is returned, whether they need to sign in to see it, are there supporting document, examples, etc. SAP SuccessFactors pretty much always wins this game (mainly because Microsoft and Google don’t have competing products in the space, because they use SAP SuccessFactors.)

SAP has come a long way in making its products somewhat developer friendly, so it really irks me when I’m told “We do not have this on our roadmap at this point in time, please raise an influence request”. So I did – https://influence.sap.com/sap/ino/#/idea/308298

If you’re an SAP customer and you manage to read this far into this post, please do me a solid and log in to vote for my influence request! Thank you! Whilst you’re there, have a look around there are loads of requests that would make so much sense to implement, vote for them too.

Customer voice is so important – and this “influence.sap.com” space is one area where we as customers actually get a little bit of a say!

The end of an era

Screen shot from very last SAP SF IAS IPS open office hour

It was with a fair bit of sadness that this week I was part of the end of something that I think was a bit special.

The SAP SuccessFactors IAS/IPS open office hour has been running for what I think was 2 years now, and for many of those Thursday evenings (it ran at 6:30pm to 7:30pm my local time) I would join, sometimes with a beer or wine in hand and would sit, listen and contribute.

I think Richard Feynman the American Nobel Laureate and Physic Professor once said :

“If you want to master something, teach it. The more you teach, the better you learn.”

Richard P. Feynman

Well, I think that’s what happened to me! By spending so much time in this call, trying to help other people figure out how to solve their IAS and IPS issues, I’ve learnt so much! I’m waiting for an IAS/IPS certification to come out and nice easy one to pass!

During this journey, I’ve developed some great relationships with SAP teams in this space. I’ve presented at SAP TechEd on the topic, had multiple influence requests turned into reality and been involved in beta testing new functionality. And more importantly, made some good friends.

There is still so much more to learn, but this opportunity to gather weekly to help out other SAP customers that were stuck in a tight spot is now over. It probably had run its time and it was time to focus the support efforts elsewhere, but whilst it was there I really did enjoy it.

Thank you to all those who helped make it happen!

Grounded in Reality and Pragmatism.

That’s not a title to any piece about AI or ML that I’ve heard for quite some time, especially not something out of any HXM vendor’s keynote!

If you haven’t already – please listen (watch too if you like) to this really short – less than one minute, clip of Meg Bear talking about Artificial Intelligent and Machine Learning as part of the executive open Q&A at the last SuccessConnect conference (2021).

sourced from twitter: https://twitter.com/megbear/status/1467231582184296449

I’ve included the transcript (as I could make out) below:

“So what we know deeply, is that machine learning and AI are great tools but they are not sufficient conditions for the overall experience that we are trying to drive. It needs to be bringing that technology in concert with people, in concert with who I am and what I want to add to it. To create something that is truly powerful.

And, so, while we are absolutely putting machine learning and artificial intelligence inside our data model. We’re talking about it in a much broader way. Because we know that just saying that you have machine learning is not sufficient. It needs to be about what is the outcome for me as an individual and what is the outcome for the business, and it needs to be grounded in deep reality and pragmatism.”

Meg Bear – SuccessConnect Executive Keynote 2021

Okay firstly, hats off to Meg! When she gets going on a topic that she’s enthused about, there isn’t anyone that’s going to stop her. I think if you listen carefully you can hear some of the the rest of the the team giggling slightly in awe of Meg doing her thing. It was a completely passionate geek-out that was by far the highlight of the whole conference for me. Mainly because I couldn’t agree harder and would have had trouble articulating it more eloquently, especially if I were on a live Q&A in front of thousands of people. Thanks Meg for following up on my request to get that video. (I’ll not include the link to the original request because Amy Wilson might not ever speak to me again if I reposted that particular screen grab!) (oh to be able to retrospectively edit the photos in livestream tweeting)

The current state of ML in people management is pretty basic and some of the uses that have been attempted are pretty bad. For an interesting take on what not to use ML for – check out Thomas Otter’s piece on flight risk indicators. Just looking at what SAP have managed to deliver in this space recently and we haven’t got much more exciting than the Amazon “other shoppers who purchased a course in first aid also purchased a course in CPR”. It’s not inspiring (which is probably why some organisations try to do things like flight risk.

So, Meg turning the conversation around from a technology bang-whizz smoke and mirrors magic show to instead focus on the objective that we are trying to achieve of great employee experience is very important. We need to realise that there is very much a “human” in HXM and attempts to remove it will fail.

I watched a demo, in the same conference (eek), of a chat bot that had been put in place to help gather more details about how people were coping during lockdown due to COVID 19. What was very interesting to me (other than I manage to stop myself from screaming at the screen) was that there were quite a range of opinions in the session I was in about whether this was good or bad. Let’s just say I was in the “You have got to be f’ing kidding me” side of the opinion poll, whilst others were more on the “That’s a cool way to get feedback” side. The reason I think this is terrible is because if your outreach to people who are suffering because of isolation is to throw a bot at them then you’ve completely missed the H bit of HXM. And that bit is important to me (and Josh Greenbaum it seems.)

And so, why is Meg’s focus on HXM and not technology so important? Because if you give techies technology -> they will build with it, and scarily enough, they will also believe what they are doing is good. I know, I’ve fallen into this hole so many times that I have a ladder purpose built for climbing out of tech for tech’s sake holes (it’s called a phone call to my good friend who has no issues in telling me I’m an idiot and to stop being stupid.)

So, I look forward to what comes next. I would really like to be able to make ML models that could help recognise things like which managers are helping their teams perform better so we can all learn what human interaction driving better experience. I want ML to send me alerts when thresholds of leave liability are likely to be exceeded so that I can send dashboard to managers who can then use their on-the-ground relationships with their staff to check those numbers and have person-to-person conversations with them. But I want all of it in a supporting, not supplanting role. Tech to help people interact with people, not replace that interaction.

We are getting (slowly, oh so slowly) to a state where we have platforms that can build these types of experience enhancing solutions. But as Meg says only when “grounded in deep reality and pragmatism”.

Okay – that’s enough SAP SuccessFactors love for one evening.

SuccessFactors team, remember all these nice things I said when I start complaining (again) about the Reimagined Home Page Migration! 😉

What would you like in analytics?

Quick one today. Whilst I’m getting over (actually I’m not) my disappointment that Analytics Cards (Stories in People Analytics widgets) are very unlikely to be available as part of the 1H2022 release, and therefore dashboard tiles will not be part of the new SAP SuccessFactors homepage when it is forcibly pushed to all customers next year, I thought I’d write quickly about a different take.

Recently, I asked a senior non-HR exec what they wanted from their HR analytics dashboards. Any guess what they wanted?

“Don’t show me any dashboards. “

Senior Exec.

They didn’t want to be required to look at a dashboard. This is an extension of the themes I expounded on in my last post. This person wasn’t going to ever action anything based on glancing at a dashboard – mainly because they didn’t have the time to look at a dashboard. What they wanted instead was a prompt to investigate.

You might be devious and say – but I could just build a dashboard that only showed prompts where there was a need to investigate. But what this manager wanted, was external prompts. I.e. an email or a notification that then linked to dashboards and analytics pieces.

Good thing is that this 2H2021 release just enabled the possibility to deep-link to a given SiPA story. What we need now is some way to actually ping links to relevant analytical stories when they are needed.

This would be a super simple thing to do for some situations. Bets on SAP SuccessFactors tooling being introduced in next few years that allows for the configuration of ML based triggers that can then be linked to custom designed dashboards.

Then I can throw a link to custom dashboard at my exec when they have a huge spike in leave liability and people not taking leave. Then they only look at the dashboard when there is a need for them to take action.

So if I wrote an SAP BTP extension that enabled you to email links to specific dashboards to your managers based on certain thresholds being met (or not), would that help you get over not having dashboard tiles on the home page?

SuccessConnect 2019

Just some very brief highlights and musings from the lounge in LAX whilst I wait for my flight home to Melbourne.

This was the eXperience SuccessConnect, there were X’s everywhere! The amount of airtime that Qualtrics and experience management got may well have equalled the amount of time that the SuccessFactors product was discussed.

My SuccessConnect really kicked off with  the Monday partner briefing and meeting up with Sylvie Otten and introduced to Micheal Grimm from Ingentis. Was good to start off the event with a good moan about the state of CF vs Neo when it came to SuccessFactors extensions. Sorry Sylvie – I earned my namesake.

At least she was smiling in the photo!

 

Next up was the partner briefing – after having made the mistake of sitting near the front last year at it being the most boring multiple hours of the conference, I sat at the back so I could sneak out rather than pass out with boredom.

I was wrong.

David Ludlow completely creamed it with his update on roadmap and recent changes. That was probably the best 20mins of the entire conference. Wish I had sat nearer the front! Although have discovered that taking photos of slides in SAP’s newly preferred dark theme really doesn’t come out well, the black comes out browny grey – doesn’t look so cool… 🙁 But I got the slide deck – gold!

There were many cool things in there, but the new UI being proposed for the user landing page was probably the most exciting bit – which is why David didn’t say much about it, but left that for Amy the next day at the keynote.

Lots of debate about this new conversational AI based UI. With the biggest one being, there better still be menus and some way i can add a link to view my payslips, and apply for leave  with one click without having to type in “view my payslip”.

We’ll see how it develops as looks like planned delivery 2020 – but I’ll bet on it not being GA before next SuccessConnect. Perhaps beta with a couple of customers… lets see next year.

After David’s excellent presentation I got to catch up with the team of analysts and media folk who’d had a briefing that day. Josh Greenbaum was holding court and had some interesting comments around SAP’s strategy with payroll, but the wine and food was excellent and I left with some of the folks there to go to the exhibition show floor and do what I was supposed to be at the conference for (not chin wagging with analysts!)

I was here at SuccessConnect to sell a SAP CP extension for SuccessFactors that me and my team have built – it provides EHS functionality embedded into SuccessFactors. It’s pretty cool! But I would say that!

 

I have discovered that I sell much better with a glass of wine in my hand…

After that it was to Jewel nightclub to the Kronos and Rizing party (not sure I really should have continued drinking, next day was hard work!) But did get to meet up with Sherryanne Meyer which was nice.

 

The next day was lots of water and the keynote.

Image

Have to say, I love the moments that matter idea. as in consider where you are putting your effort in making certain processes work better. It’s probably much more important that the initial day one experience for an employee is better than the process they have to use to apply for leave. They might apply for leave hundreds of times, but they only have one day one and it will be a much bigger impact. Think about the return to work process for return from parental leave, make that a great experience don’t worry so much about timesheet entry….

However I heard the term FAR too over used during the conference and used outside of the context i just described.

And then the keynote just went to “eXperience”. It was wow, everything was about HXM or Human eXperience Management, not Human Capital Management. Look, I dislike the HCM idea of treating employees as “Capital”, that’s not what we try to do, but still there is a whole bunch more the the successful running of employees in a business than just looking after their experience!

I observed cynically to someone (the night club from night before possibly didn’t help my mood) that it seemed  that the SuccessFactors exec team had all been given bigger KPIs to sell Qualtrics than they had to sell SuccessFactors.

 

After the keynote were lots of general sessions including loads of roadmap sessions! The conference team really listened to the customer desire for roadmap sessions and most were repeated at least one. Even better the sessions were short on presentation and long on questions. This is why people come to conferences rather than reading the slides at home (and without having to fly stupid distances around the world). So SUPER KUDOS to the SuccessFactors team, your roadmap sessions were AWESOME! I had lots of fun in one run by Mark McCawley who I meet for the first time and leaked some news that I’m hoping we can reveal soon that will make many customers very happy!

Saw mention that instance sync tool will allow copy back of employee data from prod to non-prod systems (without full system refresh) allowing for trouble shooting of issues in test environments – this is awesome and will be a huge benefit for customers. When you look at the list price that Accenture were/are charging for a SAP CP tool that does similar thing, you can see how customers were really wanting this functionality!

Talking of the SAP App Store and SAP CP extensions, they were highly visible this year on the show floor and customers were clearly interested!

Final keynote was more eXperience Qualtrics puff along with 3 partner add on solutions, and a strange plug for SAP.io which I’m pretty sure the audience didn’t care about. Much disappointment that non of the partners on the stage with SuccessFactors add ons were using SAP Cloud Platform – a real lost opportunity to showcase the power and benefit of having extensions that look like they are just additional modules of SuccessFactors, a functionality that SuccessFactors has that is unique – I’m afraid integration to ServiceNow isn’t really that unique…

Last day and the team:

went to the golf driving range, where I discovered I’m not terrible at this golf lark, but not good at it either. Was fun!

Anyway – flight about to be called.

Was great to be at SuccessConnect, think it would be good for the SuccessFactors exec team to perhaps take a moment to listen to the SAP Mentor feedback – perhaps we can arrange something for next year?

On ABAP in the Cloud

ABAP in the cloud

Michael Koch kicked it all off with a tweet,

to which of course I had to reply:

then I was prodded:

and prodded:

and then James beat me to the blog:

and if you haven’t read James’ post, please do, it is excellent.

So whilst I’m waiting to hear how much it’s going to cost me to fix my car of which the engine has decided to stop working whilst on the way to work today, I thought that rather than drinking a bottle of Pinot Gris and attempting to forget about the shitty waste of a day I’ve had, I’d do something useful, productive (this post), and drink beetroot, apple, ginger and celery juice instead.

So here are thoughts upon which I will rant.

  • ABAP is a proprietary language which make its code costly to support.
  • Building for cloud is far more than just supporting cloud systems.
  • If you love ABAP to the exclusion of everything else that’s your bed, you lay in it. I like beetroot juice, I am so going to have pink pee later.
  • Java is the boring enterprise language of choice.
  • A PaaS really should be language agnostic, if not it’s a pretty crappy PaaS.
  • Why on earth have we ended up here? Who is paying for this?
  • Evolve or die.

These are all going to get intermixed in this rant, but I will still try to address them one by one.

Firstly, on the joys of ABAPers. I have discussed and even written about this, and it may just be the particular markets where I play, but it’s damn hard to find a good and excited ABAPer. People don’t learn the language unless they want to work on SAP products. Imagine how quickly that strips out the fun people. But where people have got good ABAP skills, they tend to have far more than that, also great business process understanding (Robbo has recently written about this https://blogs.sap.com/2017/10/02/abap-in-sap-cloud-platform-why/ ) Have a read, especially if you fall into the ABAP diehards camp, it will make you feel much happier than this blog post will.

But because the good ABAP folk have such great depth of business process understanding, they command a reasonable rate – and why not having a BA and a coder in one is a bit of a win is it not? So they are expensive. One hopes because they deliver better, but I find this is not true. They just cost more. But you have to have them to support the huge monolith that is your SAP ERP system. So embedded in companies around the world are these folk who can code ABAP, understand their systems and are if not well paid, expensive to have hanging around.

And you won’t find someone off the street who has just learnt ABAP who is useful, because the skill in ABAP isn’t in the language, it’s in understanding the existing library of  standard code and frameworks that you can use to get things done.

FFS the language still doesn’t have the concept of a Boolean!

The requirement for ABAP support is one of the reasons that SAP costs a decent amount to run. In the future as we move to S/4HANA public cloud (and we will, slowly but inevitably) cost saving will be essential. ABAP costs, so get rid of it in the equation. Out-source your custom development, even better, purchase it as SaaS from someone else, are you a custom software development house? No – they why do you try to build your own software? Concentrate on dishwasher powder, chocolate bars, beer or whatever it is you have as your core.

If we start building cloud extensions in ABAP we are locking down the list of people who could support them. This will cost us extra. Having worked with SaaS for the last few years, I can clearly state, cost of delivery is far more important now than it ever was on-prem. The expectations of customers are different. They will not pay the same amount to build an extension as they paid for the SaaS solution it enhances. ABAP ain’t cheap, and neither are ABAPers.

I don’t think ABAP and it’s whole lifecycle management is really well designed to build cloud apps. James mentioned some great points in his blog around dependency management, and how ABAP doesn’t support non-linear and project based development (hopefully ABAPGit will help here, the official voice of support from SAP is very encouraging.) But having spent the last 5 years build cloud apps that integrate to SAP systems, I have been so impressed by the huge amount of standard tooling and functionality that is available for projects outside of SAP. Like have you used Maven? It’s fricking awesome! To consider even thinking about managing the huge number of libraries that I use in most of my builds to do without this tooling would be unthinkable. Since James was probably more detailed and eloquent on this point I will stop there. But really, even if SAP support ABAPGit there is a hell of a long way to go to even think of being put into an imaginary cloud development language magic quadrant chart, let alone featuring anywhere but bottom left.

#ABAPisntDead. No of course it isn’t, there will be legacy on prem apps that will run and people will make businesses out of it, like those Rimini Street folk. But if you can’t see anything out there other than ABAP, my goodness you are short sighted. Any good programmer out there should be able to code in js (server side or browser), and should have a grasp of at least 2 other languages. If you can only deal with one, you’re not a programmer, you’re a liability for the people you work with. Having multiple skills is important, and it’s also important to know when to use them. Enlighten yourselves people, there is a whole world full of cool shite out there, go and have a look. If my post infuriates you because you believe that ABAP is the best thing ever, awesome, both for you and for me, because you have passion, go and use it, and me because it means I actually got some people who don’t agree with me to read this.

Java is boring, and safe, and commodity. And that is exactly what businesses love. You want something that is reliable, has been proven, does the job. Moreover, you want bucket loads of libraries that other people have built and tested that can do the things you want to do. Whilst I built an implementation of TFA that was compatible with Google’s TFA Authenticator app in ABAP, it was a pain in the arse, and hasn’t been updated since I wrote it and then worried about releasing it as open source because you weren’t allowed to do that with ABAP. There’s a standard lib for Java. Standard boring languages are the bedrock of good enterprise builds. I do like to play with server side js, (aka Node) but i’m still a sucker for strongly typed languages.

But if you don’t like Java, then awesome, choose something else. Indeed it should not matter what you choose, because any PaaS you build on should be language agnostic when it comes to providing services to you to consume. If you’re not consuming any services from your PaaS then you missed the memo about cloud development, please go back to your application server. A PaaS offers micro-services that should be able to be consumed by any application running on that platform. This inherently makes those services consumable in a fashion that is hard to use for ABAP and pretty standard for every other language. I’m sure that SAP could wrap their services into a consumable layer that would be easier to use in the Cloud based ABAP. But this then means we start losing one of the best bits of the PaaS, that it shouldn’t favour any runtime. We’ll see how this story plays out…

Which kinda segues into my next worry/rant/observation. How did we get here that a language that really isn’t suited to cloud extension ends up as an officially supported run time in SAP’s CF PaaS? This goes back to my original tweet.

I believe that it is clearly SAP’s strategy to move to the largest part of their revenue coming from public cloud based SaaS solutions (including ERP). Btw, I think this is a sound strategic vision, because if they don’t pivot to get there, someone else will take that space. The on-prem model will not make as much money in the future, todays small companies are tomorrows giants, and with SaaS solutions they don’t need to migrate/upscale, they will keep the solution they buy today. SAP needs to be in that space, and they need credibility that comes from large customers being there too.

To this end I envisage SAP have been discussing moving some very influential customers to the public cloud. Those customer, I would guess, have responded that they don’t want to loose their current people or custom build investments.

The obvious solution from SAP is to put together an ABAP cloud runtime. I cannot be cheap to do this though. The effort to make ABAP into a secure and lightweight containerizable solution will not be something that a team will do in a week or two. There must be some sound and solid business reasons to do this. For all the reasons I have previously mentioned I believe that if companies want to extend SAP SaaS solutions, they should think about using other languages, not ABAP. But I fear this is not about making a better solution, it is about making a marketable one. If customers believe that they can extend the value of their existing investments and also benefit from moving to SaaS based solution, that is a great sales pitch. It’s having your cake and eating it.

This vision (even if it doesn’t work out to be the reality) of a simple gateway to moving to SaaS ERP is what I believe we are now being sold. This isn’t a story for developers, this is a story for the high level execs that sign the S/4HANA subscriptions.

I hope that a cloud based ABAP will be the gateway that enables some organisations to get off the on-premise mode and head to the cloud. What I fully expect is that once they are there, they will realise that there are better and more supportable ways to extend. That would be great. In the meantime I fear that we start bringing non-cloudy ways of working into the cloud landscape, this will likely cause failed/cost overrun projects. We run the risk of preferring Cloud ABAP as a way to interact with S/4HANA cloud, that would be disastrous.

It has been suggested that Cloud ABAP will potentially be the solution that encourages adoption of the SAP Cloud Platform. I just hope it isn’t the solution that kills it. I would much rather the money being spent of putting ABAP into the cloud is used to handle some of the other issues I see with SAP CP, but clearly there is a view that it will be a return on investment.

Then again, if you’re not trying new stuff and making mistakes, you’re not learning. If you’re not learning, you’re falling behind. So here’s to making mistakes and learning! To steal the excellent closing lines from James’ post:

So buckle up because there’s no turning back at this point. It’s either evolve or die.

I look forward to a lively debate on this topic.

(James Wood – https://blogs.sap.com/2017/10/04/abap-in-the-cloud-is-this-a-good-thing/)

James, I couldn’t say it better mate. Although I would refer to the platform as SAP CP 😉

I think SAP Cloud Platform is and will be a key part of the story of SAP’s  and customers’ evolution to the cloud. If it takes putting an “runs ABAP” badge on it, to get people to see how useful it is, I’ll deal with it. But for sure, it would not be my recommendation to any organisation that it would be best practice. I’ll keep an open mind, perhaps it will be one day, if so I’ll adapt and evolve – because that’s what you should do.

As always, my own thoughts, not my company’s,  please feel free to jump onto SCN and reply to James’ post. I’ll probably read those comments as well as whatever gets posted on twitter.

 

#SConnect15 – SuccessConnect 2015 Sydney Day 1

I think perhaps my photo taken on the way to the airport this morning sums up today pretty well.

An empty road with a whole bunch of speed bumps. I’m afraid that’s what today felt like. It’s kinda weird starting off a conference without hearing the keynote to set the tone. Even with SAP conferences like TechEd we have “pre-conference” days – thanks ASUG! But today was part of the conference, and it didn’t really feel like it.

An example of the bumpy road was having a session today on the new support model for SuccessFactors, but without mentioning the SFXpert program. It was kinda weird – but apparently Mike Ettling will talk about that in the keynote tomorrow, it’s a little confusing.

Moreover, there weren’t an awful lot of people here. Which in someways is pretty good, it means that we’re able to have comfortable conversations, no running around with microphones to ask questions. But it certainly seems that running a SuccessConnect in Singapore may have reduced the number of Sydney attendees. I’m not sure, perhaps tomorrow will bring more people? It was a big ask to get people to come for a whole day for 3 sessions.

But it was a glorious evening in Sydney:

 

and we’re keeping on going with the saving of Elephants and Rhinos with the corporate social responsibility thing

Would love to know where we’re at with that total – hopefully we’ve got above a few thousand dollars by now.

So a few bumps, a fairly empty road, but the way ahead looks clear, and the weather is glorious. I look forward to tomorrow. I just hope that the panel session with David Ludlow goes well. 🙂

we shall see.

 

Further update on SAP Gateway CSRF token farce

So an update on recent rant about CSRF protection that isn’t needed on SAP Gateway.

The folks in the very attentive HCI team have just added functionality into their solution, so if you configure an OData call to an onPrem system via SAP HANA Cloud Connector, it will automatically do the GET with a fetch for the CSRF token for you whenever you configure a data update operation.

That’s kinda cool, but all it does is sweep the offending rubbish under the rug.

https://www.flickr.com/photos/bruce_krasting/7695348682 - Sweep under the rug, credit Bruce Krasting

https://www.flickr.com/photos/bruce_krasting/7695348682 – Sweep under the rug, credit Bruce Krasting

So now we have logic built into an integration platform that is needlessly slowing our integration flow because of a superfluous system requirement. An extra round trip for no reason.

In this case it is truly superfluous, because the original PUT that I was using had the user credentials as part of the header. That alone should make the CSRF token not required.

What this does show, is how SAP Cloud solutions like SAP HCI are able to update and fix stuff far faster than their onPrem partners. Even if it is a work-around to a problem that shouldn’t exist.