cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with Prompt value display time after selecting from LOV

Former Member
0 Kudos

We have an A-OLAP report based on a BEX query. When the prompt screen appears and LOV is selected, it takes a lot of time to load the values. This time, though, very much similar to the time it takes in BEX Analyzer as well. But, the main problem is when the values are selected, it takes unusually long time to show up those values back in the prompt screen. Whereas, BEX Analyzer shows the selected values instantly.

We are unable to detect as to why it is so? If anyone has any idea or solution, kindly let me know.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Soumya,

Try by Re-Starting DSL Bridge Service or Adaptive Processing Service. Sometimes these services might also be the reason for this kind of issues....

Regards,

Raju

Former Member
0 Kudos

Hi Soumya,

I'm having a bit of trouble understanding where you're experiencing slowness in the application. Could you elaborate a bit further and perhaps include a screen shot of when you experience the delay? Is it after hitting "OK" in the prompt dialog?

Best regards,

Philip

Former Member
0 Kudos

Hi Philip,

Thanks for your reply. The slowness is experienced after the prompt values are selected from the List of Values screen and you hit Ok and come back to the Prompt screen. The reason why we consider this slow is because in BEx Analyzer, it shows the selected values instantly.

Let me know if that answers your question.

Thanks

Soumya

Former Member
0 Kudos

Hi Soumya,

Yes, you've answered my question. Unfortunately or fortunately, I'm not seeing the same slowness. How many values are being chosen? In my quick test, I chose 71 values and it populated the prompt dialog instantly. I'm assuming you're choosing more than that.

Best regards,

Philip

Former Member
0 Kudos

Hi Philip,

Strangely, the number of values isn't really having much effect on the slowness. Time taken for one value and for more than 50 values are same. Finding the root cause of this problem is our primary focus now. Backend i.e. BW 7 should not be a problem here as the values are already chosen when slowness is observed.

Does anyone have any expert opinion or suggestion on this? Thanks in advance.

Regards

Soumya