The following open SQL statement looks a little weird, however it could really works in 740.
(1) The field name of my structure ty_my_sflight is different from field defined in sflight, so in SQL statement I use the format
(2) I want to calculate the percent about how many seat are occupied and put the result into my field my_seatrate. Now I could push the calculation to DB layer instead of calculating it in ABAP side.
(3) The logic to determine the flight price in the example shows that we could define some application logic in open SQL statement.
(4) Since we are using new SQL enhanced syntax in 740, it is required that all variables defined in the application code must be escaped with flag “@” when they are being used in the SQL, as is shown in line 28 and 33.
The original data displayed in SE16:
The content of internal table lt_flight is listed below. We observed that the price for the 2013-2-13 and 2013-3-13 is reduced correctly, also the seat occupation percent.
By the way, here below is a slide which talks about the optimization on two ERP transaction in HANA. There are several kinds of optimization categories and one of them also uses the similar syntax described in this blog:
The performance before HANA optimization:
The performance after optimization in HANA:
要获取更多Jerry的原创文章，请关注公众号"汪子熙":