Good Evening Everybody,
welcome to the Basis Technician and Basis Architect’s world in 2017.
There is so much happening in the technical SAP world, and so little time, just when we thought
things couldn’t be more turned upside because of all of the database migrations to SAP HANA, then suddenly, we’ve S/4 HANA coming on stream and the different ways to get there, greenfield, transformation and consolidation, we’ve got SAP Suite Products moving to the SAP HANA Cloud, eg IBP Integrated Business Planning the next generation of SAP APO/SCM which is a pure Software as a Service, we got BW/4HANA, more HANA migrations, more mobile integration,
SAP Mobile Platform has moved with version 6.4 to the SAP HANA Cloud and lots lots more, Tax Declaration Framework and others.
This year, I’ll be blogging a lot of the subjects which are coming across my desk, including a lot of those mentioned and more, TDI is now with us, HANA on Power with Little Endian (support from HANA 2.0 onwards) is supported.
We’ve executed so many HANA migrations (and many more to go) that these days we’re treating HANA Migrations with the same confidence as we treat Support Pack and Enhancement Pack upgrades, and we’ve got the approach as polished too.
Lots of subjects to blog and starting from today with S/4HANA, Fiori for S/4HANA and the Fiori applications for Basis Technicians.
Back in December 2013 I challenged SAP as to why they were so slow in mobile device enabling their suite of products. I think we can now say, in January 2017 that Fiori has really come of age, and finally we Basis Technicians and Architects have Fiori Applications for our field of work and interest. Don’t they look great:
How did we get there, how did we get to running a PoC of S/4HANA 1610 and Fiori for S/4HANA 1610 ?
You might remember in this blog about SAP HANA Tenant Mobility I mentioned that the Business were seeking to have a PoC S/4HANA system installed so that they could evaluate it and come to the decision as to how to make the move to S/4HANA, greenfield, transformation, or consolidation.
The Business demanded an S/4HANA PoC system. Thankfully we are running SAP HANA MultiTenancy and this mean’t we had all of the infrastructure in place, pick a SAP HANA Sandbox which has enough capacity and add another Tenant.
S/4HANA version 1610 (1610 means Year 2016 and Month10 October) requires Fiori ABAP Front End Server for S/4HANA 1610. With Fiori ABAP Front End Server 1610 there is another pre-requisite, only SAP’s Databases are supported, that’s SAPdb, Sybase and SAP HANA. Ok, this mean’t we had to create another SAP HANA MDC Tenant for the Fiori db.
All ready to go, or so we thought, We waited patiently and finally the S/4HANA 1610 installation binaries were made available by SAP. Around the same time, SAP published the Release Note for S/4HANA 1610, OSS Note 2346431
The Release Note for S/4HANA 1610, OSS Note 2346431 bought us a nice surprise, S/4HANA 1610 is only support on SAP HANA Revision 121.00 (HANA 1.0 SPS12) or higher. Our SAP HANA Sandbox which had been chosen and prepared with the new MDC Tenant DB’s was running SAP HANA 1.0 SPS10 !
So we quickly got the Sandbox SAP HANA system upgraded to SPS12. We learn’t a very important lesson during that upgrade, something which hadn’t happened in previous versions, when you Drop a HANA Tenant in SPS12, the HANA System cleans up the Tenant’s FileSystem. We Drop and Recreate Tenants to enable our HANA Port customisations as a pre-requisite for our HANA Tenant Mobility. We got over that problem, had the SPS12 running and the HANA Tenants with the correct Ports.
Then the S/4HANA 1610 and Fiori for S/4HANA 1610 installations were completed. The installations went very smoothly.
Finally we gave the systems over to the Business for them to use in the S/4HANA familiarization. In parallel, Basis, Security and Operations are all taking the opportunity to familiarize themselves with these latest versions from SAP.
Something I am very pleased with, and back to the main subject of this blog, something I have wanted from SAP for many years, access to Basis functionality from mobile devices. And finally as shown in the screenshots above, Basis now have their own suite of Fiori Applications and hopefully the more the better.
The biggest message I want to send with this blog is, we all need to be preparing for the journey to S/4HANA. S/4HANA is the next generation of the SAP ERP software, and has totally different internals than the previous R/3. I know others especially Owen Pettiford have really explained this nicely and I reiterate it here, all of us need to be pushing our companies into preparing for S/4HANA and running PoC S/4HANA systems so that together the Business, the Functional, the Basis, the Security, the Operations, the Integration, can all familiarize themselves from their perspectives with the new technology, and TOGETHER they can all decide which approach to implementing S/4HANA would be the best for their company, greenfield new installation, transformation or consolidation.
For Basis readers, I cannot recommend enough to at least have SAP HANA MultiTenancy in one of your Sandbox HANA Appliances, this way, you have the agility to install SAP Products which require SAP HANA db without having to implement a new HANA System/Appliance.
Reminder, if you want to understand in SAP HANA MultiTenancy, which SAP Components can be clubbed together on the same HANA System, then checkout the OSS Note (and especially the attached pdf) 2121768 – Considerations with SAP HANA multitenant database containers and SAP BW. The note is great and the attached pdf really explains nicely how in Scale-Out and Scale-Up how you can mix and match Tenants with different SAP Products. For example, there’s a nice explanation of running HANA MultiTenancy in a Scale-Out 5 Node HANA System with BW Scaled-Out on 4 of the Nodes and ERP having it’s own Dedicated Node for its Tenant DB in the same Scaled-Out HANA System. Therefore in that scenario, although it’s a Scale-Out HANA System, because the ERP Tenant has it’s own dedicated Node for all intents and purposes the ERP Tenant is in a Scale-Up HANA. It looks like this:
That’s all for today, there are many more blogs to come, with fascinating subjects, some of which were mentioned in the introduction.
All the best,