This blog is second part of the discussion. In first part we discussed FIORI Landscape and usability of standard FIORI UI/Apps in our FIORI implementation. In this part we will discuss following topics
1. Skill sets required
2. Development environment and tools.
Skill sets required
This should be quite simple, but in our experience, this is one of the most underestimated areas when it comes to FIORI development.
First of all, an Architect who understands how all the parts of FIORI will sit together and more importantly can figure out, at the very least, what does current infrastructure lacks.
FIORI is a front end and it can be modified in a Java environment, period. At the minimum, what that means is you will need a resource who has Java Script and JQuery experience.
You will also need an ABAP resource to work on Odata and backend queries and logic.
On the process side, you will need a cross-functional resource that can design and configure a business process. Last but not the least, a terrific business resource, who is willing to explain the quirks and requirements will be very helpful.
Don’t forget that there will be a lot of components that will need to installed before you can get FIORI going, so my advice is to have some basis time allocated on the project too. Along with basis, you will need networking gurus to figure out issue/s when accessing FIORI URL.
I will walk you through an example to make it clearer. Let’s say you plan to implement 2 business processes (apps) in FIORI. For a moderately complex implementation, it shall take about 3 months with first month for setting up the environment etc. Here is a quick break up, though I will provide details in next blog in this series with a detailed project plan.
- Architect. On and off, but a lot more time required in the beginning.
- Basis resource (About 20 hours per business process), If this is first FIORI implementation then add 100 hours. Don’t forget that he/she will need to coordinate a lot with Network team
- ABAP resources for about 300 hours
- Cross functional and Java resource for the duration of the project (480 hours)
- A fantastic and dynamic business resource/s for requirements, guidance and testing
Another helpful blog to read
Development environment and tools
Now that you know that what skill sets are required, let’s talk about development environment. For the most part backend and Odata development is done in ECC, whereas Front end UI is developed either in WebIDE or Eclipse. Web IDE publishes the UI5 application to ECC using HANA cloud connector (HCC).
Odata is accessed using transaction SEGW in ECC. Any modification to Odata should be done here.
Here’s a depiction of what we had for the development environment. Also, please note that no basis resource to set up development environment is required for this since all this resides on your PC/laptop.
Here are the steps you need to go through to install WebIDE.
- SAP WEBIDE should be installed on your laptop. You will need admin access to your machine and access to internet to get it working.
- Also download HANA cloud connector (HCC)
- Set up a user id for HANA cloud connector (HCC) and WebIDE
- WEBIDE should be connected to HANA Cloud connector.
- In HCC, you will enter the details of your SAP environment and your log-in and password.
6. Once you are logged in, you shall see all UI5 objects that are available.
At this stage of our discussion FIORI components are installed and development environment is set up.