9/2/2015 How Simple Finance Removes Redundancy ­ SAP HANA

https://blogs.saphana.com/2014/09/30/how­simple­finance­removes­redundancy­2/ 1/11

How Simple Finance Removes Redundancy

Tweet 24 179Share 49

Posted by Jens Krueger (https://blogs.saphana.com/author/jens­krueger/) on September 30, 2014

More by this author (https://blogs.saphana.com/author/jens­krueger/)

12Like

At SAP, we set out to change how finance is done. Traditional systems relied on inflexible models,precomputed data, and slow computational systems. With SAP HANA and SAP Simple Finance wechanged that, to give you a more agile approach to financial management and planning. By eliminatingthings such as needleless duplication and precomputation of data which clogs other systems, we havesignificantly lowered your cost of managing Financials. And because our experience at building robustaccounting systems, we can do this without disruption to your business. By freeing your system of theconstraints of precomputed data models, we also open up your system to a more agile way ofcomputing, allowing financial analysts to quickly experiment with what­if models while speedingquarterly closes.

This blog post is the first of a series that dives deeper into various aspects of SAP Simple Finance andtheir technical underpinnings.

Recently, Hasso Plattner wrote about the impact of aggregates(http://blogs.saphana.com/2014/07/05/the­impact­of­aggregates/) and explored the negative impact ofmaterialized aggregates and why relying on them for performance severely restricts flexibility.Generally speaking, the generic term materialized view and the special case materialized aggregaterefer to the physical storage of derived and redundant data in a database. In this deep dive, we lookcloser into the technical foundations and highlight the positive impacts that can be realized whenremoving materialized views. We do this by looking at SAP Simple Finance(http://www.sap.com/pc/tech/cloud/software/cloud­erp­finance­management/index.html) –SAP’s next­generation Financials solution that for the first time does accounting without materializedviews powered by SAP HANA. We are going to explore why materialized views and materializedaggregates are no longer necessary and how removing redundant data storage in a non­disruptivemanner improves transactional throughput and lowers storage costs without compromising analysisperformance.

In this blog post, we focus on the non­disruptive changes to the data model that removed redundancyfrom SAP Simple Finance and why switching to Simple Finance is possible in an entirely non­disruptive manner. In the next two blogs we will investigate the concepts of materialized views andmaterialized aggregates, respectively, and demonstrate that it is indeed feasible with in­memorydatabase systems to get rid of these redundant constructs. Future parts of the deep dive series willalso highlight additional improvements and paradigms of Simple Finance that are possible thanks toSAP HANA and focus on, for example, the business value associated with Simple Finance, non­disruptive innovation, and how Simple Finance enables decision makers to overcome aggregateinformation loss.

In this first part of the series, we begin with exploring the concept of redundancy in general.Afterwards, we look deeper into the changes of the data model brought with Simple Finance andhighlight how this non­disruptive innovations has been possible, allowing an almost seamless switch­

9/2/2015 How Simple Finance Removes Redundancy ­ SAP HANA

https://blogs.saphana.com/2014/09/30/how­simple­finance­removes­redundancy­2/ 2/11

highlight how this non­disruptive innovations has been possible, allowing an almost seamless switch­over to SAP Simple Finance. We demonstrate the positive impact of the new data model on databasefootprint and transactional throughput.

While we focus on the Financial Accounting component, other components such as ManagementAccounting (Controlling) have similarly been changed, so our comments apply to Simple Finance as awhole. The following explanations focus on the classical data model in order to foster easierunderstanding for all readers, even those not familiar with New General Ledger Accounting (New G/L).Please note that SAP Simple Finance is using New G/L.

SAP HANA Makes Redundant Data Obsolete

Redundant data refers to data that is physically stored in a database but could be derived bycalculating it from other data in the database (Codd: “A Relational Model of Data for Large SharedData Banks”; Communications of the ACM 13(6); 1970). Redundancy is a frequent source ofinconsistency and anomalies. As redundant data needs to be kept in sync on updates, redundancy ina data model leads to slower updates. To reduce redundancy, database normalization techniquessuch as normal forms have been introduced (Codd: “Further Normalization of the Data BaseRelational Model”; IBM Research Report RJ909; 1971). Historically, redundant data has neverthelessoften been stored explicitly only to improve read performance, as the calculations to derive it in theabsence of materialization required too much additional effort.

For years, enterprise applications have employed redundant data storage in order to provide sufficientperformance to users in transactional and analytical applications alike. The limited performance oftraditional, disk­based database systems required redundantly kept data that could be accessedquickly, but needed to be updated and kept in sync with transactional changes. SAP ERP Financialshas historically not been an exception. In view of millions or billions of accounting documents(headers, stored in table BKPF) and their line items (table BSEG), materialized views and aggregatesas mechanisms to maintain redundant data provided fast access to items with specific properties. Forexample, SAP ERP Financials contained a materialized view for all open Accounts Receivable lineitems (table BSID) and materialized aggregates of the debit, credit, and balance amounts for eachcustomer per fiscal period (table KNC1).

Building on SAP HANA’s in­memory technology, it has now been possible to non­disruptivelytransform the Financials system into a purely line­item­based Simple Finance that gets rid of allredundant financials data. Thus, SAP Simple Finance overcomes the associated costs such asreduced transactional throughput and increased database footprint. At the same time, SAP SimpleFinance is a non­disruptive innovation of the classical ERP Financials because it replaces thematerialized views with non­materialized compatibility views. All applications that have read from thematerialized views, be it SAP standard reports or customer modifications, continue to access theviews as before without requiring any changes.

Although these are already big breakthroughs, the most important advantage of SAP Simple Financeis the dramatically improved flexibility that, for example, encourages exploring the data according tovarious analysis needs and contributes to the success of Simple Finance as an information system.Researchers have since long stressed the value of information flexibility – see, for example,“Searching and Scanning: How Executives Obtain Information from Executive Information Systems”(Vandenbosch and Huff, 1997; MIS Quarterly 21(1)), “Exploring the perceived business value of the

9/2/2015 How Simple Finance Removes Redundancy ­ SAP HANA

https://blogs.saphana.com/2014/09/30/how­simple­finance­removes­redundancy­2/ 3/11

(Vandenbosch and Huff, 1997; MIS Quarterly 21(1)), “Exploring the perceived business value of theflexibility enabled by information technology infrastructure” (Fink and Neumann, 2009; Information &Management 46), or “An empirical investigation of the factors affecting data warehousing success”(Wixom and Watson, 2001; MIS Quarterly 25(1)). A follow­up blog post will elaborate on the businessvalue that can be realized thanks to the gain in flexibility and the simplification.

A New, Non­disruptive Data Model with Zero Redundancy

The fundamental and essential data tuples of every financial accounting system are the accountingdocuments and line items, in this case stored in the tables BKPF and BSEG, respectively. Thetraditional data model of SAP ERP Financials – which is running on SAP HANA as part of SAPBusiness Suite powered by SAP HANA (in the following: Suite on HANA) – additionally containedmaterialized views that allowed fast access on disk­based database systems to open and cleared lineitems, separated by accounts receivable, accounts payable, and general ledger accounts (tablesBSID, BSAD, BSIK, …). As calculations and observations in future installments of this deep diveseries will show, SAP HANA’s in­memory database makes materialization obsolete thanks to theimproved performance. Hence, the decision for SAP Simple Finance was clear: the previously existingmaterialized views have been removed and replaced by compatibility views. These compatibility viewstransparently provide access to the same information calculated on the fly to ensure that the changesare non­disruptive.

Materialized aggregates in the traditional Financials data model included totals per account receivable(KNC1), account payable (LFC1), and G/L account (GLT0 / FAGLFLEXT). In addition to removing thematerialized views, SAP Simple Finance also evolves the traditional Financials data model byremoving the materialized aggregates from the system, again replacing them by compatibility views.

In the end, the transactional data model of core Financial Accounting – besides master data – consistsonly of the essential accounting document header (BKPF) and accounting document line item tables(BSEG). All the other tables mentioned on the left side of the following Figure 1 are then obsolete.Instead, transparent access to exactly the same information is provided on­the­fly by equally namedcompatibility views, as outlined on the right side of Figure 1.

9/2/2015 How Simple Finance Removes Redundancy ­ SAP HANA

https://blogs.saphana.com/2014/09/30/how­simple­finance­removes­redundancy­2/ 4/11

Figure 1: Key elements of Financials data model before and after simplification

Non­disruptive Innovation

SAP ERP Financials is being used all over the world by many thousand customers. It offers richmodification options to customer to adapt the system to their needs, including custom modifications.Changes to the core data model need to take this into account. They have to be non­disruptive withregard to the large amount of code (by SAP and its customers) that builds on top of the data model. Toensure adoption of the benefits of SAP Simple Finance, all innovations have been implemented in anon­disruptive manner. Switching to SAP Simple Finance does not require updating any customcoding for reading from the database.

So­called compatibility views have been the means to achieve this non­disruptiveness: a compatibilityview is a non­materialized view – essentially, a named query – that seamlessly replaces a materializedview (or materialized aggregate). As it has the same name and is transparently accessed via the datadictionary, existing applications that so far relied on the materialized view for accessing items oraggregates do not experience any difference. They continue to work as before without any changes tothe code. For example, a query accessing BSID has previously read the value from the materializedview. Now, the same access to BSID is resolved into a query using the view definition and calculatedon­the­fly. The result is the same in both cases. As the calculations have demonstrated, this is feasiblewithout compromising performance.

As a consequence of the non­disruptive innovation, all of the benefits associated with Simple Finance– such as increased throughput, flexibility, and reduced database size – are available at no adaptationcosts to customers – a migration of the database (mostly removing the redundant tables) is sufficient.

A future deep dive will look into non­disruptive innovation and the technology of compatibility views inmore detail.

As a benefit of the non­disruptive nature of the above­mentioned changes, code changes in theFinancials component (done by SAP) were only necessary to remove the now unnecessary writingoperations to former materialized views and aggregates when posting accounting documents. Inaddition, code has been adapted to further leverage the possibilities of SAP HANA. This includes codepushdown of data­intensive logic to the database and backend decoupling for new Web­based userinterfaces (SAP Fiori).

Reduction of Database Footprint

9/2/2015 How Simple Finance Removes Redundancy ­ SAP HANA

https://blogs.saphana.com/2014/09/30/how­simple­finance­removes­redundancy­2/ 5/11

Reduction of Database Footprint

The removal of both materialized views and materialized aggregates significantly reduces thedatabase footprint of Financials that has been occupied by redundant data. In an exemplary systemfrom an SAP customer, the total size occupied by the set of core tables for financial accounting isreduced by a factor of 6.5 with SAP Simple Finance. For details, please refer to the following table thatincludes a non­exhaustive list of tables that have been replaced by compatibility views.

Table sizes of customersystem

Table Description

ERPFinancials inSuite onHANA

SimpleFinance onHANA

BKPF Accounting documents 1.2 GB 1.2 GBBSEG Accounting document line

items4.5 GB ** 5.0 GB

BSID Open items AccountsReceivable

0.1 GB

BSIK Open items AccountsPayable

0.0 GB

BSIS Open items General Ledger * 23.2 GBBSAD Cleared items Accounts

Receivable3.3 GB

BSAK Cleared items AccountsPayable

2.1 GB

BSAS Cleared items GeneralLedger

* 5.5 GB

KNC1 Totals Accounts Receivable 0.1 GBLFC1 Totals Accounts Payable 0.0 GBGLT0 Totals General Ledger 0.0 GB

Total (of above tables) 40.0 GB 6.2 GB* Includes partially archived items (not considered here)** Includes additional fields for New G/L

The numbers shown above are in both cases already for a system running on SAP HANA as thedatabase. Factoring in the additional savings in database size enabled by HANA’s storage architectureand compression, the potential savings are even more impressive. Looking at SAP’s main internalERP system, the following Figure 2 demonstrates the end­to­end possibilities in database size

reduction. The combination of SAP HANA’s inherent compression with the removal of redundancyallows running a company such as SAP – with revenue of close to 17 billion Euro in 2013, over250,000 customers, and over 65,000 employees – completely in­memory using commodity enterprisehardware.

9/2/2015 How Simple Finance Removes Redundancy ­ SAP HANA

https://blogs.saphana.com/2014/09/30/how­simple­finance­removes­redundancy­2/ 6/11

Figure 2: Database sizes of SAP’s main internal ERP

Increase of Transactional Throughput

The removal of materialized views and materialized aggregates immediately has a positive impact onthe transactional throughput of the system. Posting an accounting document no longer requiresinserting redundant duplicates into materialized views nor updates of redundant total figures.Beforehand, especially the concurrent aggregate updates could lead to contention as materializedaggregates had to be locked for updating. In case of, for example, heavily used G/L accounts, thedatabase system had to handle the otherwise parallel postings sequentially. In Simple Finance,posting now only requires inserting the actual document and its line items. Experimentalmeasurements based on customer data (see Figure 3) have shown that the end­to­end transactiontime required for posting 500 documents with 6 line items each has been reduced by a factor of morethan 2, doubling the throughput. The number of tuples affected by the database operations for postingthe documents has been reduced by a factor of almost 2.5 thanks to the no longer requiredsynchronization of redundant data.

9/2/2015 How Simple Finance Removes Redundancy ­ SAP HANA

https://blogs.saphana.com/2014/09/30/how­simple­finance­removes­redundancy­2/ 7/11

Figure 3: Increased transactional throughput

Benefits of SAP Simple Finance in Summary

The data model of SAP Simple Finance is now exclusively consisting of line items. It is “simply”recording all business transactions as they happen. Everything else is being calculated on­the­fly byalgorithms on the data. This implies that the previously needed modifying operations to maintain thematerialized views are no longer necessary, thereby simplifying the program code and increasing thetransactional throughput.

The fact that it is feasible to remove the redundancy from the Financials data model demonstrates thatin­memory database systems enable new levels of flexibility. Instead of pre­defining materializedviews and materialized aggregates, it is possible to aggregate flexibly directly on the line items.Instead of being restricted to specific analysis questions supported by the underlying model ofmaterialization, all questions are feasible that can be answered based on the actual items themselvesvia any aggregation on top of them. An improved and user­friendly user experience adds to that andallows unprecedented user productivity and novel insights.

This first blog post of the Simple Finance deep dive series looked at the non­disruptive changes to thedata model. In particular, we outlined the practical benefits associated with removing redundancy ofmaterialized views and materialized aggregates; increased throughput and reduced database

footprint. In the upcoming blog posts of the series, we will demonstrate how SAP HANA as an in­memory database makes these changes feasible using performance calculations and technicalconsiderations.

Average User Rating

Rating: 5.0/5 (20 votes cast)

11784 Views

Previous(https://blogs.saphana.com/2014/09/29/kaeser­compressors­inc­and­sap­hana­helping­a­diverse­set­of­customers/)

Next (https://blogs.saphana.com/2014/10/01/innovation­

and­liberation­with­sap­hana­you­get­both­part­one­of­a­two­part­blog/)

Comments

9/2/2015 How Simple Finance Removes Redundancy ­ SAP HANA

https://blogs.saphana.com/2014/09/30/how­simple­finance­removes­redundancy­2/ 8/11

Comments

Vaidhya on September 30, 2014

Excellent article! keenly awaiting the next posts

Log in to Reply (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F)

Like (8137) (0)

mkr on October 13, 2014

Outstanding. I get it!

Log in to Reply (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F)

Like (8138) (0)

mkr on October 14, 2014

Can you write about central journal concept.

Log in to Reply (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F)

Like (8139) (0)

Jens Krueger (Https://Blogs.Saphana.Com/Author/Jens­Krueger/) on October 22, 2014

mkr, thank you for your interest. Yes, a future blog post will discuss the Central Financeconcept.

Log in to Reply (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F)

Like (8141) (0)

Evgenii Tikhomirov (Https://Blogs.Saphana.Com/Author/Evgenii­Tikhomirov/) on October 21, 2014

What happens if BSEG and BKPF themselves will be migrated into many fully normalized tables andreplaced by views? Clearly these are hugely redundant tables with > 300 fields.

Log in to Reply (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F)

Like (8140) (0)

Jens Krueger (Https://Blogs.Saphana.Com/Author/Jens­Krueger/) on October 22, 2014

Evgenii, the tables for accounting document header (BKPF) and line items (BSEG) remain thebasis for all financial accounting in Simple Finance (as shown in figure 1). They continue torecord the fundamental transactions and are more than ever the single source of truth, asaggregates are derived on­the­fly from them. The data in these tables is thus not redundant.Customers use the existing fields of these tables according to their needs. They will not bemigrated to many separate tables.

Log in to Reply (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F)

Like (8142) (1)

Evgenii Tikhomirov (Https://Blogs.Saphana.Com/Author/Evgenii­Tikhomirov/) on October 22, 2014

Technically, from the point of relational normalization theory, the tables BKPF andBSEG are redundant, because they’re not in 6NF.

9/2/2015 How Simple Finance Removes Redundancy ­ SAP HANA

https://blogs.saphana.com/2014/09/30/how­simple­finance­removes­redundancy­2/ 9/11

BSEG are redundant, because they’re not in 6NF.

But you’re right, I’ve completely forgot that these tables should be updated. And HANA(likely) doesn’t support view updating.

Log in to Reply (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F)

Like (8143) (0)

GBWis on October 28, 2014

I am new to SAP and trying to comprehend Simple Finance. Are the Ledgers obsolete too or thetransactions still would have to post to a ledger table ? It would be nice if Ledger updates andAverage Daily Balances don’t have to be calculated each time you post something.

Log in to Reply (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F)

Like (8144) (0)

Gregory Misiorek (Https://Blogs.Saphana.Com/Author/Gregory­Misiorek/) on January 19, 2015

GBWis,

‘Simple Finance’ is very simple, so to speak. the idea of posting an accounting entry is toactually update at least 2 balances, which in turn net to 0. aggregation has been needed forgenerating statements, but with calculation ‘on­the­fly’ it’s no longer necessary as each insertresults in a new set of subtotals that don’t exist anywhere but in memory.

Log in to Reply (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F)

Like (16415) (0)

6. Mike on October 30, 2014

Hello Jens,

I am sure that the fact that materialized views are not needed any longer will enable many new use cases that have not beenpossible before (because of the described overhead).

However, can you quantify the number of materialized aggregates that already have be removed and the potential (number)of materialized tables that remain to be removed in future? (for sFI, ERP, …)

BR, Mike

Log in to Reply (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F)

Like (8145) (0)

Jens Krueger (Https://Blogs.Saphana.Com/Author/Jens­Krueger/) on January 19, 2015

Mike,for your reference, these materialized views have been removed: BSIS, BSAS, BSID, BSAD,BSIK, BSAK, FAGLBSIS, FAGLBSAS; and these materialized aggregates: GLT0, GLT3,FAGLFLEXT, KNC1, LFC1, KNC3, LFC3, COSS, COSP.Other areas are now also replacing materialized tables with on­the­fly calculation based onSAP HANA.

Log in to Reply (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F)

9/2/2015 How Simple Finance Removes Redundancy ­ SAP HANA

https://blogs.saphana.com/2014/09/30/how­simple­finance­removes­redundancy­2/ 10/11

Like (16289) (0)

Anindya Bose (Https://Blogs.Saphana.Com/Author/Anindya­Bose/) on July 24, 2015

Hi Jens

Thanks for sharing !

What will happen to FAGLFLEXA table ?

I understand BW extractor would still work with compatibility views , but will there be anyplan to have less number of extractor based on base tables ?

Log in to Reply (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F)

Like (39356) (0)

Justin Mutinda (Https://Blogs.Saphana.Com/Author/Justin­Mutinda/) on January 16, 2015

Thanks Jens,

The non­materialized views have the same name as the replaced materialized views. Do the non­materialized views have the same structures as the replaced materialized views as well?

Log in to Reply (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F)

Like (16037) (0)

Jens Krueger (Https://Blogs.Saphana.Com/Author/Jens­Krueger/) on January 19, 2015

Justin,yes, the compatibility views (as we call the non­materialized replacement) have the same structure as theformer materialized views they replace. This ensures that all code reading from, for example, BSIDseamlessly works as before and returns the same values, but calculated on­the­fly.

Log in to Reply (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F)

Like (16292) (0)

Prabhakar Ramakrishna (Https://Blogs.Saphana.Com/Author/Prabhakar­Ramakrishna/) on March 15, 2015

At the outset it looks very encouraging, how this will playout in period­end activities to be seen. If thiscovers simple closing, SAP will rule ERP market.

Log in to Reply (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F)

Like (23112) (0)

Vittal Agirishetti (Https://Blogs.Saphana.Com/Author/Vittal­Agirishetti/) on April 22, 2015

Thanks Jens.

Log in to Reply (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F)

Like (26706) (0)

9/2/2015 How Simple Finance Removes Redundancy ­ SAP HANA

https://blogs.saphana.com/2014/09/30/how­simple­finance­removes­redundancy­2/ 11/11

Dharma Subramanian (Https://Blogs.Saphana.Com/Author/Dharma­Subramanian/) on June 10, 2015

Table size of 23.2 GB for BSIS when BSEG is only 4.5 GB does not make sense to me. Shouldn’t thesize of the materialized view (BSIS) be always smaller than the base table (BSEG)? What am Imissing here?

Log in to Reply (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F)

Like (30510) (0)

Gregory Misiorek (Https://Blogs.Saphana.Com/Author/Gregory­Misiorek/) on June 11, 2015

not sure, but it may have something to do with BSEG being a cluster and BSIS a transparent table.

Log in to Reply (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F)

Like (30570) (0)

Shashikant Sangalad (Https://Blogs.Saphana.Com/Author/Shashikant­Sangalad/) on July 22, 2015

Thank you. Excellent Article.

Log in to Reply (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F)

Like (37817) (0)

Ignacio Lopez (Https://Blogs.Saphana.Com/Author/Ignacio­Lopez/) on August 5, 2015

Hello Jens,Nice article, thanks for sharing!I did not see any comment around a HANA Live implementation – sidecar approach with SLT­. Doyou have any information on to how this simplification would impact HANA Live VDMs built on top ofthe mentioned tables?

Log in to Reply (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F)

Like (42329) (0)

Leave a Reply

You must be logged in (https://blogs.saphana.com/wp­login.php?redirect_to=https%3A%2F%2Fblogs.saphana.com%2F2014%2F09%2F30%2Fhow­simple­finance­removes­redundancy­2%2F) to post a comment.

United States © 2014 SAP SE Legal (http://www.sap.com/corporate­en/our­company/legal/impressum.epx)

(https://www.facebook.com/HANAbySAP) (https://twitter.com/sapinmemory)

(https://www.youtube.com/user/saptechnology) (https://www.linkedin.com/groups?gid=3683024)

(http://www.slideshare.net/saptechnology) (mailto:asksaphana@sap.com) Follow & Share