[Link]

v=F-lTAd1m3ZE

[Link]

[Link]
Creating+a+SAP+Query+and+Ad-
Hoc+Query#CreatingaSAPQueryandAdHocQuery-
[Link]-CreatingtheSAPQuery
Transaction Code assignment for Query created in SQVI
1) Go to SE93

2) Maintain the zee tcode you want and click Create

3) Maintain a short text relevant to that tcode

4) Select the button "Program and selection screen (report transaction)

5) Maintain TCode text and the relevant program name

6) Maintain tick for all under the tab "GUI support"

Step 1: go to SQVI t code and enter your query name and press enter

Step 2: In the menu path select Quick view additional functions Generate
Program

Step 3: After Generating the program In the menu path select Quick view
additional functions Display report Name

Step 4: Now in se38 enter the report name in Program field and execute

Step 5: You will get the Initial Selection screen of the report . Go to Menu of System
Status

Step 6: Note down the Program name and Screen number

Step 7: Go to SE93 and Create a Z tcode for the query, Enter the description and
importantly you have to select the 2nd Option radio Button Program and Selection
Screen (Report Transaction) and Press enter

Step 8: In the next screen enter the Report Name in Program field and enter the
screen number

Step 9: In the classification Section select Professional user Transaction

Step 10: In GUI support section select all the options i.e SAPGUI for HTML, Java,
Windows
and save

The system will ask for Package select your package if not there then select local
object
now execute the Z tcode your report will run successfully

USEFUL

How to move SAP Queries, Infosets and User

Groups to another client or system (DEV, QAS,
PRD)?
Moving objects from one client to another normally requires a transport request. We
created our query in the test system, which is not set up for automatic change
recording and does not generate transport requests. An easy way to move queries
between clients and systems is to use download/upload. Note that this functionality
can only be used for Standard Area queries, not for Global Area Queries.

As we created the query in the Standard query area, we can use the
download/upload functionality to move queries between clients and systems.
Content list

Download / Upload
queries
Transport tool
Downloading
Uploading

Download/Upload queries

The download/upload functionality is available in the query transaction (SQ02

Infosets). On the initial query screen (SQ01) choose menu Environment/InfoSets.
Ensure that you have the Standard Query Area selected.

There is transport button in the bar (can also be found under menu Environment).
Click on the button.

In addition to queries, you need also download the User groups and InfoSets
associated with the query.
Transport tool

The transport button opens the the transport tool display. In case you don't see the
Download / Upload buttons, you are probably in the Global Query Area. Change the
area under Environment/ Query area.

Our Transport Action Selection will be Download/ Upload. Download is used to create
text files that containt the object definitions. With Upload these definitions are
imported to the target systen.

Test run is automatically checked. Uncheck it when you are ready for the actual
Download.

The choices below Test run are for Export, Import and Copy. This means that
variants saved in queries or report-to-report interfaces (reports assigned to queries)
are not copied with Download and must be recreated in the target system.

In Transport Option Selection area there are boxes for user group, InfoSets and
Queries. Below the transport of InfoSet VBRK_VBRP is defined.
The work order is following:

1. Download the user group(s) or create them manually in the target system
2. Download the Infosets
3. Download the relevant queries
4. Log into the target system
5. Upload the files

Downloading

Download is selected. Test run is unchecked. Transport InfoSets is selected and

VBRK_VBRP is entered.

Start the Download with the clock.

A pop up appears. Enter a file name and select the directory where the text file is
saved.

Select Option Transport Queries. Enter the Query name SD_BILLING.

Uncheck the Test run and start the transfer with the clock.

A pop up appears. Enter a file name and select the directory where the text file is
saved.

Now we have created two text files containing the definitions of one InfoSet and a
query.

I did not transfer the User Group. Maybe I created it manually or it already existed in
the target system.

Uploading

Log on the target system, where you want to move the query definitions.
The Upload is done in the same place as the Download. In SQ01 from
Environment Menu InfoSets (or transaction SQ02), click on Transport
button.
In Upload no object definitions are needed. The systems recognizes the object. Just
select Upload, uncheck the Test run when you are ready to start the actual transfer.
Choose whether you want allow ovewriting, if the InfoSet already exist in the target
system. Start with the clock.

Select the text file from the file list.

My Import log tells me that I have imported an InfoSet replacing an existing InfoSet.
The assignment to User area FI_AR did not succeed, because the User group was not
there. However, this is only a warning and the InfoSet is created. Before I can use it, I
must create the User group and assign the InfoSet.

Next do the same procedure for the query.

You have now successfully copied query defining from one system to another and
are ready to test the query or assign it to Area Menu. Remember that the report
assignment (in our case drill down to SD invoice) was not copied and must added to
the query. Also any variants used, must be recreated.

10 Useful Tips on Infoset Queries

Introduction
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.

Tip1
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

OR

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)

Tip2
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.

Note:

[Link] your Report Assignment option is found disabled, then the reason and setting to
restore is here: How to make ‘report assignment’ available in ‘SQ01’
[Link] 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.

[Link] Details on this subject here: Calling Reports from an Infoset Query

Tip3
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.

OR

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.

Tip4
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.

<img />

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.

Tip5
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.

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.)

Tip7
F4 help related

F4 Help is not available in infoset query.

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

Tip9
User defined fields

Tip10
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.

Move Query from One Client to Another ( SQ01)

40 total views
Moving Query / Infoset from one client to another.
1. Generally a query can be created in the standard area or in global area, You can
find then when you enter the SQ01 Query screen.
2. Now as a per-requisite to download the query you need to have them in the
Standard area.
3. IN case if the query was in the global area you need to move to the global area.
For this select SQ01>Environment>Transports .

4. Now select the Copy Global to Standard

5. Now run in test mode and later in real mode to copy the query to standard area.
6. Now when your query is in the standard mode then again go to the environment
and now you will find the download button. with this provide the required information
to the Infoset / Query and download to the local server
7. After this go to the target client and then set the import area as standard area .
8. Import the same in this step.
9. Assign them to the user group.
10. Execute.
Note: This will address your requirement and not intended to replicate all the steps.
for any doubts and query leave a comment.
How SAP Consultants Create Queries with These Three
T-Codes
Queries in SAP are report-building tools, and functional SAP
consultants can use them to develop simple ad-hoc reports. This
blog post will talk about the transaction codes SQVI, SQ01, and
SQ02, which can be used to create these queries.

It’s important to know how to use these T-codes since it will help
streamline the reporting process and provide queries to business
users in a timely manner. Let’s dive right in and see how they
work.

SQVI
SQVI is a simple ad-hoc report that can be written directly in the
production system, meaning there is no need for transporting
information between systems. Any functional consultant (or even
business user) with a good understanding of SAP tables can write
a query with SQVI.

Let’s consider this use case: The client has requested from you a
report that displays billing information for both the customer and
customer group.

To get this report, go to transaction code SQVI. Type in a unique

name for your QuickView (the term QuickView inspires the “QVI”
in SQVI) and hit the create button.
Next, fill in the title and comments fields. There are three options
for picking a data source; in this case, you would pick table join,
select the radio button for Basis Mode, and then hit the green
checkmark.

On the next page, you’ll hit the Insert Table option, or hit Shift +
F1. (Pro tip: always insert the primary table first and then the
other tables. SAP will not allow you to delete a primary table, but
you can delete secondary tables if needed.) For our example we’ll
add VBRK first, then VBRP and KNVV.
SAP automatically creates joins between the tables. You can
delete or change the definition of the join by right clicking on it.
For this example, let’s delete the joins between VBRP and KNVV,
and manually create joins between VBRK and KNVV. We will link
the Sold To field from VBRK to Customer Number in KNVV, and
link Sales Org from VBRK to Sales Org in KNVV.

Once the joins are validated, it is a best practice to click on the

check link condition option, or hit F8. Next, click on the green
back button which will take you to the following page.
We normally suggest to use the data fields section to add fields to
the selection screen and output. For this example, we want to use
Billing Document, Billing Item, Sales Org, Billing Date, Sold To
Party, and Customer Group.

We can move the fields around in the order we like by selecting

the field and using the up and down arrow keys, as shown in the
figure below.
To sort, for example, by Billing Date, follow these instructions:
find the sort field tab, select Billing Date, and move it to the
“Select Sort Order” side by using the left arrow key.

To change a label, toggle to layout mode, or hit F5. Select the

field on the right-hand side of your screen and relabel it. Note that
this would only change the label in the output but not on the
selection screen.

Then hit save.

You will see a few warning messages that can be validated, and
then hit the green checkmark. Next, click on the execute button,
or hit F8. The program will compile for a few seconds as this is the
first time it’s run, and we’ll see the screen as shown below.

Doesn’t this report look exactly like one your ABAP developer
would have created? You are on the way to becoming a techno-
functional consultant!

Lastly, add your selection criteria and execute the report.

SQ02/SQ01

I intentionally write T-code SQ02 before SQ01 and you will see
why in this section. One of the key differences between SQVI and
SQ02/SQ01 is that SQ02/SQ01 queries are transportable. In the
SQ02 transaction code, we set up the InfoSet and perform the
role/usergroup assignment. With SQ01, we set up the field
selection for input and output, do variant determination, and add
titles and notes.

Let’s look at this use case: the procurement team requested a

complete lifecycle dashboard for PR to PO. The dashboard should
contain dates, approvals, and GRs. And it can be in the form of a
report.

You can develop this dashboard through T-codes SQ02/SQ01. We

always start with SQ02 and then move onto SQ01. That is why I
refer to this query as SQ02/SQ01 and not SQ01/SQ02.

To get started, let’s go to transaction code SQ02 and create

InfoSet “ZPRPODASH.”
Click on the join option and add tables EKKO, LFA1, T001, EKPO,
EKKN & EBAN. Modify the joins as shown in the figure below.

Next, we’ll create field groups and add data fields per the
requirement.
For our use case, we are not doing an alias table or extras. So, we
can just hit the generate option, or press Shift + F6.

You’ll once again see a log of warning messages. Validate them

and hit the green checkmark.

The system will prompt you to create a workbench request or

transport, as shown below.

Create the transport and save.

Next, select your InfoSet and click on the role/user group
assignment button.

For this use case, we will assign ZPRPODASH to user group ZO2C.

Hit save and exit the transaction.

Next, go to transaction code SQ01, click on the other user group

button (or hit Shift + F7), and find your user group (in our case
ZO2C).

Type in the query name; we would suggest to use the same name
as the InfoSet. We’ll enter ZPRPODASH and click on the create
button.
Match query PRPODASH to the InfoSet PRPODASH (created earlier
with SQ02) and click the green checkmark.

Next, go into change mode for the query and modify any things
that need updating per your unique requirement. In this case, we
will modify title and field names, and we will sort the output
based on purchasing documents. We will also choose the fields
we want to show in the selection and output.

After entering change mode for our query, the first page gives us
the flexibility to modify the title:
Next, click on the basic list option and modify the field labels as
needed. Add purchasing document to the sort field bucket as
shown below.
In the data fields section, choose fields for selection and list
(output).

Once done, hit save and go back to the home page for SQ01.

On the home page, select the query and click on execute, or hit
F8.
Enter the selection and click execute.

It works like a charm!

Z Transaction Codes

For the report we just created, you shouldn’t give end users
access to T-codes SQ02 and SQ01. It is not a good user
experience to have your business folks play around with these
technical transactions. So, for a complete end-user experience,
you should create a report in SQ02/SQ01 and then associate a Z
transaction code (custom code) with it. SAP allows you to create
these Z transaction codes, which can be used like any other
standard transaction code.
To do this, first go to T-code SQ01 and follow this path: Query >
More Functions > Generate Program.

Copy the program name. Next, go to T-code SE93. Enter a unique

transaction code starting with Z, enter a name in the short text
field, select the radio button for “program and selection screen
(report transaction).”
Enter the program name you copied from SQ01 and fill out the
classification fields as shown in this figure.

Hit save. The system will prompt you to enter the package name
which you can get from your ABAP or Basis person. Save the
changes to a transport and ta da! Your z transaction code is ready
—in this case, we named it ZPRPO.

Type ZPRPO into your command prompt, hit enter, and you will be
directed to your report POPODASH.
Not too hard, am I right?

Conclusion

When working as an SAP consultant, you’ll need to work with

queries. This post talked about the transaction codes SQVI, SQ01,
and SQ02, which can be used to create such queries
Recommendation

How to change the order of the fields in the list output of a SAP query ?

Goto SQ01---> Give the query name ---> Click on Change

Click on Basic List (if the query is a Basic List type )

If the List Layout is displayed in the above graphical format then it

is diffiicult to rearrange the order by drag and drop option.
In such a case,press back button and come to previous screen.
Click on Settings-->Settings in the menu bar as below
and uncheck the Graphical Query Painter checkbox.
Click on Enter

Now you can see the List Layout in the below format and you can
change the order of the fields that appear in the output by
changing the Sequence numbers accordingly.
Local Fields in SAP Queries
When creating SAP query reports using Tcode SQ01, it’s sometimes
necessary to create what is referred to as ‘Local Fields’. These are
fields you create that aren’t drawn from the transparent tables when
maintaining the infoset. So these fields are ‘local’ to the query you’re
building.

A common reason for creating local fields is when you need to

perform a calculation on a field. One example is to get the ‘Per Unit’
price of an item that is normally purchased as a quantity greater than
1, such as a pack of batteries. In SAP queries you can enter a
formula for calculating the value, and you can also enter the
conditions under which this formula would apply.

T-code SQ01 – Maintain SAP Query

From the initial query start screen, click ‘Change’ or ‘Create’ as

needed after entering the query name according to your company’s
naming conventions.

Note that you can’t create a local field from the Edit menu until you
have first gone to the ‘Field Selection’ option under the ‘Go To’
menu.
To enable the ‘Local Field’ functions, first access the Field Selection
screen under the ‘Goto’ menu.

The fields contained in the tables selected for the query are
displayed.
Then go back to the ‘Edit’ menu to switch on the field short names.
Assign a name to any of the existing fields you may want to either
reference in your new Local field, or for fields you may want to use in
calculating a formula.

Next, go back to the ‘Edit’ menu, and the Local field functions will be
activated:
Enter data on the new Local field as needed, including any formulas
required:

Once added and saved, the new local field will be displayed on the
Layout Design screen of the SAP Query and can be flagged for
selection, display, or both on the report.
Using ABAP Coding In SAP Standard Query

It is hard to find an easy explanation about ABAP coding in standard queries. In some cases
you can’t easily attach additional information to a field in a Query or you need to call and
ABAP function module to do an specific calculation, then adding coding to a local field may
be a suitable solution. To demonstrate this we are going to make a standard query with one
table using ABAP Coding on it, instead of creating an infoset with three tables (inner join) as
usual.

In order to illustrate this I’m going to create a query using MARD table (Materials per Plant)
adding names for Plant and Storage Location with ABAP coding. MARD table includes
fields WERKS (Plant) and LGORT (Storage Location) and their names are stored on tables
T001W and T001L respectively. A previous knowledge of standard SAP Query and basic
ABAP programming is needed for plenty understanding of this guide .

Infoset Creation
First we launch SQ02 in SAP’s command line to load Infoset Initial Screen:
Then select:

Fill Infoset Name and Direct read of table:

After filling data on screen aboveit is necessary save infoset:

Here second option is marked and click on the button:

Here we proceed to create a custom field in the query clicking on:

For field creation click on button:

We are going to create 2 fields PLANTN (plant name) and STORN (storage location name):
Click on button:
On this screen it is necessary to fill Long text and Header. Field format has to be declared
too. There are two ways declaring field format (using a direct field type or using a text):

As a default first field declared get the first number of Sequence Code. Finally click on
button to save field:

Then we proceed to create the next field STORN using the same process described above
(assigning sequence number 2):
After click on

we have:
In my practice I have found that if you want to include additional coding for each field at
every select iteration code should be written in the last field declared. In this case STORN. It
is done clicking on field STONR and then click on

Here we have an ABAP editor where our coding can be written to find Plant and Storage
Location names:
After coding we need to check syntax code clicking on:

And save:

Then we have to return to main infoset screen:

In order to make our fields and their codes work it is necessary to include Additional Fields
to Storage Location Data for Material Field Group. To do this expand “Additional fields” and
“Storage Location Data for Material”:

Then drag fields PLANTN and STORN to group 01 “Storage Location Data”:

Then we have to generate our infoset clicking on

To save we click on:

Click on:

Finally we assign infoset to User Group.’[u=

After creation this must be assigned to user group:

Next step is creation of query in SQ01 using ZTEST001 infoset.

Query Creation
Executing SQ01 we can create our query named “ZTEST”:

Now click on
and then assign it to infoset created above:

Click on

In the next screen we add a title for query:

Then click to next screen
Now check filed group and follow next screen clicking

We have to check fields to be used in our query, then go to next screen

Then marking “Material Number ” as unique selection criteria we call Basic List design

In order to test it we click on

Then we use a material to test query:

Fields “Plant” and “SLoc” are key fields from MARD, then “Pl” and “Storage Loc Name”
are additional fields.

Author: Roberto Cañas

Roberto is a responsible IT professional with 15+ years of experience in functional support, configuration
and programming in SAP ERP. Now seeking to contribute his skills and expertise in new SAP projects.
Proven Skills in the following areas: SAP FICO Configuration and Functional Support SAP MM
Configuration and Functional Support SAP SD Configuration and Functional Support SAP ABAP
programming of reports, module pools, enhancements, user exits, etc. SAP Administration of Roles and
Authorization Objects.

Module(s): ABAP, Basis, Controlling, Enterprise Controlling, Financial Accounting, Human Resources,
Logistics Information System, Materials Management, Sales and Distribution

Tagged: ABAP, Standard Query, Coding

Newest First
Newest First

I try to do SUM with VBAP-KLMEND but dont work...

My code :

in table MARA

I have add field with this code

TABLES : VBAP.

Select SUM( KLMENG ) FROM VBAP INTO CDECLIENT

WHERE MATNR = VBAP-MATNR.

SAP Query and Abap

Add your own columns to a Sap query ? Involve Abap coding in your reporting setup ? The infoset on
Sap Query can be enriched with logic.
The SAP Query tool is very flexible and powerful, especially where HR reporting is involved. This
article explains how a field can be added to your query results, as column in the reports. It assumes
you are already quite familiar with SAP query and Infosets.
The first thing to do is add the new column field to the Infoset that will be used for your query (or
queries). Through transaction SQ02, change the Infoset you want to add the column to. Note that in
most systems, the Infoset can not be changed when it is in the Global area (Cross-client). Make your
Infoset available in the Standard area first.

Once you have entered SQ02 in change mode, simply add your field in the “Additional fields” section
by clicking on the right mouse button “Create”. Supply a name and set select “Additional field” for this
(single column) example.
Then press enter, which will present another popup
Details are supplied, making this a 20-character field called “Characteristic”. The next step is to assign
the new field to a group, which will make it available in Query output.
Click on the “Field groups” button and drag/drop the new field to the required group:

At this point, a new column is added and made available to the Infoset and Query, however this is still
without selecting it’s content. Click on the right-mouse, context menu and select “Field code”.

Now fill in the coding supplied, which is explained later on:

The coding supplied is custom-made for a certain query field use, which can be re-used for other
purposes as well.

* This is where the CHARACTERISTIC value is retrieved from

* the available information on P0001-ORGEH

data: lw_hrp1010 type hrp1010.

field-symbols: type any.

assign ('SYHR_SPLITS_WA-ENDDA') to casting type d.

select single * from hrp1010 into lw_hrp1010

where plvar = '01' and "Active

otype = 'O' and "Organization

objid = p0001-orgeh and "Organization

subty = '0001' and "Subtype of KENMERK

istat = '1' and "Active

begda <= and

endda > and

varyf = space and

 seqnr = 0.

if sy-subrc = 0.

characteristicfield = lw_hrp1010-hilfm.

else.

clear characteristicfield.

endif.

What effectively happens here is a selection of characteristics from the HRP1010 table, which is set
up for Organizations. The Organization number from infotype 0001 is used to fetch information from
the HRP1010 table, for which the correct selection date is used. The date is derived from the bottom
end and high end of the selection dates on the selection screen, which could be a single date, but it
couls just a well be a date range. The customer has chosen that the highest date in the range is to be
used for this selection.
The Field-symbols setup is made available to fool the SQ02 tool into thinking it can compile the
coding. The easiest approach to determine what is available and what can be done is by putting a
break-point in the coding block and having a look around. The query report itself is a report like many
others, which means it can be viewed from the report selection screen. Do note that this setup was
aimed at adding a single field with selection information that was already available. There are many
more abap coding block options on the Infoset to lean on !

Trouble shooting
SQVI Table join EKKO-EKPO not showing all line items

Hello Experts,

I want to create a report for

Company Code

PO Document Type

Valid from Date

Valid To Date

PO #

Line #

Vendor #

Material #

Plant#

But the output is not showing all line items, Please help!
Here is what I did

Step 1

Step 2 Joined EKKO and EKPO

Step 3
Execute
Result

As you can see below in the contact there are 2 lines items but SQVI output is only
showing 1 line item.
These Table has 2 link . Please remove/ Delete link for Item Number in Purchasing
Document . Leave only one link which is Purchasing docuemnt number . Right click
on Link " Item number for Purchasiing document and click on delete .

then generate you query again .I am sure that will solve your problem .

[Link]-
[Link]
Hi

Please follow the below attached I hope solve this issue

1st Join the table EKKO & EKET than back to data fields & tick the Item Number of
Purchasing Document than save & Execute,,,,, than input the Purchase order
No than execute .