Skip to Content


Often it is seen that. Infoset-query users, stop exploring  at the 1st hurdle and switch to ABAP report programs, for requirements a little bit beyond simple ones. But, it is the author’s experience, that we can use this tool (Infoset Query) given to Functional people by SAP,  to reach very close to the ABAP report programs, with features like those discussed in the other document and also some discussed here.

In this document the author tried to put together the pieces of his knowledge to present in the form of a document.


To have a Tcode to your work in Infoset Query.

The following screen with report name appears..

Now you give this report name to your ABAPer and ask him to create a Tcode


You do it yourself through SE93 Tcode, if you have access.

Steps for SE93

And Save. Thus your Infoset query will now be working with Tcode ZTCODE

(This applies also to Quick Viewer report SQVI)


Calling Reports from Infoset Query reports.

The output of your query contains key fields like Notification no., Equipment No. etc.

It is natural that one wants to go to the Notification screen or the Equipment screen from the output.

Do this way.

In SQ01

We get this screen

Click here on  then on  then select

In the resulting pop-up, specify the Tcode you want to link with the Row in the SQ01 output.

Say IW23 and Save.

It is Done.

Now upon D’clicking anywhere on a particular line item in the query output, you are directed to IW23 screen of the notification of the line-item (row).

You can have many such report assignments.

Suppose you want to have IW22 also. Then repeat the same steps above to have IW22 Tcode.

Now when you D’click (anywhere) on one line-item (row) of the Query output, you will be presented a pop-up menu to select which one you want. i.e.,

Display Notification  or Change Notification. You are taken to the corresponding screen as per your choice.



1.If your Report Assignment option is found disabled, then the reason and setting to restore is here: How to make ‘report assignment’ available in ‘SQ01’

2.We always need to remember that, after Tcode assigning, the modifications done in SQ02 or SQ01 would be in effect to the Tcode, only after executing SQ01 once.

3.More Details on this subject here: Calling Reports from an Infoset Query


Make your report colorful with giving different colors in order to group columns

In SQ01 Basic List Screen

Here just Drag & Drop the color from Right Tool-Box to the desired field in the Centre portion.


Double click on a field in the Centre, to display field details and color options on the left. Now you select the color.

Example of such output.



Always have Selection Fields from Infoset (SQ02).

What does this mean and Why?

This means

We have options for Selection Screen designing both in SQ02 and in SQ01.  It is advantageous if we declare selection options in Infoset (SQ02),

Here is how we do it. (In the Extras area), Go to Selections Tab, Click on Create icon, select Selection Criterion or Parameter like below.


And define the Selection field as under.


Observe here the strings written in Extras field.

OBLIGATORY makes this field in the selection screen mandatory.

NO INTERVALS removes the selection range (Removes the To field of the selection criterion)

NO-EXTENSION removes the multiple selection push button

DEFAULT ‘M2’ provides the M2 value as default in the field.

Like-wise you can design a selection screen as shown below by defining fields one after another.


Note that, we can declare only Standard Selection Fields here. Additional Fields are to be taken into Selection Screen only from SQ01.

The disadvantage in having these standard fields into selection screen from SQ01 is, the previously used values reappear as defaults for new running of the report. We need to erase and type our values. Also there is no provision for making a field mandatory.


This is to develop queries in Standard Area rather than in Global Area.

What is this?

See the option below in SQ02 while creating an Infoset Query.

In the Query Areas above we have two options: Global Area, Standard Area.

When we are working in Development Server (client 200 or 210), we work in Global Area option, which generates a transport request, subsequently this will be transported to QAS and PRD at the end of work.

When we select Standard Area as the name indicates, it is client-specific. This means you can directly develop in PRD with this option. To have a Tcode for reports developed so, we need to use the same way explained earlier in this document. But  it is to be noted that, we get the report name from the PRD client where we developed the report, and create a Tcode in Development server (client 210 or 200) and same will be. transported to PRD.  (One time job)

The main advantage I always enjoyed here is, the moment some addition/deletion/modifications performed on this repor, it is instantly available in PRD.

(No hassles of transport requests). Only requirement is to run SQ01 once. The Tcode will be giving the changed report.

Also, the testing of the the report work is done in a perfect environment with real-time data.

(Working through the Global Area option in Development clients may be having its own advantages, like work back-up , but I never felt such necessity in my environment.If needed we can have a copy report in PRD itself)


In case we do not want a certain category of records in the output, then go to SQ02 –> Extras–> Code tab –> Record Processing section, and

Give a code like the sample given below.

( check viqmel-abckz <> ” . )

What does this do?

With this code, the Infoset query does not bring any records where the ABC indicator field is blank.

Like-wise if you give a code like: check crhd-arbpl <> ‘xyz123’.

the output will ignore the records with maint. work center value ‘xyz123’.

(Note that these are permanent filters, For optional filters either the Selection Screen OR the Filter in the  ALV output display can be used.)


F4 help related

F4 Help is not available in infoset query.


How to create a radio button in SAP Query SQ01/SQ02.


User defined fields


We know that, the infoset reports work on Table joins in Infoset. In complex cases, where many tables are joined, the correctness of report depends upon the quality of joins we define. Though system suggests some joins, user can define more joins as per his table knowledge. This is what controls the multiplicity of identical rows appearing in the output sometimes.

It is seen that in situations where the user is unable to control the duplicate (or multiple) identical rows , the CHECK statement used in Tip6 works conditionally. In other cases this multiplicity becomes one of  the points where one is forced to go for an ABAP report.

The author has been working in this area since few years. This is an effort to share his knowledge about some very common requirements in this area with the forum. Hope member friends especially those who love Infoset queries, find this useful.

Thank you


PS: This post and all further posts in the area of Infosets have been compiled to this blog Infoset Queries: Collection of important posts

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member

    Hi Jogeswara,

    Good Day!

    Very nicely documented. I appreciate all your time, effort and support.

    Keep up the good work! Keep sharing and motivating us forever!

    Have a nice day! 🙂


    Hari Suseelan

  2. Mayur Priyan


    First I would like to appreciate your work. I would also like to add a point regarding creating T-code to the query report, as stated.

    It is seen that the Query report name usually changes between systems i.e. Development, Quality and Production.

    Hence while creating T-code it is advisable to assign the T-code based on the User Group and Query name instead of the Query report name generated.

    Please find the procedures to do the same.

    1. Make a transaction with parameters transaction from se93 .

    2. Put START_REPORT in the transaction

    3. Check the skip intial screen checkbox

    4. in the table control in the end of screen put these values



    (G stands for GLOBAL AREA:)(Entered after a space)(G should come after 9

    chanracters(8 char for user group,one space and then G)


    Note: Though you have mentioned to use the query report name as in the PRD system, the method which I have stated is usually recommended.


    Mayur Priyan

  3. Former Member


    useful and very nice documentation.

    Is possible insert authority check into INFOSET for example about plant?

    And if is possible where i put this check?



    1. Jogeswara Rao K Post author

      Hi Srinivas,

      Really Documents like the present one involve efforts and their objective is fulfilled when few members learn from them and these efforts are rewarded when experts like you recognise.

      Thanks again 🙂

  4. Former Member

    An excellent document in itself and a valuable contribution of Mayun to help run the Tcode and Query in all Servers (Development/Quality/Production).

    Unfortunately TIP 2 works only for some transactions like Notifications/Equipment/Batch/Stock etc. But it is failing to Run MM03 and other kinds of report. Is there any way we can set the parameter id of the double clicked row?

    Sorry I am asking question here but sadly 🙁 because of this only requirement I have to change a perfect working SQL Query created report to ABAP.

    Keep it up !!!!!

    1. Jogeswara Rao K Post author

      That’s really a difficult question for me Frank. I consider this is a limitation in query area and at such requirements, I switch to full pledged ABAP report programs. Due to scarcity of related knowledge around, this topic is still in ‘yet to learn’ list of mine.


      Jogeswara Rao K

  5. Former Member

    Thank you Jogeswara Rao for sharing this, its really helpful for those using infoset query and avail the different functionalities of it.



  6. Former Member

    Jogeswara Rao garu,

    your work is really adorable and gratifying thanks a lot for documenting, your efforts are really appreciable.. lot many are getting educated with your stuff.  great work, keep posting.  All the best.

    Ram kumar

  7. B V Yadav

    Hi Jogeswara rao sir,

    I have created one quick viewer Report through SQVI transaction code and I have created on Tcode assigned with programe as you said in TIP:1, when I run this Tcode I am getting run time error. Please give some suggestion

      1. B V Yadav

        yes, I got the output SQVI by direct execution. when i run through Tcode it showing run time error. what could be reason, how to solve it?

    1. Jogeswara Rao K Post author

      1. Check for proper copying of the program name

      2. Run the program through SE38 and see.

      3. If problem persists contact your ABAPer for debugging to locate the fault

      4. Also take help of BASIS

  8. Nicolas Giuffrida

    Mr. Kavala,

    I found your post super interesting.

    Can you please help me out with this issue?

    I add a check box in the  Query Selection Screen as you indicated, but it appearing in a “General data selections” frame, I see that the check box recently added as not checked the Standard Selection check box, I cannot check it due it’s an output only box.

    How can I take my checkbox out of the “General data selections” frame?




    1. Jogeswara Rao K Post author

      The checkbox will be in General data selections block only, because we are creating it in Infoset (SQ02). I’m afraid there is no other alternative to this.

      I could not follow these lines.

      I see that the check box recently added as not checked the Standard Selection check box, I cannot check it due it’s an output only box.

      You should be able to Tick the checkbox with mouse click.

      1. Nicolas Giuffrida

        Sorry, let me rephrase

        How can I get this option checked so I can see Checkbox parameter out of the frame?


        Do I have to set something in SQ01? Can you please help me here?

        Thank you very much.


        1. Jogeswara Rao K Post author

          Hello Nicolas,

          This checkboxes are ticked for the Standard Selection fields provided by the system in Infosets where Logical Databases are used. These are provided by the LDBs. I do not think we can define our own selection fields a Standard. I never tried to tick these checkboxes neither any such requirement arose. Both checkboxes next to Standard are ticked automatically when we use ‘Obligatory‘ word in the Extras field. Standard checkbox setting is not in our control. These things we can not control from SQ01.


          1. Nicolas Giuffrida

            Thanks for your answers, I finally managed to take the checkbox out of the frame.
            You just need to declare the checkbox parameter in the Data read. prog secction.

            I hope this help someone else.




    1. Jogeswara Rao K Post author

      Hello Rajesh,

      These are queries on specific tables which I feel, do not fit in this thread. There will be multiple advantages if you start a new thread either in ABAP space or Finance and Accounting space. (Also I do not have exposure to Accounting tables)

      Best of luck



Comments are closed.