Many customers are evaluating SAP Fiori and SAP Cloud Platform to improve the user experience of SAP solutions. SAP Fiori Cloud fits exactly in this kind of request, accelerating the pace of innovation, allowing SAP users to benefit from the new user experience SAP has delivered.
In this series of three Blogs I’m going to describe the steps that should be followed to connect SAP Fiori Cloud Extended Demo Account to a customer landscape.
We have followed the 12 steps described in @Elizabeth Thorburn’s Blog series.
You can get access to her blog series at: https://blogs.sap.com/2016/06/16/back-end-connectivity-with-sap-fiori-cloud-edition-extended-demo-account-part-1/
We have activated one of the most requested app for SAP customers, the Fiori App “Approve Purchase Orders”.
The 3 blogs series consists of:
- Part I – Describes the initial steps (A1 & S1) and architecture of the solution.
- Part II – Describes the technical steps that must be carried by a system admin (steps S2 to S6).
- Part III – Describes the business steps that must be carried by an Application Consultant (steps A2 to A6).
As a result, you’ll have the step by step documentation of what we did in the 12 steps to activate and Run the Approve Purchase Order App.
A1. App Selection
The customer request in this case was very clear: Approve Purchase Orders using a mobile device.
We have used the Fiori Apps Library to get the information of what the App does, see some screenshots, and get technical information of the software components needed to set it up.
So, the selected app was: Approve Purchase Orders. Follow the links for the documentation:
We have some possible architectures for connecting Fiori Cloud to the On-Premises customer landscape.
The main difference is that the Fiori Front-End Server moves to the cloud, as described in the following diagram:
In our case, we used landscape option 1, with SAP Gateway Hub installed separately from SAP ERP. This configuration adds some steps to config the relationship between SAP Gateway Front End Server and the Backend.
* Remark: In our case, the backend server used was a SAP ECC installation. Keep in mind that when the backend used is SAP S/4HANA, the SAP Gateway On-Premise may be still necessary since the SAP CP OData provisioning services does not fully replaces the SAP Gateway server capabilities. For more information and restrictions, please check the SAP note 1830712.