

So how can you capture the semantics of the data model in the database so that the model can be easily reused by different consumers, e.g. They should be clear and unambiguous, reusable and flexible, even extensible. High-quality data models should provide a single definition and format for the data.
#Sap hana studio null handling code
It is logical to conclude, from the Paradigm-shift of Code Pushdown, that to enable real-time businesses in HANA, we need some of these services ideally also brought closer to the database as well.įor SAP this presented several challenges. Well, this is also true for the underlying data models of the business applications.ĭata modeling in ABAP typically involves organizing your data in database tables/views and often providing some additional high-level services for the applications using the appropriate ABAP frameworks. This was coined as “Code Pushdown” by SAP. The rule-of-thumb is simple: Do as much as you can in the database to get the best performance. He can be reached at we described in the prior blog The ABAP Developer Road Map to SAP HANA, with the advent of SAP HANA, there has been a paradigm shift in the way business applications are developed. Jon’s focus has been in the areas of ABAP OOP and ABAP Web Dynpro. Jon has over 5 years experience with SAP, with a concentration on ECC SD, MM, and IS-OIL modules.

Jon is also the President of Andre Technical Consulting LLC located out of Centreville, Virginia. Jonathan Andre is a lead ABAP developer at IT Partners.
