Skip to Content
Technical Articles

SAP Query gets Dump after new query or change, import a query & also occurs every time a release is upgraded.

Introduction

Hello Everyone, It’s my second blog post, On SAP Query dump created from SQ01 after ECC to S4HANA upgrade. I got up with a solution for the same.

Overview

The system displays the below error when you Run the Query report created from SQ01 after migration from ECC to S4HANA.

Please follow the below Step to overcome the above error.

  • Copy the program under Short Text

i.e. In my case, I got the error in program  AQL4SYSTQV00002QINSP_TYPE.

  • Enter Tcode SE37
  • Enter Function Module – RSAQ_DECODE_REPORT_NAME
    • Then press F8 (Execute)

Now on the below screen;

  • Paste the copied program under REPORTNAME
  • Press F8 (Execute)

You will get some of the results according to your REPORTNAME

Copy the USERGROUP & QUERY

  • Now, Execute Tcode SE38
  • Enter Program SAP_QUERY_CALL

Press F8 (Execute)

Paste the USERGROUP & QUERY

Press F8 (Execute) and This will Open up your Query the same as before.

Also, the is a shortcut for the same. But I’m not sure that it would always work or not but here is another way.

Suppose you get the program as AQL4SYSTQV000002RTGDATA

————————————————————————————————————————————-

Thanks for going through the detailed document. Do revert back if you have more queries or feedbacks/ inputs so that I can update the document.

And here is the link to my first blog post on Simulating BAPI.

https://blogs.sap.com/2019/07/29/bapi-simulation-finding-bapi/

 

Best Regards,

Raj Sinha.

6 Comments
You must be Logged on to comment or reply to a post.
  • I think it should be reported to SAP as a bug, because running a query from a standard transaction should make sure the program exists and should be regenerated if needed.

    Something I notice is that this program corresponds to a quick view (pseudo user group SYSTQV…), so it should be executed from SQVI by the user who created it, not from SQ01.

    About the way how to find out which query it corresponds to, you have the information that it’s a client-specific (in the “standard area”) query created in client 500, so the user should log in client 500 to run SAP_QUERY_CALL. You may also simply use the transaction code SQ01 to access the query. For information, if the program is prefixed AQZZ… it means it’s a cross-client query (“global area”), so the client is of no importance.

    Maybe you can generalize the title of your blog post because there’s nothing specifically related to the upgrade.

    There’s some interesting information in the note 393160 – SAP Query: Using queries about program not found (it also says that the report SAP_QUERY_CALL is a template for creating custom code to call queries).

    • Thank you, Sandra, for adding up your valuable comment to this post,

      ‘As the above issue was reported to me at the time of the S/4Hana upgrade. So I justed posted up the blog with that name.’

      Best Regards

      Raj Sinha