SAP for Banking Blogs
Read and write blog posts showcasing innovative banking solutions and success stories powered by SAP. Discover cutting-edge insights and practical tips.
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member

Finance and Risk Data platform has been in news in the recent times. It was also mentioned as one of the main focus areas in the area of back office for regulatory compliance during the banking strategy presentations.  I was equally interested to know about it. Apparently I got an opportunity to present this topic to one of the developer communities and I tried to learn and build my first application using the F&R platform.


I would like to emphasize on few advantages which were obvious to me due to my previous experience in similar projects.


I was earlier involved in a project to build HANA content (HANA as secondary) for AFI scenarios. In Bank analyzer, one would probably never know underlying data base tables. Many a times, these tables are generated during the initial generation phase. Source data services are used to read data from SDL objects and data from RDL is consumed in BW system for reporting. Hence there is also no necessity to know table level details. In my earlier project we had to identify the underlying data base tables, replicate them to a HANA system, extract the texts for the corresponding tables and build HANA models based on these tables. It was a lot of effort from a modelling perspective. And any new additional fields or modifications, all the required models have to be adjusted manually.


A significant part of modelling effort can be eliminated using the F&R data platform. Let me list few steps involved in the process. An ABAP extractor program is provided in the BA system. It reads the meta data of all the SDL and RDL objects and have to be extracted and stored as XML files. These files need to be imported to the Sybase power designer environment into the local project. An additional plug in is developed in power designer for Bank Analyzer which provides logical reference data models. The extracted XML file needs to be imported which automatically generates or updates various data base entities such tables, data elements etc... And HANA artefacts can be generated just by a click based on these BA entities. And with another click these HANA models can be imported to the HANA system.


The whole life cycle of extracting the data models, replicating them, and building the HANA artefacts to deploying them can be done in very less time. These HANA artefacts can be directly consumed in the BI4.0 reporting tools for the generation of reports.


New regulatory requirements keep coming and all might not fit into the scope of Bank Analyzer. But it should also be noted that there are quite a number of scenarios which have overlapping data requirements .Integrated Finance & Risk architecture tries to address this concern and Finance &Risk platform acts as a reporting framework to consolidate Finance & Risk application landscape on one data platform. While the existing framework can be used right away to cater to standard scenarios, more complex scenarios can be built using the combination of power designer and HANA Studio features. Thus we could see modelling various scenarios such as BA, LRM, and ALM etc. on one single platform.



What do you think ?