Core Data Services

Classic ERP architectures quickly reach their limits in the insurance industry. In order to record and process 20,000 financial statements and portfolios across multiple systems, classically structured ERP architectures quickly require up to 24 hours because many influencing factors lead to high complexity. As a result, however, this is not only too slow, but also torpedoes further inquiries.

To accelerate computing processes with the SAP commission module FS-ICM (Financial Services, Incentive and Commission Management for Insurance), more and more insurers are turning to fast-working, flexible in-memory architectures; with these, calculations and data transformations no longer take place at the application layer: Code pushdown, i.e. operations directly in Hana, succeeds in transmitting lean, already fully prepared data streams to the application layer. Core Data Services (CDS) are the linchpin of this design.

CDS allow data to be processed in Hana in real time. On the architecture side, the in-memory solution replaces the data storage layer with a direct connection to the NetWeaver integration component. Since fewer transformation steps are required, operational speed is accelerated. Fewer implementation steps are required for new developments. In addition, classic ERP architectures usually provide commission clerks with business data with FS-ICM with a time delay and information is also not transparent. For example, compensation information can literally force employees who have not set precise filters to take a coffee break until the data has been prepared.

In-memory constructs, on the other hand, expand the application possibilities enormously. For faster and more appealing commission data evaluations at the user interfaces, Hana makes it possible to link a Fiori app with the core data services. This allows clearer, intuitive front ends to be built. The list tools ALV-Grids (SALV IDA) improve the existing SAP GUI: The applications read Hana directly, bypassing the application server. Search functions and autocomplete with a fuzzy search also facilitate fuzzy searches. If clerks enter a similar-sounding customer or agent name with the wrong spelling, the data records they are looking for can still be tracked down.

Those who rely on code pushdowns can streamline their development processes. IT departments do not necessarily have to use database procedures or Abap Managed Database Procedures (AMDP). Rather, it is more important to develop and apply CDS views with a sense of proportion. This simplifies maintainability as well as future implementations that are not covered by the SAP standard.

Download as PDF only for members. Please create an account Here