Query is not saving in QUERY DESIGNER ??

dear experts / friends...
iam selecting the particular query in query desginer and trying to change the text view as stadard to short...
but while doing this am getting an error like...
status message
Error package ZKJ2 does not exist
please suggest me i want to make small changes for that particular query and have to save....
thanks in advance
regards
anand

since the package does not exists.. you either create 1 or use any existing
If you wish to use existing one.. go to RSA1 -> transport connection -> query.. find your query and piull on the right pane... change the package button... give here any of the existing package name... also ensure your transport request has this same package...
if you want to create the package..
go to SPACKAGE tcode ... here create the package

Similar Messages

SAP Query when saving title for Query is not saved if we reopen queries o

Hi,
i am not able to save title for a query that is already created,
when i change and give the title name and comes back it is seen in scree SQ03 but
reopen the Transaction Sq03 by selecting user group and query the title is not not displaying.
can anyone help me on this, it is Urgent.....
Thanks in advance.
Regards
Adarsh.

Hi,
Change the title of the query in tcode
SQ01-->change
here change the title and save
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Apr 14, 2008 3:49 PM

Query could not be saved

Hi Experts!
I Created a Query.When i click save,iam getting a message..1. The query could not be saved due to a problem
            in transport.
         2. Bex transport request is not available or not
            suitable.
         3. choose an existing request.
Could the experts give me suggestions to steps has to be taken.Its a bit urgent.
Thanks in advance.
diya

dear Diya,
new query should have no problem with transport,
you may need to create a new bex request,
rsa1->transport connection->click button truck icon with bex, assign to package/development class,
'unfortunately' you may need to logout and login again bex analyzer.
and you aren't creating query directly in production server right ?
check the possible problem cause with oss note
194051-Transport problem when saving queries
Symptom
An error occurs when you save a query:
Error when saving
"The query could not be saved due to a problem in transport".
Other terms
Business Explorer, query, transport, save, R9 124
Reason and Prerequisites
There are 4 possible reasons for this problem:
1. The BEx default transport request or the development class-dependent transport request is not maintained or released in the Administrator Workbench.
2. The system is set to "cannot be changed". Refer to Note 337950 (as of 2.0b SP 11), which describes how query objects can be edited in systems that cannot be changed.
3. You are not authorized to write to Workbench requests.
4. The BEx default transport request or the development-class-dependent transport request in the Administrator Workbench has another target system than the query (the transport destination of the query is determined via the transport layer of the query's development class (as of 3.0: of the package)).
The error only occurs for query objects which already have a development class, that means, which were already placed on a transport request.
Solution
Solution for Cause 1:
a) Start the Administrator Workbench
b) Choose 'Goto' to change to Transport connection
c) Choose "Request BEx" or "BEx development classes" in the toolbar.
d) Create a (new) request.
e) All changes in the BEx are now written to this request.The end user is no longer confused by 'Transport' dialog boxes.
Solution for Cause 2:
See Note 337950
Solution for Cause 3:
Authorize user to write to Workbench requests.
Solution for Cause 4:
Create a request for each target system. Assign the request suiting the target system of the transport layer of the development class (of the package) to each development class (as of 3.0: to each package) used for BEX objects.
If this does not change the situation, further information is useful for error analysis.
Go to Transaktion SE16, Table RSZCOMPDIR. In field COMPID, select the technical name of your query. Read the COMPUID of your query.
Go to SE37, function module rso_elem_get_related. Parameter I_IOBJNM is set to the COMPUID, and parameter I_OBJVERS (object version) is set to A. Only the export parameters E_T_OBJ_EXISTENTIAL and E_T_OBJ_DEPENDENT are of interest.
These entries are then entered in function module rs_tr_objects_check_insert in import parameter I_T_TR_OBJECT. In this parameter, fill field PGMID fixed with 'R3TR' and field OBJECT fixed with 'ELEM'. Field OBJ_NAME is filled with the contents of field OBJNM from export parameters E_T_OBJ_EXISTENTIAL and E_T_OBJ_DEPENDENT. The other fields are not relevant.
The export parameters of this function module are required for further error determination. Add this information to your OSS message. The table of messages E_T_MSG is important in particular.
hope this helps.

Scope in your query does not exist

I've created a Search Center Site Collection but the results aren't being refined based on the scopes and I'm getting the message that the Scope in your query does not exist The query is being formed correct as this is what the url displays:
/Sites/Search/Results.aspx?k=bcm&s=BCM
The scope contain one Include rule and the rule seems to work, in that it is finding items (118 in the below example) but the Total is 0. I've tested this similiar configuration in another test site and it shows the same number for both Item Count AND
Total AND it works correctly so I'm guessing this is the issue.
Any ideas?
Joe

Inderjeet,
Both the dev and prod are different is that dev is using a search site col and dev is using just a search page as follows:
dev - http://dev.com/Search/Results.aspx?k=test&s=ACM
prod - https://prod.com/Sites/Search/Results.aspx?k=Test&s=ACM
As for permissions...I noticed that the Ribbon is greyed out in the Search Site Col. I'm an Owner and can add users to that group but am not being provided any access to ribbon.  Could that be an issue?    I still find it
odd that the Scope indicates results but that Total is blank.
If I rerun the query while on the results search page then it returns results
https://prod.com/Sites/Search/results.aspx?k=test, so it can find the data.
Joe

Why SQL queries are not saving in agentry editor for first publish?

Hello Experts,
In the process of developing an agentry application i have defined SQL steps and saved in agentry editor with out any errors .When i have published definations for first time it is displaying error 'Invalid object some where' in back end SQL log file ,when i have seen in editor some times the query is not saved,some times even it is defined then also the same error.So i have copied the steps and saved again.Now i have done a publish,it is working fine.This is happening only when i implement exchange mechanism(Showing error in ATE getfetch error).But with out exchange mechanism it is working fine.Is this related to the installation of editor plig-in is not correct?. I have done preferences setting in my workspace correctly.
Help me in this regared.Thanks in advance.
Thanks & Regard,
Sravanthi Polu

Sravanthi,
For your error: displaying error 'Invalid object some where' in back end SQL log file.. This is happening only when i implement exchange mechanism(Showing error in ATE getfetch error)
Two suggestions (My best suggestion is item 2 below - I think that is where you have the error)
Item 1: Are you using the right encoding? In your Eclipse Editor under the main menu Windows - Preference -> General -> Workspace. What is your Text file encoding set to? Cp1252? Try setting it to UTF-16.
There is a tutorial about this in:
https://service.sap.com/sap/bc/bsp/spn/esa_redirect/index.htm?gotocourse=X&courseid=70246375 (Enterprise Academy classes). The course is really a simple < 5 minutes discussion on different types of encoding and why they exist and how to change the Eclipse to what you wanted. SQL is normally done in UTF-16 for 16 bit.
I am assuming that the encoding could be wrong.
Item 2: Another thing that could be wrong is how you specify the SDML (Flunky code).
In your SQL Script: Anything that has the "<<" and ">>" open and close marker is an SDML (Data Markup Language) and needs to be pre-populated before the Agentry Server submits your SQL query to the backend. In essence, this is use to populate the SQL query with predefine information like your userID or location and when the SQL gets process it will populate the script with the correct information.
So if you are not properly using the flunky (ex: <<object.address>> where address is not a key ID in a Fetch step (Check manual for usage of SDML AgentryLanguageReference_6.0.0.0.pdf) then you may get invalid object.
When you do a SQL "Fetch" Client Exchange and Server Exchange Steps, you can select a few options:
For this discussion let us talk about these 2 items below.
1. Run Attribute: Run One Time
or
2. Run Attribute: Run Once Per Object.
When you select Run Once Per Object the only available Flunky or SDML commands you have are:
object.keyPropertyName
lastUpdate
fetch.messageNumber
The 3 above are your only options
If you try to do something like object.property1 where property1 is part of your object properties then it will not work for Run Once Per Object.
It may work for Run One time as fetch.propertyname.
From your symptoms where you are complaining about an issue in exchange steps, your error is a typo or a misused or a misunderstanding of how fetches and SDML works (documented in page 398 or 399 of AgentryLanguageReference_6.0.0.0.pdf).
See pictures just in case you don't have access to that pdf file (The picture below simply proves what SDML options is available for your Fetch Client Exchange Step).
Hope this helps.
Regards,
Mark Pe
SAP Senior Product Support Engineer

Downloads not saving to Downloads folder

Downloads are not saving to the designated "Downloads" folder in My Documents.
Instead, they are saving to C:\Documents and Settings\{username}\Local Settings\Temp.
Tools/Options setting is pointed at Downloads, but the files just aren't saving there.

It is possible that your anti-virus software is corrupting the downloaded files or otherwise interfering with downloading files.<br />
Try to disable the real-time (live) scanning of files in your anti-virus software temporarily to see if that makes downloading work.
See "Disable virus scanning in Firefox preferences - Windows"
*http://kb.mozillazine.org/Unable_to_save_or_download_files

Query View name not saved in "Analysis Grid Properties" under Data Provider

Hi BW World;)
We are on BI 7.0
I have created a BI workbook which contains a query view.
However when we go into design mode and then "analysis grid properties" for this query view then "change data provider" it does not show the query view name but the query name. (we have saved the workbook)
Is this the normal scenario?
Surely should show the "query view name " and not the "query name" as confuses what data provider is being used?
Is this a bug?
Best
Stevo.... Points of course... Thanks in advance.;)
Edited by: bw4eva999 on Sep 10, 2009 4:40 PM spelling

Hi,
You have created a workbook on top of a Query View which is again depends on a Query.Now the base for Query View is a Query.So the underlying Data Provider for a workbook is a Query.
Hence when you go to Properties of grid->Change Data Provider,it shows the Query and the InfoCube,but not the Query View.
So this is not a bug and this how its been designed.
If you click for the Information of that workbook,it will show the Query and Info Provider,but not the query View.
Though it looks like wierd,it is not a bug.
Rgds,
Murali

Infoobject in infoset but not displaying in query designer

Hi,
I have created a query on infoset(ods1 & ods2).
a custum defined infoobject (fiscyr) is not displaying in query designer while it is present in infoset.
pls give your inputs,for why this infoobject is not available in query designer.
Thanks
Radika

Hi Radika,
I cannot think of anything other than the solutions already mentioned in this thread (checking the IOBJ in infoset, running RSISET and activating it). I just had a foolish idea that you might not be looking for the right IOBJ. All the IOBJs from an infoset are not displayed with their original technical names in the query designer. They are disdplayed in the format: <infoset_technical_name>_FXXXXX where XXXXX is a number.
Also try one more thing. Go to transaction RSISET and type in the technical name of the infoset there.
Right below the box where you type the Infoset name is a check button. Check your Infoset there and then activate it from within the RSISET transaction (the activate button is right after the check button). With Infosets, sometimes just activating it from within RSA1 does not work but RSISET always seems to work.
Do this and see if it helps.
Thanks & regards,
Nikhil

The Query Could not be saved due to a problem in Transport

Hi All,
we move the data from DEV to QAS but in the QAS when you are going to save as query giving this error
error: The Query Could not be saved due to a problem in Transport
can any one please tell me the solution for this
thanks
sidhartha

Sidharth,
When you create a transport request for queries in Transport connection, what is the grouping condition you have taken and also please be ensure that all the query elements have to be selected to transport that query.. Please check whether all the elements have been selected or not.. You can check this out in SE09 under your request.
Hope this helps...
****Assign Points****
Thanks,
Gattu

Mapped characteristics in Multiprovider not available in Query Designer

Hi,
we have a multiprovider with approx 10 cubes and lot of characteristics, Navigational attributes mapped to it. I have added around 3 more characteristics and mapped to underlying cubes. But these added characteristics are not visible in Query designer. Is there maximum limit for the number of characteristics.
Thanks,

Disconnecting the BEx made it work. But i dont understand i added this yesterday in the multiprovider. But i also removed some navigational attributes from the mapping. I will re-map and check. Thanks for the tip.

Hierarchy node not available in Query Designer

Hello Gurus,
I can find the hierarchy node variable in BW but it is not available in query designer. Does anyone know what might be the problem and a solution?
Thanks,
Mark

Hi Mark,
You said you "find the hierarchy node variable in BW but it is not available in query designer".
How did you find the hierarchy node variable in BW? From backend SAPGUI, you will only be able to see the variable in some internal tables like RSZGLOBV. Did you mean this?
For "it is not available in query designer", do you means that when you want to create a hierarchy node variable for this characteristic in Query Designer, you don't find this certain hierarchy node variable in the hierarchy node variable list?
Important thing to notice is that, flat value variables and hierarchy node variables are listed separately. Did you make sure that you have chose to list hierarchy node variables in Query Designer?
Regards,
Patricia

The Report Designer does not support this query drill down colum

Iam working On BI7 When iam doing report desingner when iam opening query through data provider
Iam getting thsi error The Report Designer does not support this query drill down colum colum axis may contain one structure only remove additional dimensions
I modify the cube and i remove some dimensions also My problem is when iam putting characterstics in Colums Iam getting this error When iam removing that charcterstics from colums it was not throuing any error
Chaitanya

hi,
report designer is for front end view design and the designcan be done with restriction to navigation.
you have dynamic and static report designs with restricted navigations.
chk the links for document
http://help.sap.com/saphelp_nw04s/helpdata/en/dd/cea14119eb9f09e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/17/16d941de405f24e10000000a1550b0/frameset.htm
Ramesh

Need help regarding "saving a query"

Hi BW gurus,
I have a few doubts.
I developed few queries in the DEV and i transported to QA.
Since DEV was not having much data i could visualize the report(graphical report) if it meets my reporting specs.
So i made the query changes directly in the QA system, and i created a workbook,which contains plenty of Excel work and macros programming.Now my report is ready in QA.
These are my doubts
1.Can my queries and workbooks be transported to PROD without any problem from QA?
2.I tried to make the similar changes to the queries in DEV ,and i tried to save it,but i got an error on the Query Designer window stating that,the query cannot be saved due to a problem in the transport?
Tell me what are the ways to solve my problems
Thanks in Advance,
Have a nice day
Regards
SM

Hi Sam,
When you need to make any changes to any object BEx related or AWB objects, the changes have to be first made in the dev system and then transported to QA. If there is a difference between the QA and the dev system the transports might fail.
And as you already got the solution. Create a BEx Transport Request in Transport Connection and then make the changes to the query and save. Then you can transport the same to qa and prod without any issue.
How this helps.
NewBW

How to design a query without using Net Weaver Query Designer

Does anyone know if any alternative way to <b>design an query without using Net weaver GUI</b>? in order to reduce the time consuming, I am wondering if there have any method which can define/modify a stack of cells, characteristics and structures without work through the GUI.
Deeply thank for any of your advices.

Can you give an example?
Just from what you write, I would assume that you talk about something like a mass-property-changer. As far as I know the BEx this is not really possible, but what I do normally is building one query and then either using query-views (saving more or less the navigation state) or by copying and changing the properties of the few characteristics and key figures.
But without a specific example it's difficult to exactly understand what you exactly need.
Mario

Available OLAP connection list not showing in Query browser

Hi all,
Hope everyone is doing great. I tried using query browser to consume BEx queries in dashboard. But I am not able to see the available connection list after choosing BEx query as my source in query browser. Attaching a screenshot of the same.
Request your assistance in solving the issue. Am i missing any settings ? Please help
Many thanks in advane,
Nikhil Joy

Hi Nikhil,
Are you able to see the list of universes (Unx)?
Also you could check the following
1. Logon to Central Management Console (CMC).
2. Go to Applications.
3. Now double click on Web Service and go to Properties.
4. Update the Access URL as mentioned below and click on Save & Close:
http://<WebServer>:8080/dswsbobje
Confirm if this URL is accessible in the browser.
5. Launch Dashboard Design, open Query Browser, click on Add Query and enter BusinessObjects Enterprise logon credentials.
Regards,
Noopur

Query is not saving in QUERY DESIGNER ??

Similar Messages

Maybe you are looking for