Author: Ana-Maria Pop, Teamlead Cross Technology
Today we will talk about our second application from the Inspiricon Toolbox, Time Tracker. This application helps to manage the employees’ working time within an organization.
Why did we choose to develop this application?
There are companies, especially the ones which work with SAP, that have solutions for time tracking based on excel. We saw that Microsoft Excel is considered by many to be the most commonly used BI tool in the world, but from our point of view it is not efficient enough. That is why we have found another way to access and analyse SAP BW data, through SAP Fiori and OData service.
The backing of the Inspiricon Time Tracker application is assured by a Planning Cube. Data transfer from the backend is made possible through an Input-Ready Query which is consumed as OData in the Fiori application.
How does the application work?
We will explain the workflow based on an example:
Let’s assume that you are an employee in X Company – a company which is using a SAP ERP and they will always need BI tools for visualization, reporting and so on. Every day you work on a project and on a specific task of this project, but you need to keep track of all this.
How do you do that?
With Time Tracker! A cross browser application which allows you to stock all this information. You can do it from anywhere and from any device: PC, laptop, tablet or smartphone. It is all real time, so if your manager needs your timesheet right now in this moment, he will just have to login to the application and it’s all there. Or if you have made a mistake in your logged work, it’s only a matter of seconds to change it.
Functionality, scope and workflow of Time Tracker
The functionality is quite simple and straight-forward. Usually in SAP Fiori applications, it is a best practice to split the functionality as much as you can. For example, in the timeline case, there will be at least three applications:
- one for login the work,
- one for planning
- and one for request approval.
Time Tracker is the one to login the work.
Basically, you have just one view with all functionalities (FIG.1):
- Filter by date: The data binding between Calendar Date Interval component and the OData received was a bit tricky (because of the ACALLDAY). But we don’t give up easily! We created the mock-up with this component and the result was a success. With this component, you are able to choose a specific date or an interval to visualize your work.
- Have an overview off all logs: this is table component with search and sort as additional functions (FIG.2).
- Log your work: you just have to click the Log Work button and a dialog with a submit form will open. Choose the project, the task, add a description of what you did, the number of hours, click Log and you are done (FIG.3 and FIG.4).
- Update each logged work: is also a dialog which will open when clicking an entry from the table – here you can adjust the number of hours (FIG.5).
And this is the scope and the workflow of our second application. In the future we plan to implement the planning and the request approval applications as well.
All good things go by three
Next week we will present our third app to you– BEx Query Analyzer. Maybe a bit more technical application but also very very interesting! :)
You missed the article about our first application, Manage User? No worries, you can always read it on our blog.