SAP Quickviewer

Dear All,
I have created a SAP query in quick viewer. I need to know whether any user other than me can use this query ?
I know that this can be achieved by SQ01, SQ02 and SQ03 by creating user group and assigning users to that group.
But i want to know whether this can be achieved by SQVI.

It cannot be done from SQVI transaction.
But any user with authority can execute your quickview without the need of  creating user group and assigning users to that group.
Preparation:
Execute SQ02
Choose from menu Settings > Settings
Activate u201CDisplay system objectsu201D, and then press Enter to adopt the changes.
Make sure that your work area is set to u201CStandard areau201D in menu Environment > Query areas:
Operation:
Execute transaction SQ01
Klick Change Usergroup
Each User has its own user group for Quickviews.
The name starts with SYSTQV followed by a sequential number.
Choose a desired User group.
All Quickviews of this usergroup are listed and can be executed from here.

Similar Messages

  • Report from SAP Quickviewer code

    Hi,
    I have been given a code generated by SAP Quickviewer (transaction SQVI). The client expects me to design an ABAP Report using this code as a guideline. Is this practically possible. I don't even have access to the name of the quickview. No tech spec too.
    Some lines of the code: Just to give you guys the feel of it...
    REPORT AQL3SYSTQV000116ORDERS_CPR====
       LINE-SIZE 253 NO STANDARD PAGE HEADING LINE-COUNT 000(001).
    INCLUDE <SYMBOL>.
    INCLUDE <ICON>.
    SELECTION-SCREEN: BEGIN OF BLOCK PROG
                               WITH FRAME TITLE TEXT-F58.
    %FA00000 /BAY0/AXCMR_AUT2-SUBSTITUTE
    TABLES /BAY0/AXCMR_AUT2.
    TABLES VBAP.
    TABLES VBPA.
    TABLES /BAY0/AXCMR_CPR.
    *TABLES KNA1.
    DATA AVBEGKNA1 LIKE KNA1.
    TABLES KNA1.
    TABLES VBAK.
    DATA %COUNT-VBAK(4) TYPE X.
    DATA %LINR-VBAK(2).
    SELECT VBAKANGDT VBAKAUART VBAKBNDDT VBAKERDAT VBAK~ERNAM
           VBAKERZET VBAKKUNNR VBAKVBELN VBAKVKORG VBAP~ABGRU
           VBAPARKTX VBAPMATNR VBAPPOSNR VBAPPRODH VBAP~VBELN
           /BAY0/AXCMR_CPRKUNAG /BAY0/AXCMR_CPRKUNWE
           /BAY0/AXCMR_CPRMATNR /BAY0/AXCMR_CPRPRICE
           /BAY0/AXCMR_CPRVKORG VBPAKUNNR VBPAPARVW VBPAVBELN
           AVBEGKNA1KUNNR AVBEGKNA1LAND1 AVBEGKNA1NAME1 AVBEGKNA1ORT01
           /BAY0/AXCMR_AUT2ML1 /BAY0/AXCMR_AUT2ML2 /BAY0/AXCMR_AUT2~ML3
           /BAY0/AXCMR_AUT2ML4 /BAY0/AXCMR_AUT2OBJID
           /BAY0/AXCMR_AUT2PRICE /BAY0/AXCMR_AUT2SUBSTITUTE
           /BAY0/AXCMR_AUT2VKORG KNA1KUNNR KNA1LAND1 KNA1NAME1
           KNA1~ORT01
    INTO (VBAK-ANGDT , VBAK-AUART , VBAK-BNDDT , VBAK-ERDAT , VBAK-ERNAM
         , VBAK-ERZET , VBAK-KUNNR , VBAK-VBELN , VBAK-VKORG , VBAP-ABGRU
         , VBAP-ARKTX , VBAP-MATNR , VBAP-POSNR , VBAP-PRODH , VBAP-VBELN
         , /BAY0/AXCMR_CPR-KUNAG , /BAY0/AXCMR_CPR-KUNWE
         , /BAY0/AXCMR_CPR-MATNR , /BAY0/AXCMR_CPR-PRICE
         , /BAY0/AXCMR_CPR-VKORG , VBPA-KUNNR , VBPA-PARVW , VBPA-VBELN
         , AVBEGKNA1-KUNNR , AVBEGKNA1-LAND1 , AVBEGKNA1-NAME1
         , AVBEGKNA1-ORT01 , /BAY0/AXCMR_AUT2-ML1 , /BAY0/AXCMR_AUT2-ML2
         , /BAY0/AXCMR_AUT2-ML3 , /BAY0/AXCMR_AUT2-ML4
         , /BAY0/AXCMR_AUT2-OBJID , /BAY0/AXCMR_AUT2-PRICE
         , /BAY0/AXCMR_AUT2-SUBSTITUTE , /BAY0/AXCMR_AUT2-VKORG
         , KNA1-KUNNR , KNA1-LAND1 , KNA1-NAME1 , KNA1-ORT01 )
    FROM ( VBAK
           INNER JOIN VBAP
           ON VBAPVBELN = VBAKVBELN
           INNER JOIN /BAY0/AXCMR_CPR
           ON /BAY0/AXCMR_CPRKUNAG = VBAKKUNNR
           AND /BAY0/AXCMR_CPRVKORG = VBAKVKORG
           AND /BAY0/AXCMR_CPRMATNR = VBAPMATNR
           INNER JOIN VBPA
           ON VBPAKUNNR = /BAY0/AXCMR_CPRKUNWE
           AND VBPAVBELN = VBAPVBELN
           INNER JOIN KNA1  AS AVBEGKNA1
           ON AVBEGKNA1KUNNR = /BAY0/AXCMR_CPRKUNWE
           INNER JOIN /BAY0/AXCMR_AUT2
           ON /BAY0/AXCMR_AUT2PRICE = /BAY0/AXCMR_CPRPRICE
           AND /BAY0/AXCMR_AUT2VKORG = /BAY0/AXCMR_CPRVKORG
           INNER JOIN KNA1
           ON KNA1KUNNR = /BAY0/AXCMR_CPRKUNAG )
           WHERE VBAK~ANGDT IN SP$00003
             AND VBAK~AUART IN SP$00001
             AND VBAK~BNDDT IN SP$00002
             AND VBAK~ERDAT IN SP$00004
             AND VBAK~ERNAM IN SP$00005
             AND VBAP~ABGRU IN SP$00010
             AND VBAP~MATNR IN SP$00006
             AND VBAP~POSNR IN SP$00007
             AND VBAP~PRODH IN SP$00009
             AND VBAP~VBELN IN SP$00008
             AND /BAY0/AXCMR_CPR~KUNAG IN SP$00016
             AND /BAY0/AXCMR_CPR~KUNWE IN SP$00015
             AND /BAY0/AXCMR_CPR~MATNR IN SP$00014
             AND /BAY0/AXCMR_CPR~PRICE IN SP$00013
             AND VBPA~KUNNR IN SP$00011
             AND VBPA~PARVW IN SP$00012
             AND /BAY0/AXCMR_AUT2~ML1 IN SP$00022
             AND /BAY0/AXCMR_AUT2~ML2 IN SP$00021
             AND /BAY0/AXCMR_AUT2~ML3 IN SP$00020
             AND /BAY0/AXCMR_AUT2~ML4 IN SP$00019
             AND /BAY0/AXCMR_AUT2~OBJID IN SP$00018
             AND /BAY0/AXCMR_AUT2~SUBSTITUTE IN SP$00017.
      %DBACC = %DBACC - 1.
    Please help with this.
    thanks,
    Vishal.

    My advice would be to make sure the client tells you what they want the new ABAP Report to do that is <u>different</u> from the Quickviewer Report.  If the client does not have a formal technical spec process, then you at least need to be told verbally or via e-mail what to change.  Without that information you cannot proceed with any meaningful development.
    Assuming that you can get that information, all you need to do is to create a copy of the Quickviewer program (via SE38) since the Quickviewer program is just a regular ABAP program.  Then you must get a feel for what the code is currently doing (understand the logic) so that you can proceed with making the changes required for the new version. 
    Another approach might be to simply get an understanding of the Quickviewer code and start your own ABAP Report from scratch (using your own preferred style of coding).
    Have fun!
    Regards,
    James Gaddis

  • SAP Quickview: converting to Query

    Hi,
    I've created a quickview, and this quickview can be used for other users, and I want to convert this quickview to a quey.
    If I go to the query screen (SQ01), there's the 'convert quickview' functionality (Menu: Query --> convert quickview). But this function is grayed out in my system, as well as the IDES sytem. I think I'm missing a step which hinders me in creating the query.
    Can anyone help, will award points!
    Kind regards,
    Mark

    Mark,
    It is simple you need to change the "Query area" to "Standard area - Client Specific". Currently you are checking in "Global area - Cross Client".
    In SQ01 transaction, you need to use menu path Environment--->Query Areas. Select "Standard Area - Client Specific". Now try the menu: Menu: Query --> convert quickview.
    Hope this resolves your problem...Reward your points,
    Regards,
    Prasobh

  • Adding a Structure in SAP QuickView

    Hi,
    I have to make a report in QuickView using the tables VBRK, VBPA, VBFA. Also, I need information from Structure KONV (Condition records), but I cannot join it as a table. How should I proceed?
    Thanks for your help!
    Cristiana

    Hi,
    actually, with SQVI, you can choose the logical database : VFV.
    Another solution to use directly KONV, you can add an ABAP code by using SQ02 to create your own infoset.
    Regards,
    Lionel

  • SAP Quickviewer query for pricing records - V12L and KONH / KONP

    Has anyone used the logical database 'V12L' for pricing queries? There seems to be an issue with this logical database with some vague warning messages.. When I tried to create a simple table join query with KONH and KONP there are again some vague errors. I need to see the following fields in the query output.
    KONH-KNUMH, KONH-KOTABNR, KONH-KSCHL, KONP-KBETR, KONP-KONWA, KONP-KPEIN, KONP-KMEIN.
    Are there any other simple and robust way to query KONH and KONP simultaneously? Thanks in advance.

    Hi Dhanaraj,
    I tried linking KONH and KONP and it just gave me just warning errors that won't affect your query. Disregard those errors since your not using it anyway and proceed as usual.
    Try not to query directly to these tables as much as possible for obvious reason, IT"S HUGE....
    I suggest to start with AXXX pricing tables and then link KONP with it. It's faster and you can directly identify the key combinations used.
    Enjoy!
    Arnel

  • Convert SAP QUICK VIEWER to SAP QUERY

    Could any one pls tell me to convert the SAP Quickviewer to SAP Query. Also tell me how to make the other users to view this SAP Query or Report using the Custom Area Menu.

    Dear Neelu,
    go to QuickViewer (SQVI), create and save an object, go to Menu "Environment" in SQ01 and switch to Standard Area(client-specific). Next, u go to Menu QuickView and push "Convert QuickView..". Finish!
    EDIT: Regarding your question about queryview for other users:
    [U must create a user group|User Groups for Queries; in SQ03 or choose a existing one and then u can assign it to a query. If u want to see different user groups in SQ01 go to 'Edit' -> 'Change usergroup'.
    Hope this helps!
    Regards,
    Zaya
    Edited by: Tuncay Zaya on Aug 5, 2009 3:31 PM

  • Quickviewer

    Hi,
    I want to learn, how to use the quickviwer for daily queries.
    Please help.
    Thanks / Bhavesh

    Please see the following documentation SAP Quickviewer.
    http://help.sap.com/saphelp_46c/helpdata/en/b7/26dde8b1f311d295f40000e82de14a/frameset.htm
    When creating your quick query, select table join from the datasouce listbox. Click green check. On the next screen click "insert table". Enter the 1st table name, I'm using MARA and hit enter. Click insert table again, this time use MARC. hit enter. Notice that it made the connection for you. it does this when it finds fields with the same field name. You can change it if you want. This is how you join tables in the SQVI.
    http://help.sap.com/saphelp_46c/helpdata/en/50/a71ec8f65911d296390000e82de14a/frameset.htm

  • The fixed value date is empty and not displayed in the VA05 report

    Hi SD Gurus,
    With in the Sales Order in the line item level in the billing tab we have the fixed value date (VBKD - VALDT) were entered. 
    But when we try to execute the report VA05 were the fixed value date column shows empty (i.e without the date it shows the blank).  Can you any one help me with regard.
    We would like to fix this problem.
    Thanks in advance for providing solution to this query.
    Thanks and Regards,
    SAP-SD group

    Hi janarthanam,
    Ok.
    Goto t-code SQVI,SAP Quickviewer.
    Give a name to your query and enter description ,etc.
    Next enter the table from which you want to fetch data,ie,VBKD .
    Select "Layout mode" for displaying data on the SAP screen or "Basis mode " if you want to extract the data to a word doc,excelsheet or a flat file.
    Next you can select the fields you want to display into your report,their position and ascending/descending order,Here make sure u select
    the field u need to display ie. the fixed value date ( VALDT) .
    also select the fields u wish to have in the selection criteria.
    Enter these required information and u would get a report on the SAP screen or in your desired format.
    Hope it will suffice you.
    For any queries ,your are welcomed.
    Thanks,
    Umesh.

  • ABAP Query: FI Tables - BSEG and BKPF

    Dear All,
    I have tried to use SAPQuery - SQ01 to join 2 SAP tables (BSEG and BKPF) by creating an Infoset (SQ01 >> Environment >> Infosets >> Create)
    However, there is always an error message for the table join when I generate the infoset. Tables BSEG and BKPF are joined together by conditions BSEG-BELNR & BKPF-BELNR; BKPF-BURKS & BKPF-BURKS; BSEG-GJAHR and BKPF-GJHAR.
    The error message prompted is, "You cannot use comparisons with column references in pool and cluster". Is the message trying to say that BELNR, NURKS and GJAHR are column references in pool and cluster, thats why we can't join the tables?
    The purpose of the infoset is to extract accounting documents. I will need to extract accounting doc data from DEV, QA and Prodcution Server.  If I use SAP QuickViewer, everytime I go to a differenct server I will need to create the QuickViewer in the system before I can use it. But if i use SAP Query, i will need to create once and transport the SAP Query to another server.
    Kindly advise if there is a way I can extract accountng document by using SAP Query?
    Million Thanks in Advance.

    Hi Mark,
    I appreciate your response.
    Im tyring to extract information for open GL items. Thus the relevant tables would be BSIS. But I find that  some fields such as Purchase Order Number; Purchase Order Line Item, Asset No.,Asset Sub-No which Im interested in do not exist in BSIS. But these fields can be found in Table BSEG?
    If I have to link BSEG and BKPF, how should i go about doing it?
    Kindly advise.
    Thanks in Advance!

  • Download a value

    Hi,
    When we download a value like 12.300 from SAP into an excel sheet, in the excel sheet the value is downloaded as 12.3. It is wrong and it should be 12300. In SAP '.' is considered as comma and ',' is conidered as decimal point.
    How can we download the same into excel sheet without losing the zeros like 12300 instead of 12.3.
    I cannot change the user profile setting. it is client specific.
    Thanks

    hi abhishek,
    check this notes,
    Many SAP reports have direct download function to EXCEL.
    SAP Query and SAP QuickViewer are excellent tools for Downloading (BvdR AO).
    Transaction SE16N allows you to access any sap table and download result to Excel
    SAP RFC functions can be called directly from Excel / VBA.
    Use transaction BAPI in SAP to find your business object and study the function.
      If you know the SAP table the RFC RFC_READ_TABLE offers a SQL query of the table
      Trouble is .. you can not use joins here. you have to put the join in as a query in the SAP database and use the query in RFC_READ_TABLE
    To upload data from Excel into SAP:
    Some of the Business functions (BAPI's / RFC unctions) offer data upload
    The general tool in SAP for data upload is the Batch input / call transactions
    In the batch input file you specify screen by screen and field by field the input to SAP. SAP has a recorder to create the sample file. Just run trans SHDB and within this trans you run a case of the changes you want to do. On exit of the trans you will have a batch input file that you can download and from excel manipulate the file before you call the RFC function RFC_CALL_TRANSACTION.

  • Modify existing SAP Query / Quickview

    Hello,
    Greetings!
    We have a requirement to modify an existing SAP Query. This query was created much earlier by a user who is no longer present.
    We have the query name, user group, and the program for the query. This query, we assume was created using tcode SQVI.
    However, in tcode SQVI, we cannot see the query as we have not created it.
    I understand that this is because the quick view has not been converted to query.
    I have referred:
    SQVI - Quick view modification
    http://wiki.sdn.sap.com/wiki/display/ABAP/QuickViewer
    In tcode SQ01, we are unable to see the query, as we get an error that the user group does not exist.
    In table AQLTQ, we get an entry for the query and the user group. But the user group does not exist in tcode SQ03 as well.
    In this case, how to we convert the quickview to query? Or is there any other way to edit the exisitng quickview/query?
    Kindly help.
    Best Regards,
    Smruthi

    Hello Suhas,
    Thank you for your reply.
    I checked in both the tables.
    There exists an entry only in AQLQCAT(Local or Client-dependent queries). We now have the infoset as well, along with the user group and the query.
    When I check for the infoset in SQ02, I get an error, "Infoset <infoset name> not created"
    The user group is the same as that found in table AQLTQ.
    Best Regards,
    Smruthi

  • Find exact package for saving the workbech request for std SAP object

    Hello friends I have edited a std SAP prog for printing the import PO(got access key from market place).After editing while creating transport request I am not able to find the package to which it should be saved.now the problem is that How to move that program to our quality server.
    the program is
    /1BCDWB/LSF00000063TOP

    Hi achal,
    are you sure you modified a standard SAP object. /1BCDWB/ prefix is common with all quick view reports - they are local and user-specific. You can convert a quickview to query to report. Using a modification key you may add it to the standard - choose a package as you prefer. But better copy the generated query report to customer name space - because it never was and never will be SAP standard. If it is in customer name space, release changes are no problem at all.
    Regards,
    Clemens

  • How to remove duplicates in SAP Query

    Dear Frns,
    I created a simple SAP query with quickviewer by table join option.
    tables are MAST & STPO.
    Link is only STLNR.
    I am getting a duplicate extra line with same data.
    Can anyone suggest me how it happened.
    Is there anyway to remove these duplicate lines.
    pl suggest

    Hi,
    You can sort the internal table and then delete the duplicate entries.
    sort itab ascending by STLNR.
    delete adjacent duplicates from itab comparing STLNR.
    Reward points for useful answers.

  • SAP Query Report gives Repeated Values

    Hi Gurus,
    I run a fixed asset report in Quickview in SAP Query but the output shows repeated results. Example I created a report in Quickview for all assets captalized in a period. When I run the report, I see all the assets repeated several times in the report. Is there something I am missing?

    If you just need cap date, then use ANLA only in the query and it should work fine. if you are defining a join with any other table check the join.

  • List of Tcodes in SAP(Technical)

    Hi Gurus,
    Send me a list of Tcodes in SAP.
    Thanks in Advance,
    Sakthi

    Hello Shakthi,
    Transactions:
    search_sap_menu - Finds the menu path to a transaction - Can either type in TX code in the search criteria or a description- ie. 1st try SE38 and then ABAP.... the returned result is 'bottom to top'.
    EDI Specific Transactions
    VOE1 Translation between EDI categories and SD item categories
    VOE2 Table EDSC view. Customer link to sales area detail
    VOE3 Table view EDPVW. Add partner types that will be transferred to the IDoc
    VOE4 Table view EDPAR. Link external partner number with our internal number
    WEDI EDI Administrator Menu
    BALE Idoc Administration
    Scheduling agreements
    OVA9 Create entries for each sold-to customer for which you will receive EDI schedule releases. At implementation, the only field that needs to be maintained is "Check PO number," which causes SAP to make sure that the PO number sent on the release matches the PO number on the schedule agreement. This transaction updates table T663A. SAP will not post an EDI schedule release, if this record is missing.
    OVAI Create entries for each Vendor / Partner description combination. (Vendors must match sold-to Acct. at Cust., and Partner descriptions must match ship-to Partner descriptions.) This transaction updates table T661W. SAP uses this table to determine the schedule agreement sold-to partner.
    OVAJ If you would like SAP to post schedule requirements using discrete dates only, instead of weekly and/or monthly buckets, you can indicate the days of the week that you deliver to this customer. SAP will divide the customer's quantity for a week or month evenly into the days of the week specified by the distribution function code. This code must be sent in the DELINS IDoc in field E1EDP16-ETVTF.
    IDoc Transactions
    WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
    WE05 View IDocs
    WE19 EDI test tool. Use to test inbound Function module changes.
    WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing
    WE30 Create IDoc extension type
    WE31 Segment create
    WE57 Assign function module to logical message and IDoc type
    WE60 IDoc type documentation tool
    WE82 Link Release detail to Extension IDoc Type
    BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations
    BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
    BALA ALE Application Distribution
    BALM ALE Master Data Distribution
    Output determination
    856 - ASN
    V/36 Maintain output determination for deliveries (Output determination procedures). V10000 (Header output) has condition type LAVA (usually with requirement 1 NB: Use V/84 – V7ALLE – SHAD for grouped ASNs. I.e. Group deliveries into shipments
    VV21,VV22,VV23 Create output condition records for shipping. LAVA – WE (Partner function) - We must add each new partner with VV21
    VL71 Reissue output for deliveries
    810 - Invoice
    V/54 Maintain access sequence for billing documents
    VV31,VV32,VV33 Create condition records for billing documents. (RD00 – RE Billing party)
    VF31 Reissue output for billing documents
    855 – Order Response
    V/30 Sales document output types (BA00)
    V/48, V/32, V/43 Maintain access sequence for sales documents
    VV11,VV12,VV13 Create condition records for sales documents. (BA00 – SP Sold to party)
    Requirements coding
    V/27 Create code to check requirements for output control. Used to check ZBA0 against BA00 output.
    Sales & Distribution
    Sales order / Quote / Sched Agreement / Contract
    VA02 Sales order change
    VA05 List of sales orders
    VA22 Quotation change
    VA32 Scheduling agreement change
    VA42 Contract change
    Billing
    VF02 Change billing document
    VF11 Cancel Billing document
    VF04 Billing due list
    FBL5N Display Customer invoices by line
    FBL1N Display Vendor invoices by line
    Delivery
    VL02N Change delivery document
    VL04 Delivery due list
    VKM5 List of deliveries
    VL06G List of outbound deliveries for goods issue
    VL06P List of outbound deliveries for picking
    VL09 Cancel goods issue
    VT02N Change shipment
    VT70 Output for shipments
    General
    VKM3, VKM4 List of sales documents
    VKM1 List of blocked SD documents
    VD52 Material Determination
    Workflow
    SWEAD Event queue administration
    SWE2 Event type linkages
    SWE3 Event linkages
    PPOME Organizational Unit Maintenance
    SWE5 Consistency Checks for Event Linkages
    SWUD Workflow Diagnostic Tool
    General
    The following section provides detail on other useful SAP areas.
    Create delivery via transfer orders
    Once the order is saved proceed through the following steps. The process assumes the item has values in the warehouse bin.
    VL04 Delivery due list. Run the delivery due with your order number to create the delivery
    LT03 Create Transfer Order. EG. Warehouse: 101 and enter. Picking background. Save
    The Transfer order should now be saved. It now needs to be confirmed.
    In LT03 go to menu option Transfer Order -> Confirm – Transfer Order
    Enter
    Save
    The transfer order is now confirmed.
    VL02N Delivery change. EG: Edit the delivery to do the following Pack – External customer material number = COO. External delivery number – Waybill number. BOL – Transport tag. Carrier – Header partner – SP (E.G. FXP). Tracking number = Packing Unit
    Purchase Orders
    ME22N PO Change
    ME57 Create PO from purchase requisition
    ATP
    CO09 Availability overview
    Goods Movement
    MIGO Post goods receipt
    MB51 Material document list
    MB01 Goods Movement
    Other
    MD04 Material Requirements. Shows material requirements and releases against materials
    SE38 ABAP Editor. Used to modify ABAP programs
    SM01 Transaction list. Lock transactions in the system. Also a good tool to see what transactions are available
    SHDB Transaction recorder (BDC)
    CMOD User exit \ project tool. Coordinates your changes into projects for the purpose of activating all user exits for a particular project. A user exit needs to be modified before it will work
    SE16 Table contents display
    SOST View mails sent externally from SAP
    SU53 Check authorization object
    SQVI Table Quickviewer – Used to created quick client dependent reports
    ST22 ABAP Dump Analysis
    ST01 System trace
    ST11 Display developer trace
    ST05 SQL Trace
    SM21 System log
    ST22 Display short dumps
    SM12 Display locked entries
    With Regards,
    Vidya
    **Please reward with points

Maybe you are looking for