how to use TCode SQVI

[Former Member]

Kindly help me in using t code SQVI .....

i m using datasource table join and ......when i insert 2 tables than it automatically joins two fields.how it works actually.

i m using VBAK and VBRK table ...and after giving input in the Sales org and division field it gives me message No data selected......

plz help me....

Cheers

shalsa007...........

[Former Member · Accepted solution]

HI Sailesh,

SQVI Table Quickviewer – Used to created quick client dependent reports

Probably the easiest and most flexible way to do this is thru one of the abap query transactions.

Transaction SQVI can do this and it has a very good help function that explains how it works... the drawback is that it is only for one user.

You can play around with it and see if it meets your needs...

The query results will come back in an ALV Grid or Excel... you can select what fields are returned, and have a selection screen to enter the search criteria.

To allow any user to run a query, then you can create an Infoset with transaction SQ02 (you define what fields the user will get in their results, and what fields will appear on the selection screen), then create a multi user query using transaction SQ01 and the infoset you creataed in SQ02. One of the basis people can then create a transaction from your sq01 query, and that transction can then be moved into production.

SQVI and SQ02/SQ01 are far more powerful than SE16 as they allow you to do table joins. SQ02 also allows you to create computed fields.

Check this link

http://supplychain.ittoolbox.com/groups/groups.asp?v=sap-r3-log-mm&i=783523

<b>**Reward if this helps**</b>

Regards

AK

[Former Member]

Hi shailesh lodha ,

Let me give you generic explanation,

When you what to join two tables, there shold be common fields available.

Say for eg you want to join VBAK and VBAP, I have common filed Sales document VBELN, When I do not have the common fields in the table you want to join you can make use of Document flow table VBFA as a intermitant table.

Regards,

Sateesh

[Former Member]

hi shailesh,

SQVI is used to create quick querry (if u do nt have acess to sq02 and sq01). whenver you try joining two tables thru sqvi, the system proposes join conditions (which can be changed). the join (both the proposed by the system and dne by the user) is based on the simple database concepts of keys and joins. the system will propose join between two tables if the said field has the same value in both the tables. in your case the system will not throw ne data as the table you are trying to link are diiff. VBAK- is for sales doc header into and vbrk for billing doc header info.

to get the requisite dat insert anither table VBFA (doc flow) and esablish the join as per your need.

Saurabh

[Former Member]

Hi,

SQV1 is used to convert a QuickView into a query.

QuickViewer:

The QuickViewer allows you to define reports without having to program yourself. The QuickViewer is especially useful for new users and occasional use.

QuickViewer is a tool for generating reports. SAP Query offers the user a whole range of options for defining reports. SAP Query also supports different kinds of reports such as basic lists, statistics, and ranked lists. QuickViewer, on the other hand, is a tool that allows even relatively inexperienced users to create basic lists.

QuickView definitions are user-dependent. You can transfer a QuickView into SAP Query in order to make reports, for example, accessible to additional users, or to use the other functions available in SAP Query.

The following is a comparison of QuickViews and queries:

QuickViews possess the same functional attributes as queries. However, only basic lists may be defined with QuickViews.

In contrast to queries, no user group assignment is necessary with QuickViews. Each user has his/her own personal list of QuickViews. QuickViews cannot be exchanged between users. QuickViews may, however, be converted to queries and then be made available to other users in a specific user group.

InfoSets are not required for QuickView definition. Whenever you define a QuickView, you can specify its data source explicitly. Tables, database views, table joins, logical databases, and even InfoSets, can all serve as data sources for a QuickView. You can only use additional tables and additional fields if you use an InfoSet as a data source.

The QuickViewer uses various controls. Certain hardware and software requirements must also be fulfilled before you can use the QuickViewer.

To define a QuickView, you select certain fields according to your data source that determine the structure of your report. The report can be executed in basis mode with standard layout or may be edited using drag and drop and the other toolbox functions available in WYSIWYG mode.

Reports created using the QuickViewer may also be passed to external programs (Excel, for example).

Call the QuickViewer using System -> Services -> QuickViewer (or transaction SQVI).

Enter the name of the QuickView. QuickView names can contain a maximum of 14 characters.

Choose Create.

Enter a title for the QuickView and remarks, if you think they are relevant.

If you do not want to base your list on a table, use the possible entries pushbutton in the Data source field to select another data source. You can choose logical databases or InfoSets. In addition, you may also create table joins. For further information, see Selecting a Data Source.

Choose Basis mode if you want to create the list directly with no list design. Choose Layout mode if you want to define the layout of your list yourself.

Reward points if it helpful

Regards

Govind.

[Former Member]

Logic:

VBAK-VBELN = VBFA-VBELV (For Linking Delivery)

LIKP-VBELN = VBFA-VBELV (For Linking Billing - VBRK)

Incase of order related scenario:

VBAK-VBELN = VBFA-VBELV (For Linking Billing)

Regards,

Rajesh Banka

Reward points if helpful.