- "All problems solved mentality
- SAP HANA will not improve your requirements management
- SAP HANA does not solve any technical-conceptual or implementation-related problems.
- The processing time also increases in SAP HANA with the complexity of the task.
- Detailed drilldowns were rarely carried out on leisurely working databases with large amounts of data and problem cases remained hidden.
- If dependencies were not consistently taken into account in the existing ETL automation, a new automation of the loading processes is appropriate due to the greatly changed loading speed.
SAP HANA drives differently
Are you planning a migration to SAP HANA? We'll show you the challenges that need to be considered and the advantages of a migration. After the migration, we recommend a regular assessment of individual components or the entire system, as this saves you a lot of time and increases user satisfaction.
What challenges does a migration to SAP HANA pose for application development?
What is SAP S/4HANA?
With S/4HANA, SAP has developed a database that can process data much faster than conventional databases thanks to in-memory technology. The in-memory technology no longer accesses hard disks during data retrieval, but keeps all data ready in the working memory. In this way, data can be analyzed and processed almost in real time - which greatly accelerates business processes in the area of big data. On the software side, SAP S/4HANA uses a combination of column- and line-oriented working methods. HANA was initially developed for business intelligence and business analytics applications and used for SAP Business Warehouse and Business Objects Strategic Workforce Planning. S/4HANA can also be used to run other SAP products and all SQL-based applications.
Why should an application optimization take place after the HANA migration?
From a technical point of view: In the many application cases, the last persistent data layer can be completely dispensed with, i.e. allocated storage space is permanently reduced through the application and the application is streamlined.
From a business perspective: Migration to a HANA database usually takes place in combination with an SP upgrade. BI tool development under 7.4 is very dynamic, with numerous improvements for development and administration.
What is checked in a review?
Like mechanical devices, BI systems are subject to wear-like effects:
- Other/changed user behavior and needs than originally planned
- Increasing amounts of data / missing indexes and archives
- "Small" subsequent extensions of the original data model with disproportionately large effects on stability and reporting speed.
When does a Review make sense?
The ideal times for reviews are:
- After the creation of the specification sheet/technical specification
- Immediately after the GoLive (if necessary after the pilot's GoLive)
- Depending on the scope of the subsequent adjustments, half-yearly/annually after GoLive
Why should this apply to you?
The areas of tension
- "Fast solutions" versus "integrated solutions"
- "departmental data" versus "shared data"
- "latest BI tools" versus "proven BI tools"
- "the new colleague knows the new tools"
regularly lead to procedures that are objectively difficult to comprehend and subsequently to questionable design decisions.