Skip to main content

SQVI Query

At times, businesses will ask for a report based on the table extract of single or multiple tables. As this is a direct table extract, we need not take the help of a developer to extract the data from the tables.

SAP has given a provision to generate this kind of report by functional consultants rather than taking the help of the technical team.

This report extracts by the functional team will be done with the help of SQVI and SQ01 queries.

SQVI query created by a user cannot be accessed by another user ( User Dependent)

SQ01 query created by a user can be accessed by other users based on the user group ( User Independent)

SQVI queries in general will be generated by the business and consultants will mostly assist business users.

But at times, consultants use the SQVI query to extract specific data in a quick way as per business needs and then subsequently extract them to excel and provide the required information to business users.

If business insists on the query access for the SQVI, then we can convert a SQVI query to SQ01 query and through SQ01 transaction code and assign the user name to the user group




Comments

Popular posts from this blog

[SAP EWM] Batch job to reprocess the failed queues in SMQ1 and SMQ2

Reports RSQOWKEX/RSQIWKEX can be scheduled as a periodic background job to reset the status of LUWs registered to outbound(SMQ1)/inbound(SMQ2) queues. RSQOWKEX for outbound queues (SMQS/SMQ1). RSQIWKEX for inbound queues (SMQR/SMQ2). The below parameters are to be maintained : Queue Name as '*' Select 'No Running Queues' Do not select 'No Retry queus' Queues running longer than  < Time in Mins > ideally 20 mins No queues older than < Data > Note that this job will change the status of the failed queue to 'READY' status so that scheduler will process it. But for any queues struck in 'READY' status, th ese need to be processed manually.

[SAP SD] Mass deletion of deliveries in SAP

If there is the requirement for collective deletion of Outbound deliveries in standard, the following can be performed. Transaction VL10* with corresponding user role settings can meet this requirement. Go to VL10*, only flag indicator 'With Deliveries' in 'Data Selection' column in User Role After flagging above indicator, go into the following screen. Then flag indicator of 'Add to delivery', and fill the delivery numbers or other parameters into corresponding fields and then execute In the display screen, select the lines and click 'Delete' button

How to change records in SAP using debug mode

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th...