ABAP Query download to Spreadsheet problem

Hi,
Using the Output Format "Spreadsheet" radio button choice from within the ABAP Query selection screen (accessible through SQ00) results in a certain user getting ONLY the pop-up that says "Save the data in the Spreadsheet", but the Excel Spreadsheet itself does not pop-up.
We are on 4.7 and the user is using Excel 2007. I suspected settings from within Excel, as well as perhaps the SAP Profile settings for the user in SU01, but am not sure what to check or where to look.
If the user chooses ABAP List or SAP List Viewer, they can correctly save the data to an Excel spreadsheet of their choice path. It just doesn't seem to work with the Spreadsheet radio button?
Hoping for some advice on where to look / what to adjust.
Thanks!
Jeremy

More info from the user, after I discussed an SAP GUI upgrade with her, indicates that it used to work well before she was moved from using a physical laptop to being on VDI and is now accessing a Virtual Machine. Our whole company is converting to using virtualization to provide virtual desktops. I will try to get her upgraded to the latest GUI, since our Basis group is piloting it. That might do it, and I'll report back to this thread.
While I try that, does the additional info of VDI seeming to "break" this, trigger any thoughts?
Thanks
Jeremy

Similar Messages

ABAP query download/upload

Hello experts,
How do I get the query name from its generated program and how to download/upload queries from system to system (4.6C to ECC6)?
Please help, thanks!
Chuong

program name behind query: SQ01 / Query / More function / Display report name
for transport use program RSAQ3TR (from SE38)
correct process:
export from source system with above program (it creates a transport request)
release transport (like any other transport)
import transport into target system
import transport with the above program
hope this helps
ec

Duplicate Records in ABAP Query

I have prepared ABAP query with tables KNA1, KNB1, BSID. I have mapped only BUKRS and KUNNR from BSID . as I don't have any condition to map the fields. I want only one record for considering KUNNR and BUKRS in report . But in report It is displaying all entries from BSID considering BUKRS and KUNNR means for documents all line items.Kindly suggest as soon. How to avoid such duplicate records

Hi,
Duplicate Records in ABAP Query
Regarding on your problem,
Use these link, It will helps to your post
ABAP Querry Duplicate entries
Regards,
Sekhar

Problem with logical database DDF in ABAP query

Hi All,
I have created an ABAP query via the transaction SQ01 using the logical database DDF to retrieve customer master data from tables KNA1 & KNB1. The selection screen used is the screen 903 of the logical database DDF. But now the problem is that when I execute the query, I am getting a blank value in the tax code4(KNA1-STCD4) field though there is value in the KNA1 table for this particular field. This field was added to the table by means of a customizing include. Can anyone suggest a way to get around this problem so that I can view the content of the field STCD4 in the query.
Thanks and regards,
Sarath.

I think it's not used by DDF.
so you must check it with:
check kna1-bran1 in s_bran1.
A.

Problem in Currency field in Abap Query

hi.
I have created an additional field for storing the currency type.
Based on some calculations i want to store the currency type into this additonal field.But the problem is that the currency field is not getting displayed in the report though i am getting the currency type in the additional field when i check it while debugging. Can anyone help me out...

Vimal,
Is it ABAP Query problem(SQ01).If yes, then
In tcode SQ02(Infotype)>press extras button(F5)>In right side you will find 4 tabstrip buttons.Press on Extras--> create variable with same type of currency.
goto Field group button--> add this field to field groups.
In record processing event after your calculations assign your value of cuurncy to this new variable.
In tcode SQ01-->enter query name >F6>F6>F6>select your new varaible
>Press on basic list button(shift+F4)>left side you will find additional fields Node From there select your new field-->Save come back and execute the query.Now you will find your variable.
Don't forget ot reward if useful....

ABAP query problem.

Hi All,
I have one ABAP query which has been created for vendor details. Its using standard sap LDB KDF. Now there are some fields in vendor classification which are not there in LDB. so i need to add these fields in ABAP query.
those fields are in other tables, ehich are not been used in standard LDB.
Can anybody suggest me. Its really urgent issue.
Regards
Azad.
If any further clarification required about the problem please get back to me.

Azad,
You will need to change the Infoset using tcode SQ02 (Probably copy current infoset and change in the new one), in new info set you can add tables and even custom fields with ABAP code behind them.
Thanks.

ABAP Query display variant problem

Hi,
We have three different SAP clients development DV1, Staging ST1 and production PC1. I have created an abap query for which I m trying to create a global display variant (not user specific). I m able to do so easily in DV1 and PC1 systems. But when I try to create a display variant on ST1 by first running the report and then going to menu Settings->Layout->Save . I find that by default the User-Specific checkbox is selected and disabled. Because of this I can create only user specific display variants for my queries.
Where can I change the settings so that when I go to the above menu the User-specific checkbox is enabled and I m able to create global display variants ?
Thank you for reading.
Krishna

I am confuse after reading your question , any way we can adding "default" variant in SQ01. You can also assign the same variant in SE93 , when you create T-code for the specific query !!.
Well if it doesnt solve your problem ..please explain your question with the help of tr. codes and what youre trying to do !!
Im sorry , its really making me knutt by reading your question again and again .
Thanks
Saquib
Message was edited by: Saquib Khan

ABAP Query transport problem

Dear All,
I need to copy queries from Standard Area to Global area. When I use the transport facility (SQ03 --> Environment --> transport), it does pop-up the transport workbench request screen at the first time. I created one transport request number for it. After that, I accidently deleted the transport request without released it first. Now I have problem to add back the queries into the new transport request since the prompt for transport workbench request is not pop-up even I successfully copied the query from standard area to global area.
Is there any suggested solution?. Thank you in advance for any suggestion.
Edited by: shahrir razlan on Apr 16, 2008 6:36 PM
Edited by: shahrir razlan on Apr 16, 2008 6:37 PM

chances are very very slim.. (i think zero) to delete a request, when it has objects .
so your statement - "I accidently deleted the transport request without released it first " doesnt sounds logical...
either you have removed your objects from the list before deleting the request..
but if that was teh case, then it shud pop up for new request..
as it is not asking for new request.... it is almost sure, that it is still in some request..
look hard in se01 - your request shud be there... description shud be something like 'transport for abap query'.

Problem with ABAP QUERY LDB

Hi to all,
I am using LDB for ABAP Query. For this I given selection fields. I don't want selection screen as like standard one. Ex. For QM11 transaction what ever screen appering like that my query smae appering . Please give solution for this. I want my selection fields only in my selection screen while using LDB.
Thanks.

Resolved

ABAP Query Variant Problem

Hi,
I am trying to Execute a query through Program
I had copied standard querys (ME80FN) Program RM06EAAW to my custom program
In that program , it is caaling a query and assigning one variant
Any idea from when that variant was assigned or How to create variants for ABAP Queries??
Thanks
Chandrasekhar J
Edited by: Chandrasekhar Jagarlamudi on Feb 20, 2008 1:08 AM

Hi,
Check these links...
http://help.sap.com/saphelp_nw04/helpdata/en/62/bc934814ba11d6999900508b6b8b11/frameset.htm
Re: ABAP Query variant - Error during SE93
Hope it helps u...
Regards,
KK

How to transfer ABAP query from one server to another server

Hi all,
I have a ABAP query in development server and i need to transport it to production server.
I have attached a transaction to it using the program which got generated in the back ground
from the abap query in the developemnt server.
I have downloaded and uploaded a ABAP query from one server to another server.
But the program which got generated in the back ground in the production server is different from
program which is generated in the development server.
But my transaction is attached to the program in the development server.If i transport the transaction
to production server,it is giving error since that program is not present in the production server.
Am i going in the right way......?
Is there any problem in my upload/download procedure ?
Is there any way to achieve my purpose ...............?
Please kindly reply me at the earliest.

You have different ways to call a query using a t.code. One way is to create a pgm with the following code and attach a t-code to it.
data: gv_test type sy-repid.
DATA: GV_USERGROUP TYPE AQADEF-BGNAME VALUE 'FI',
      GV_QUERY TYPE AQADEF-QUNAME VALUE 'ZCON_FI_QUERY',
      GV_RNAME TYPE AQADEF-PGNAME .
CALL FUNCTION 'RSAQ_REPORT_NAME'
EXPORTING
    WORKSPACE        = ''
    USERGROUP        = GV_USERGROUP
    QUERY            = GV_QUERY
IMPORTING
   REPORTNAME       = GV_RNAME
* For the dynamic excution of the called query assisgn GV_RNAME to <gv_test>.
gv_test = GV_RNAME.
SUBMIT (gv_test) via selection-screen and return.
Alternate way is while creating T-Code you choose option Transaction with parameters.
Transaction as START_REPORT and in default values table control at bottom give as follows
D_SREPOVARI-REPORTTYPE = AQ
D_SREPOVARI-REPORT = User group
D_SREPOVARI-EXTDREPORT = Your Query name
Regards
Sathar

ABAP Query Transport request related

Hi,
I have created a Abap query,
1) User group
2)Infoset
3) Query
But when i transport the request in to Quality, I can see only Infoset, not able to see User group and query which i created in the
Development
Please suggest, is this std behaviour or is anything missed
Rgds,
Jai

Thanks to all,
I just created TR with new package for user group and included ifoset and query in the same TR
and imported, issue is resolved
But my question is,where we can utilize below help material, I have spent much time to understand below given explaination and finally left without any conclusion
Short text
SAP Query: Transport tool
Description
The report RSAQR3TR handles all tasks concerning the transport of queries, InfoSets and user groups.
General information
Queries, InfoSets and user groups are stored in the table AQDB. This table is client-specific. For the transport of queries, InfoSets and user groups, there is a special client-independent transport table called TAQTS. You can carry out transports either
·     from a client (source client) of an SAP system to another client (target client) in the same SAP system or
·     from a client (source client) of an SAP system (source system) to a client (target client) in another SAP system (target system).
In both cases, you have to perform similar actions.
The objects to be transported must first be copied from the source client using an export from the table AQDB into the transport table TAQTS. At the same time, a transport request is created for the transport system that includes all entries created by the export from table TATQS (transport dataset). The name of this transport request conforms to the transport system naming conventions (sysKnnnnnn) and is included in the export log. The transport dataset is stored in the table TAQTS under a key which matches the name of the transport request.
If you are transporting within one SAP system (from one client to another), you can import the transport dataset from the target client. The name of the transport request to use for this purpose is that specified during the export, since it should match the key of the transport dataset in the table TAQTS. With this import, the transport dataset is read from the transport table TAQTS and inserted into the table AQDB, where extensive checks ensure that there are no inconsistent statuses in the table AQDB.
If you are transporting from one SAP system to another, you must first use the transport system to release and export the transport request generated by the export. This transports the transport dataset from the transport table TAQTS into the target system. Then, you can import from the target client of the target system, as described above.
The transport datasets generated by exports in the transport table TAQTS are not deleted after successful import unless this is explicitly requested. Therefore, you can import a transport dataset several times (when copying a functional area to several different clients, for example).
This report handles exports (generation of transport datasets), imports (reading of transport datasets) as well as the management (display and deletion) of transport datasets.
As transport action, you must specify one of the values EXPO (export), IMPO (import), SHOW (display transport dataset) or DELE (delete transport dataset).
Transport action EXPO (exports)
If you select the 'Test only' parameter when exporting (no blank characters), the system determines only those queries, InfoSets and user groups that would be selected according to the selections for transport described below and generates an appropriate log. A transport dataset is not generated in the table TAQTS. This allows you to check whether a selection really includes the queries, InfoSets and user groups to be transported.
With exports, there are four different options for selecting objects (user groups, InfoSets, queries) to be transported. These are 'Transport of user groups', 'Transport of InfoSets', 'Transport of InfoSets and queries' and 'Transport of queries'. You must choose exactly one of these transport types.
In each case, you can also define an import option depending on the transport type. This allows you to determine how the transport dataset is inserted in the table AQDB of the target client during a later import.
The import options, each of which has an abbreviated syntax,
are as follows:
REPLACE or R
MERGE    or M
GROUP=ug or G=ug    (ug = name of a user group)
UNASSIGN or U
If you use the transport type 'Transport of user groups', all user groups are transported according to the select option 'user groups' and the selected import option. The import options REPLACE and MERGE are allowed.
If you use the transport type 'Transport of InfoSets', all InfoSets are transported according to the select option 'InfoSet' and the selected import option. The import options REPLACE, MERGE, GROUP=ug and UNASSIGN are allowed.
If you select the transport type 'Transport of InfoSets and queries', all InfoSets are transported according to the select option 'InfoSets' and the selected import option. The import options REPLACE and MERGE are allowed. Also, all queries are transported for each functional area selected, according to the select option 'queries'. In this case, the user groups of the queries are irrelevant and only the import option REPLACE is allowed.
This transport type allows you to transport a modified InfoSet and all the associated queries.
For the transport type 'Transport of queries', all queries are transported according to the select option 'User groups' and the select option 'Queries' as well as the selected import option. The import options REPLACE and GROUP=ug are allowed.
The export log displays which user groups, which InfoSets and which queries are transported, as well as the import options used.
Transporting a user group
Transporting a user group means transporting all members of the group from the source client. However, the InfoSet assignment to the user group in the source client is NOT transported.
The import option REPLACE first deletes all members of the group in the target client and then enters the members from the source client.
The import option MERGE leaves all members of the group assigned in the target client and adds the members of the group from the source client.
Entering a new member in a user group in the target client is possible only if a user master record exists.
In the target client, the assignment of InfoSets to this user group remains.
Transporting an InfoSet
Transporting an InfoSet means transporting the InfoSet and the InfoSet assignment to user groups in the source client.
Importing an InfoSet is possible only if the same logical database exists in the target client. Extensive checking is also performed to ensure that there are no inconsistencies between the InfoSet and the logical database.
The import option REPLACE first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries dependent on the InfoSet. The InfoSet is then transported to the target client and the assignment of the InfoSet to user groups is copied from the source client, if user groups also exist in the target client.
The import option GROUP=ug first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries referring to the InfoSet. The InfoSet is then transported to the target client and assigned to the user group ug of the target client, if such a user group exists.
The import option MERGE leaves the assignment of the InfoSet to user groups in the target client and transports it to the target client. It then copies the assignment of the InfoSet to user groups from the source client if user groups also exist in the target client.
The import option UNASSIGN first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries referring to the InfoSet. The InfoSet is then transported to the target client. No assignment of the InfoSet to user groups is performed.
Transporting a query
Transporting a query means only the query itself is transported.
Importing a query is possible only if a corresponding user group (see below) and a corresponding InfoSet exist in the target client and if the InfoSet is assigned to the user group. To demonstrate the effect of the import options, suppose that the query has the name QU and belongs to the user group BQ in the source client.
The import option REPLACE overwrites the query QU of the user group BQ in the target client if the user group exists.
The import option GROUP=ug overwrites the query QU of the user group UG in the target client if the user group exists. In this case, the query is explicitly assigned to a user group in the target client. This target user group may be differnet from the user group in the source client.
Transport action IMPO (imports)
If you choose the 'Test only' parameter with imports, only a test import is performed. This means that the system performs checks as for a real import and generates an import log. The import log contains information on the locks that have to be set. With a test import, you can check whether a transport dataset can be imported without any problem and which changes it would make in the table AQDB of the target client. A test import itself never makes changes in the table AQDB of the target client.
All transport datasets are imported according to the select option 'transport request'. In this case, the system outputs a detailed log of all checks carried out and all changes made in the table AQDB.
If you select the parameter 'Delete after successful import', the transport dataset in the table TAQTS is deleted after the import of each transport dataset if no errors occur during the import.
Transport action SHOW (display)
All transport datasets included in the transport table TAQTS are output with name (also the name of the transport request) and contents in the form of an overview.
Transport action DELE (delete)
All transport datasets are deleted according to the select option 'transport request'. To avoid unintentional deletion, the select option 'transport request' must contain values, meaning that the transport action DELE is not performed if this select option is empty.
Transport of ABAP Query
I am involved in this upgrade project to 4.7
The users are not able to find any reports (in QA System) which were there before the upgrade in SQ01. But they can see them in production which is not yet upgraded. They want me to copy all the reports to the QA system now....I dont have any idea how to do that.
I remember a similar problem upgrading to 4.6C from 4.5B ......
Take a look at OOS note 672784.
You can transport queries between systems in SQ02 (hit the lorry button) or run program RSAQR3TR.
You download the infosets, queries etc into a file and load them into whichever system you wish.
Just wanted to share my experience of transporting queries:
I needed to move a user group, 2 infosets and 3 queries from a 4.6 system to a 4.7 system.
When I tried doing this via the SQ* transactions I did not get the import/export option, so instead ran RSAQR3TR.
Step 1. Run RSAQR3TR in 'old' system. Select EXPORT and specify the objects to be transported.
(System includes these in an automatically created transport request)
Step 2. Release this transport and request it be transported to 'new' system.
(This results in the entries being populated in transport table AQTDB in 'new' system).
Step 3. Run RSAQR3TR in 'new' system. Select IMPORT and tick the Overwrite checkbox. Specify the transport number in the field labelled 'dataset with imports'.
(RSAQR3TR gives the message that stuff has been imported OK).
Step 4. In my example I still couldn't find the queries, so ran RSAQR3TR one more time, this time specifying 'Copy Standard Area -> Global Area'.
(Now my queries etc were available in new system).
Perhaps there are better ways, but after 1.5 days of struggling I was glad to get this far.
regards,
Jai

Performance tuning for ABAP Query (created from t-cd SQ01)

Hello all,
We created ABAP Query report from transaction SQ01.
But the generated report has an appropriate SQL statement which causes performance problem.
To solve this issue, I guess the easiest way is;
0. Give up to use it.
1. Copy it to another object in the customer namespace.
2. Ajust SQL statement.
But I'm wondering if there're appropriate ways to adjust SQL statement of Query.
Could anybody give me any better idea?
Thank you
Yuko

You can try this: Create 2 ranges, for objnr and cdtcode and fill like:
ra_objnr-sign = 'I'.
ra_objnr-option = 'CP'.
ra_objnr-low = 'OR*'.
append ra_objnr.
ra_code-sign = 'I'.
ra_code-option = 'CP'.
ra_code-low = 'CO*'.
append ra_code.
SELECT objnr udate utime
FROM jcds
INTO TABLE it_jcds
WHERE objnr IN ra_objnr
AND stat = l_tj02t
AND cdtcode IN ra_code
AND inact = space
Regards,
John.

Getting error while assigning ABAP Query to Tr.Code

Hi Guys,
There is a problem iam facing with ABAP query while transporting which need to solved asap. It will very greatfull if u guys can resolve this problem.
My problem is, I created one ABAP Query with Name ASSETOVERVIEW. I had transported this even, now when iam going to assign it to one transaction code with se93 lets say ZAOR. I need to give its description and program name in se93 right. now my question is what is program name i need to give in se93. Bcoz in SQ01 where i created the query, there is no name as 'program name' rather there is 'Name' in that we will create the query name i.e, ASSETOVERVIEW. In se93 u give tr.code and when u see down there will be radiobuttons in 'start object',in that i had checked program and selection screen (report transaction) is this right button i had checked or any other i need to check?. I had assigned this name i.e,ASSETOVERVIEW and development class and then when i check the name for syntax check its giving "'ASSETOVERVIEW' does not exist". I don't understand what program name i need to give.
If u guys can help me out with this problem it will be very much appreciable and definetly can get the reward points.
Thanks for as usual help in advance.
Regards.

Hi omer,
1. Just run the query.
2. one selection screen will come
3. then using SYSTEM---->STATUS, (from menu)
look for the program name
4. the program name will be something wired foramt.
/asdfasdf/asdfdas etc.
5. Give that name in se93.
regards,
amit m.

How to get the name of an executing ABAP query in run time

Hi ABAP Gurus,
I need to get the ABAP query name when it's running. For example we can get the current executing ABAP program name from SY-REPID.
My tried logic - every query generates an ABAP program like AQZZUGQUERY. 'UG' stands for user-group name and the length specified for it is 12, if the length of the user-group name is less than 12, then the rest will be filled by '='. Next 'QUERY' stands for ABAP query name and the length specified for it is 14, if less, then the rest will be filled in with '=' in the right. I've tried to extract the query name by using cut and trip (offset) operations.
But somehow this logic is not working - always it's picking up the function name as checked in debug mode.
Guys - Can you please provide me the solution on this.
Thanks & regards,
Jayanta Bej.

Guys,
I've cracked the issue. Instead of retrieving the query name from sy-repid, I've retrieved it from sy-cprog and the problem is resolved.
Thanks guys for your quick responses.
Thanks and regards,
Jayanta Bej.

ABAP Query download to Spreadsheet problem

Similar Messages

Maybe you are looking for