Query could not be saved

Question

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

Answer 1

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.