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.
We get this screen
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?
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.
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
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.
PS: This post and all further posts in the area of Infosets have been compiled to this blog Infoset Queries: Collection of important posts