SQVI and related system/security issues

[Former Member]

Can anyone please definitlively confirm if there are any issues with allowing end users to write and run queries using joins via transaction SQVI in Production? It appears to be a very benign transaction, compared to SQ01 or SQ02, in that you select the table or tables to be joined, select your fields to appear in the output and select your criteria fields. It appears that SAP does the joins automatically based on common fields from the tables. What system degradation is possible using this transaction? If there was an inordinate amount of records being processed I would presume that a timeout error would occur and the report would abend. There doesn't seem to be a whole lot that can break with this tcode. Can anyone elaborate on their experience with this transaction?

Thanks

Mark

[Former Member]

SQVI is used to join the tables and fetch the required information, if any user in production is given rights to view tables then there is no harm in giving rights to SQVI as it will allow user the flexibility to join those table and see the data according to his need.

That means we can say if user can be given access to view tables then SQVI can also be given and vice versa.

[od_manikandan]

Hai Mark,

SQVI query builder can be given to users.

And you can inform the users:

SQVI will link only transparent tables

user should know thw table names

To know table names user can click F1 in the field and they will come to know what is the table and Field.

-

---

If you have a core Team SAP modulewise

the core team memner can get the requirements from user and

He can create the query and execute.

Once the data displayed correctly in output.

Core team member can take the program name from Environment status.

Ask Abaper to create a T.CODE for the query program

T CODE: SE93

Transaction code: ZXXXX ( new t code )

assign the program

And give the T code authorization to the required users..

Regards,

Mani