topic Re: SQVI query display problem when published via custom t-code in Application Development and Automation Discussions

SQVI query display problem when published via custom t-code

Former Member — Thu, 30 Oct 2008 14:55:26 GMT

Hello,

A user created a custom query in SQVI and then published the generated program to a custom transaction code. This was then transported to our production environment. However, we're having some problems getting the results to display correctly. When a user runs the transaction, the results page displays without any data; there are no columns/fields displayed and no table data, just the overall query title and the ALV container where the data should be. But if that same user runs the query program via SE38 - the same program that is linked to the custom transaction code - and enters the same selection screen parameters, he gets results displayed correctly. In both runs data is found that meets the selection criteria; otherwise a "No data was selected" error would be displayed. The same user is running it in the same environment. So why does the same program display the result data when run via SE38 but not when run via the custom t-code?

Thanks for the help,

April Erickson

Re: SQVI query display problem when published via custom t-code

former_member125661 — Thu, 30 Oct 2008 15:19:37 GMT

April,

I believe this has something to do with the authorizations. How is the user accessing the SAP ? Is it from a browser ? Pls make sure

SAP GUI for HTML

SAP GUI for Windows

SAP GUI for JAVA is checked in SE93 for this transaction.

Re: SQVI query display problem when published via custom t-code

Former Member — Thu, 30 Oct 2008 15:24:41 GMT

Hi Shareen,

The user is accessing SAP using a Windows browser. The transaction code was transported to production quite awhile ago, before those options were required. So none of the GUI support boxes are checked. But the user recreated the query in our development environment, and I created a custom t-code there for the program without using the GUI support options. Even without those options checked, the transaction still worked correctly for me in development. So I don't know that checking those boxes will make a difference. But I might give it a try.

Thanks,

April