SAP SQVI – Part 2 – Creating a Quick Report using Quick Viewer – Cool Tips



This Blog is a continuation of my last Blog “Part One – Creating a Quick Report using Quick Viewer (SQVI)”. That Blog outlined the steps required to create a quick and simple query/report using transaction SQVI.

This Blog will cover:

  • Using SQVI Layout Mode

There are two “modes” that can be used when creating a Quick Viewer Query, Basic & Layout. As mentioned in Part One Blog I like to use Basic Mode to create the query and then switch to layout mode to get a clear picture of the report’s / query’s layout.  The first part of this blog covers the Layout Mode.

  • Copying existing Quick Viewer (SQVI) Query.

I highly recommend copying an existing Query when adding new tables (joins) to an existing SQVI Query. Joins are not forgiving.   If you join a new table that negatively impacts your query, which can happen, you may not be able to un-join or delete the new table.   This means you have to re-build the entire Query from scratch.  Never fun.

  • Adding new tables to existing Quick Viewer (SQVI) Query.

In the “Part One” Quick Viewer Blog we created a simple purchase order query joining tables EKKO (Header) and EKPO (Line Item).   In this Blog we will add table T024 (Purchase Group text) and EKET (Scheduling Agreement Schedule Lines).

  • Adding a Transaction Code to Quick Viewer (SQVI) Query.

This is quick, simple and cool.   But depending on security and environment setting may not be possible in some systems especially Production Environment.   And this is not transportable because the SQVI program name is uniquely generated in each system.

Other SQVI related Blogs to check out:

As always my goal is that any knowledgeable SAP person can successfully use the following information, however this is not an SAP training manual and does require a good understanding of SAP and specifically a strong understanding of how the data you are wanting to report on fits together.

Recommended Saving your query every once in a while.   I usually hit save after every step in process.   Nothing worse than spending quite a bit of time on a query to have a “glitch” kick you out and nothing is saved.

Continue reading