Context
Every department had its own list, with its own columns, its own rules and its own mistakes. None of them could be compared. IT only saw the numbers once they were in the system, and by then it was too late to check them.
Approach
One app that works the same way for all evaluation types and departments. It checks the entries while they are being filled in and once again when they are saved, then it writes the result straight into the system. The list and the retyping are gone.
How it is built
The frontend is SAPUI5, the backend runs on SAP RAP, the data lives in an ADSO in BW. The check rules sit in the RAP model, the frontend only displays them. That way the same rule applies, whether the entry comes from the app or from somewhere else. The app is embedded in the intranet so the departments reach it without a detour.
| Component | Technology | Decision |
|---|---|---|
| Frontend | SAPUI5 | One interface for all evaluation types and departments |
| Backend | SAP RAP, ABAP | Validates the entry for good and writes it away |
| Data store | ADSO in SAP BW | The result lands in BW directly, not in a list |
| Check rules | RAP model | The same rule applies, wherever the entry comes from |
| Access | Intranet | The departments reach the app without a detour |
Learnings
- One app for several evaluation types is only possible when the differences sit in data, not in code.
- Checking in two places is not double the effort: the frontend makes the entry pleasant, the backend makes it binding.
- The mistake happened during the transfer, not while filling in. That is exactly the step that is gone.