Skip to Content
0

Are characteristic restriction pushed down to HANA view

Mar 29, 2017 at 11:33 AM

201

avatar image

Hello All,

I have a BEx query created on a composite provider. This composite provider has a union node with only a calculation view. The BEx query is expected to fetch the data based on fiscal period that user has requested.

So the question is - when the user enters the value in the prompts (used in characteristic restriction of BEx query), will HANA fetch only the required data and then perform the operations in view (or) will all the be processed in HANA and then filter is applied for required fiscal month.

This question is basically to understand the impact of the design process on performance of BEx query.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

4 Answers

Frédéric Cincet Mar 29, 2017 at 04:07 PM
2

For sure, your filter will be pushed down to the calculation view (which is managed by Hana). If the filter will go down up to the physical tables will depend on the way you build your calculation view. The plan Viz of your calculation view will show you if this is the case:

Regards,

Frederic


capture.png (12.5 kB)
Share
10 |10000 characters needed characters left characters exceeded
Vikram K P Mar 31, 2017 at 11:16 AM
0

Hi Frederic,

Many Thanks for your reply.

Can you please let me know how did you generate planviz for BEx query execution.

Plan view of CV is as below and when I ran with where condition on fiscal period (say 2015.011), I see that filter is pushed in HANA and overall performance is in terms of milliseconds.

Following is the design of Composite provider.

And I have BEx query on this composite provider. Please note that the Characteristic restrictions have fiscal period at BEx query level and not as input parameter in HANA view.

Now if I see the statistics of BEx query, I see that performance is as below.(screenshot of both the tabs were taken in two separate runs and hence they are not same)

If we see, the performance is very slow when compared to HANA view execution.

Can you/anyone suggest me what is going wrong in here. It is taking 5 seconds to fetch 1 record.

Where as HANA seconds takes in milliseconds.

Thanks and Best Regards,

Vikram


capture-plan.png (20.5 kB)
capture2.png (14.8 kB)
capture5.png (4.6 kB)
capture7.png (8.7 kB)
capture4.png (39.4 kB)
capture8.png (29.5 kB)
capture8.png (29.5 kB)
Share
10 |10000 characters needed characters left characters exceeded
Frédéric Cincet Mar 31, 2017 at 11:49 AM
0

Try to catch the SQL query generated by your query execution (for instance with an SQL trace - ST05) and see if the selection on FISCPER is there.

Regards,

Frederic

Show 2 Share
10 |10000 characters needed characters left characters exceeded

Hi Frederic,

Many Thanks for quick reply.

I checked the with SQL trace. The line which is taking a lot of time is as below.

There is no information on SQL statement. Is there any way to find out what SQL is fired against this statement.

Thanks again,

Vikram

0

I can't see the image on your comment.

0
avatar image
Former Member Oct 31, 2017 at 04:57 PM
0

Hi Vikram,

Did you get anywhere with this? We are seeing similar issues.

Many thanks.

Nick.

Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member
0