on 12-26-2015 9:53 AM
Chaps,
4 quick questions :-
(1) Can we run S/4 HANA on AWS Cloud Solution(Private) ? Is this an option or is SAP HEC the only cloud platform allowed (We have a mandate to go for SAP ERP on Cloud)
(2) If we can indeed run the Full ERP S/4HANA on AWS Cloud, will I still need to use S/4 HANA Cloud Extensions for development/customization activities ?
(3) I understand that some functions within S/4 HANA are now simplified and has dedicated FIORI Apps for it. I`m confused as to how would the end-user navigate within FIORI Apps (for simplified functions) and traditional ECC T-Codes on SAP GUI (for non-simplified functions). Does it mean for example, when a business user is completing a Procure-To-Pay cycle, he/she will have to toggle within FIORI Apps and traditional SAP GUI T-Codes?
(4) Can you explain/warn me of the disadvantages/cons with the option to go for S/4 HANA on AWS instead of S/4 HANA on SAP HEC ?[Note: AWS is much cheaper option that SAP HEC}
Would appreciate if you could share your insights and thoughts, as these are some the very critical factors we`re considering in our next ERP Purchase.
Thanking in advance mates !
Cheers,
John Mcluskey
Hello John,
Good questions, below is my take on these questions:-
(1) Can we run S/4 HANA on AWS Cloud Solution(Private) ? Is this an option or is SAP HEC the only cloud platform allowed (We have a mandate to go for SAP ERP on Cloud)
Yes, you can go for AWS. Even now you can have 30 days trial of S/4 HANA on AWS
You can check it here-
SAP S/4HANA Trial Landing Page
Also check this blog ( especially the last part on options for S/4 Cloud)
(2) If we can indeed run the Full ERP S/4HANA on AWS Cloud, will I still need to use S/4 HANA Cloud Extensions for development/customization activities ?
Not sure what you mean here.
(3) I understand that some functions within S/4 HANA are now simplified and has dedicated FIORI Apps for it. I`m confused as to how would the end-user navigate within FIORI Apps (for simplified functions) and traditional ECC T-Codes on SAP GUI (for non-simplified functions). Does it mean for example, when a business user is completing a Procure-To-Pay cycle, he/she will have to toggle within FIORI Apps and traditional SAP GUI T-Codes?
SAP's approach to Fiori has been to new and Renew, i.e. create new Fiori apps which were not present before, e.g. View Checkbook Fiori App and to Renew i.e. create a Fiori version for the existing transactional apps.
Having said that, you will get most ( not all) Transaction being still there for which Fiori apps are created.
So if a user is comfortable with GUI screen he can pretty much do everything there.
(4) Can you explain/warn me of the disadvantages/cons with the option to go for S/4 HANA on AWS instead of S/4 HANA on SAP HEC ?[Note: AWS is much cheaper option that SAP HEC}
Detailed topic and depends a lot on your requirement and scenarios.
Hope this helps,
Regards
Rishab
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Rishab, thank you for sharing your insights. Let me try to detail my question.
(2) Assume we`re already running S/4 HANA on AWS cloud. Would the manner in which I would perform customisations, modifications, extensions remain similar to doing it On-Premise ? or would it be any different ?
(3) So is the answer yes, as in business users would have to toggle between FIORI Apps and traditional SAP T-Codes to get a complete cycle of Procure-to-Pay or Plan-to-Product business transaction complete ?
(4) Assuming it`s a fresh green field implementation, my question is trying to gauge the advantages of HEC over AWS specifically to S/4 HANA ERP Implementation
Appreciate if the community could assist me out. Thanking in advance for your contributions
Cheers,
John
John,
2- maybe one way to approach your question is to differentiate the different cloud deployments and applications
S/4HANA on premise edition
all traditional extension capabilities are still available including all types of modifications, as well as ex-app extensions with HCP.
a: If you go to AWS, this means you are using IaaS, Infrastructure as a Service. AWS only provides the infrastructure, you will be still doing all the software work as if on-premise. The only difference is that AWS provides the boxes. You will still be doing transports, security etc. Or in other words, AWS payments cover CAPEX, the customer still pays for OPEX.
b: If you go HEC, this is a full service model or MCaaS Managed Cloud as a Service. SAP will provide all work for you including providing the required levels of SLA's. Customer has one payment to HEC, no more CAPEX.
S/4HANA cloud edition
The cloud edition runs only in the SAP cloud currently (no AWS etc...and also currently not in HEC or HCP) based on the SaaS Software as a Service principles, and there are different scenarios, which are not just SAP-specific
a: SaaS Public Cloud - no modifications or in-app extensions - only ex-app extensions like in HCP
- As some people say true SaaS means all software is shared and all customers run the same release at the same time, and only data are customer-specific.- That is why of you follow SaaS principles all in-app extensions are excluded "by design".
In order to segregate customer data access, S/4HANA cloud edition is using a separate database container for each cloud edition customer. Possible SaaS deployments can also mean just a specific customer key on shared tables or a customer-specific client insoide the same, shared, data base.
Some SaaS vendor offer as an additional service an analysis across all customers' data and usage and sell for example average data patterns/usage to the other customers or for general analysis purpose.
b: SaaS in private cloud - in-app and ex-app modification scope is possible based on individual service agreements. In General the more in-app extensions are required the more expensive the service agreement.
3: Fiori
SAP offers standard Fiori and custom Fiori options - means SAP will offer a Fiori or Fiori-like screen for all S/4HANA transactions, and in addition customers can also create their own Fiori or Personas screens.
Fiori deployments are possible either as a modification, means with transports etc.., or in HCP as Fiori as a Service means as an ex-app extension.
4. greenfield
To answer your question, please see my comments under 2.
in addition, please keep in mind that;
even AWS means for many people "cloud", AWS does not mean SaaS.
Greenfield might be an option if you have a heavily modified system today, and your company wants to avoid adapting all old code to the new world (please see this video S4HANA Technical White Board - YouTube for more details ) and in addition cut down on regular and expansive custom code/modification maintenance going forward by rather using standard functionality. This is possible with both S/4HANA on-premise and cloud edition.
If your company wants to get out of the business to run data centers and apply patches and install new releases etc., then either the SaaS scenario with limited modifications or the HEC scenario might be options to explore.
Hope this helps
erich
| User | Count |
|---|---|
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.