Transport request failed-inactive version of query element.

I have transported 70 reports from BI development to production.
the request has failed due to inactive version of the query element.
How to find which report the query element belongs.
Please advice how should i troubleshoot this issue.

Murali, check this table :RSZELTXREF
enter the element name in field TELTUID. Then from the result, select the value of field SELTUID and enter it as value of field ELTUID to check data of table RSZELTDIR.
That will give you the query name.
Regards
Ashwin.
Edited by: ashwin kumar on Apr 27, 2010 10:11 AM

Similar Messages

Transports, M version of query element missing in Dev

Hello
We're trying to import transports to a system copy of our Development system but when trying to do so we get an error in RS_AFTER_IMPORT saying "Element XYZ is missing in version M". (The transports comes form Dev). The element is a Text-variable
When checking in table RSZELTDIR in Dev-Copy I do only see A and D versions of the element XYZ. The same is true in Dev. But in QUA and PROD the element exists in A, D and M versions.
Is this normal? And how do we do if the transport strategy is to Transport between Dev and Dev-Copy?
Thanks in advance
/ Daniel

Thank you for your answer.
However the same transport has entered QA and PROD correctly, it's only when transporting into Dev-Copy that it fails.
Scenario :
Day 1 : a system copy was taken
Day 2-10 : transports leaving Dev going to QA and PROD
Day 11 : Dev-Copy created from the system copy from Day 1
Day 12: The transports from Day 2-10 is being imported into Dev-Copy (and Query transports failing)
So the developers have collected needed objects in the first place, but something is happening when importing into Dev-Copy..... the M versions is missing in Dev-Copy (and Dev) compared to QA and PROD
/ Daniel

Incorrect Transport Requests : SAP delivery version getting collected

Hi,
In our development system, when we try to include objects in a transport request, the entries in the transport request are getting saved as the SAP Delivery version rather than the active version.
For example an ODS ( z object, newly created in development environment) entry is being logged as R3TR DODS XXXX (Obj name) rather than R3TR ODSO XXXX.This is happening for all object types ( Info objects, cubes, workbooks etc).
Also while collecting workbooks in transport request ( using transport connection) we got the following error -Logical transport object 414Q not found in table RSTLOGOPROP. Not sure if the above two issues are interlinked.
Appreciate your help on this.
Kind Regards,
Bansi

Hi KxD,
I don't expect the loading date to be equal to the delivery date but I expect it to be 2 days before the delivery date since the time specified on the route is 2 days. So I would expect my loading date = delivery date - 2 days (route time)
The way system is acting is loading date = committed date + 2 days (route time).
FYI.. when you turn on route scheduling the delivery creation date is based off of your route time and not your planned delivery time from the material master
Thanks,
Imran

Transport request failed; recollected with new TR;what happens to first one

Hi,
I released a transport request and requested that the request be transported to the testing environment.
I received a message from Basis that the transport failed. I suspected that it might fail because I say many duplications in se09.
To fix this problem, I basically recollected the objects carefully and under a new transport request number; and released it.
I have requested that the Basis team move the new request to the testing environment.
1. What is wrong with what I did?
2. If the second request successfully gets moved to the testing environment, what becomes of the first request which was released, therefore no more available in development for me to delete? I tried to delete it under the "Released" section in se09 but got a message that it is not available to delete.
3. Could I have used the same Transport Request number the second time around, although the first number had been previously released?
Thanks

1. What is wrong with what I did?
It depends, did you check the Log.
Log should tell you why it failed or atleast give you some hints.
Ex : Missing objects ..might have been locked in an other request.
2. If the second request successfully gets moved to the testing environment, what becomes of the first request which was released, therefore no more available in development for me to delete? I tried to delete it under the "Released" section in se09 but got a message that it is not available to delete.
If the second request contains similar objects to the ones in first, everything will get overwritten in the target system.
TR1 - 10 Objects
If TR1 returns RC=8 due to one object, 9 objects will be successfully transported. You may only transport the failed one in the next request with its corrections.
3. Could I have used the same Transport Request number the second time around, although the first number had been previously released?
Yes, same released request can still be imported more than once but it may result in the same.
Try to find the reason the request failed, accordingly add objects in the next corrected request.
You can also copy requests into an other.
RClick on the request - Include Objects ( Ctrl + F11 ) - Enter Request Name.

Planning book changes transport request failed in quality.

Hi all,
I have to make some changes in Macros for one of our planning book. As per practice I made these changes in Development and tested everything looks fine and created transport request to Quality. Request failed in quality with error code 8. which says individual objects could n to transport succesfully. I further tried to analyze the issue and looked at objects and they look like Slections ids were failed. Can anyone advie how do I locate and correct these - .
I created transport request from function sapapo/tsobj and selected the planning book. I think this has selected all selctions ids also. Later I created another transport request from Planning book and this went through succesfully.
But how I can corect the old transport request which is showing in red light as error.
Thanks
KV

Hi KV,
Regarding your wrong request, you can't dop much about it.
Don't worry, I will be suprise if you were the first to have a wrong request in your system.
I suggest you check your internal practice to know how to handle this kind of request.
But basically the idea is: do not transport further. If possible "reject" it to ensure nobody will ever transport it.
Another point: in your case it looks like you don;t really want to transport selection. It is however quite useful to do so, especially for the selection used in background job. I often suggest to:
1. Have different naming convention for batch jobs selection and selection for interactive use (you can even control selection creation / usage with autorisation to avoid misuse)
2. transport all selections related to batch job. If you decide to do so, you need to ensure all these selections are correctly defined in your development AND you need to delete this selection in all your target system (to avoid the locking issue you got)
Sorry if all this is a bit outside topic...
I hope it helps
Julien

Export and Import transport request between different version?

Hi,
I have tried to Export the transport requests from ECC5 to ECC6 via STMS .Its not throughing any error but no Master datas are transported. Anyone have idea about that?

Hello,
From my experience SAP didn't recomneded transporting from 46C -> ECC5.
The structure of tables and objects are a little bit different between different
releases.
Dimitry

Import transport request fails through CHARM

Hi,
I have configured CHARM on SolMan 4.0. For a support message, I could able to create change request and change document. I am having following two issues:
1. When developer enters into change document and try to change the status from "create" to "To be Developed", it is changing and coming back to same status "create" after save.
2. I am able to create and release transport request successfully from SolMan. But when I am trying to import into Quality box, it is throwing error, saying that "could not read the import queue of Quality box". Import I am doing from SAP Change manager task list.
All the prerequisite for CHARM have been successfully done, which I verified from SPRO, check CHARM.

Hi Ruben,
Thanks for your quick update.
1. SLG1 logs shows error "unable to read CBQ import queue"
2. RFC Destination TMSADM@ from SolMan to QA connection test is working fine.
Thanks
Shiv

File Transport request failed in PI/PO 7.4 dual stack

Dear Experts,
i am transporting from QA to Production Environment of ESR objects through file transport, it is showing import successfull.
but whn i checked the latest version/modified objects those are not reflecting in ESR.
cache is clear and i have checked Cache connectivity test and also CPA Cache full.
Still we are facing are not able to see latest imported version.
Suggest....
Regards,
Kiran Polani

Hi SriGnanaKiran,
If you import the lower version than current version system will ignore the lower version of the object, may be you are importing the lower version of the object.
Also see is there any version conflicts for the object.
Regards,
Praveen.

Standard BEx transporting Request

Hi Dudes,
Can u explain me with a scenario, what is this Standard BEx Transporting Request and what is the purpose of this,
Thankyou.

Hi,
This is what note says:
Symptom
Editing of a query in Query Designer may return the various error messages concerning transport system. Query or query component can not be changed or saved.
The following error messages are possible:
'Query could not be saved due to a problem in transport' message R9 124;
'BEx Transport Request XXX... is not available or not suitable. Choose an existing request';
'Object ELEM XXX... could not be saved to order YYY...';
'A dependent object is being locked by the transport system' message R9 113
'The dependent objects are in different transport orders' message R9 114;
'The upgrade is already running - you are not able to change objects'.
In some particular cases using NW 2004s server with 3.x Query Designer
'Operation failed, no message available from server'.
Other terms
Query, Query Designer, Correction and Transport System, CTS, ELEM, Transport Request, Changeability.
Reason and Prerequisites
The error messages rise as the result of wrong administration of Correction and Transport System (CTS).
Transport System Mode
Two main modes of Transport System can be used for BW system: Standard Transport System and BW Transport System. Both modes require different administration efforts.
Standard Transport System (system default)
Within this mode an assignment of newly created query elements is done during save procedure. System asks for appropriated Package and corresponding Transport Request within this Package. The mode allows separating of changes done in the system different users in different Transport Requests. Users must be authorized to create new Transport Requests or to write into existing Transport Requests.
BW Transport System (recommended for handling of BEx objects)
Within BW Transport System initial assignment of newly create query elements is done automatically to $TMP Package. This is a Package for temporary objects and does not require modifiable Transport Request. Changes of those query elements can be done without further restrictions. Further assignment to a Package and corresponding Transport Request can be performed using Transport Connection of Administrator Workbench (transaction RSA1).
All kinds of changes for query elements which already have been assigned to any Package different from $TMP (for example, queries transported from another system) must be registered in so-called Standard BEx Request. Using Standard BEx Request all changes done to query elements can be also transported to any other system. If the old Standard BEx Request has been released, another one must be created immediately in order to allow further changes for query elements.
The typical reason for error messages listed above is a situation when NO Standard BEx Request is available anymore in the system. The algorithm of query SAVE contains a transport systems check. If the transport system check fails, no changes are possible.
Changeability of query elements
The recommended setting for query element (ELEM) is 'Everything Changeable'. Using of other settings, like 'Original Changeable' or 'Nothing is Changeable', will make editing of objects not possible when the general system changeability will set to 'not changeable' (SCC4).
Setting 'Original Changeable' allows changes only for query elements which have been created in this particular system. Quite often an ordinary query may contain, for example, variables or other reusable components created in the other systems. In this case changing of a query containing those objects will be not possible.
Changeability of Package
Package (Development Class) where the corresponding Transport Request has to be created must be changeable. If a Package has a property 'Package is not extendable' set to true, no requests can be created within this Package. This means no objects can be registered.
Solution
The following messages mainly happen if BW Transport System is activated. The existence of Standard BEx Request and correct settings for object changeability should be checked.
'Query could not be saved due to a problem in transport';
'BEx Transport Request XXX... is not available or not suitable. Choose an existing request';
'Operation failed, no message available from server'.
How to create a new Standard BEx Request?
Start Administrator Workbench (RSA1) --> Transport Connection. Find button BEx. Under the button user is able to create/assign a new Standard BEx Request.
How to check Changeability of object?
Start Administrator Workbench (RSA1) --> Transport Connection. Find button 'Object Changeability'. Set property 'Everything changeable' for query elements (ELEM).
How to check Changeability of Package?
Start transaction SE80 --> select corresponding Package --> find properties dialog. Check whether the property 'Package is not extendable' is set to false. Assignment of query elements (R3TR ELEM) to a corresponding Package is stored in the table TADIR (field DEVCLASS). In order to obtain a list of query elements used in a definition of a particular query having problems use the function RSZ_X_COMPONENT_GET with the I_OBJVERS = 'A', I_COMPID = technical name of a query. Execute the function and copy all elements (ELTUID) from the exporting table C_T_ELTDIR. Use this selection as the input parameter for selection from TADIR table (field OBJ_NAME). Collect all Packages and check the changeability as described above.
The following messages mainly happen if Standard Transport System is activated. The problem happens in case, when one or several objects from definition of a particular query have been already written in another modifiable Transport Request. In BW 3.x each object can be processed only within one Transport Request.
'Object ELEM XXX... could not be saved to order YYY...';
'A dependent object is being locked by the transport system';
'The dependent objects are in different transport orders';
The situation may happen, for example, if a Query A contains a variable which has been already used in another Query B assigned to different Transport Request. In this case, saving of Query A will be not possible while the Transport Request containing the shared variable is not released.
How to find an assignment of object to a Transport Request?
Start transaction SE03 and select 'Search for objects in requests/tasks'. Provide ELTUID of the element which can not be saved. Object type is R3TR ELEM. Search for modifiable Transport Requests containing this element. If corresponding Request is found, it can be released. After that is will become possible to save this query element into another Request.
Changing of query elements during running upgrage is not possible. The system sets a global lock in order to prevent any change which may potentially affect the consistency of objects. In such situation users should stop the upgrade procedures and wait until the process will finish.
Regds,
Shashank

Unable to collect the changed query elements to a transportable request

Hi All,
I had saved the query changes to dummy request, now I have to collect the changed qurey elements in a transportable request. This I am doing in the transport connection tab in rsa1. Now I want to collect only the changed elements of the query, & not all the elements. I have made (changes) restriction to a key figure inside the keyfigure collum. Now when I try to make a collection of this to a transport request - I am unable to find it under the query elements in the transport collection.
Pls advice how to collect it in a transport request & move it?
Thanks & Reagrds,
Shreesh.

Hi Shreesh,
It may be collected under default request. You can collect changed objects by releasing default request.
aftre releasing default request
go transport connection(TX-RSOR) object type -
>query elements -
> Query--> collect your query.
Grouping option as only necessary object
then click on "Package"
then check for your objects if not checked against your query elements(which you want to collect), plz check. at the same time check for your query name it should also be checked then only query will carry the changes.
Hope this will help you.
Thanks,
Vijay.

Add R3TR element to the Transport Request

Hello BW Experts,
I am transporting a query and get the below error message.
Element 40WVM5KB0OENRCAWG7PN2GHM3 is missing in version M
Message no. R9132
Diagnosis
Element &1 in version &2 is referenced but is not available.
System response
The action had to be terminated.
Procedure
Please supply the missing elements to the system by transport.
if i go to rsa1 > transport connection > query elements > query > select the query (options dataflow before / only necessary objects )
i do not see the element 40WVM5KB0OENRCAWG7PN2GHM3 in that list given.
I think there is a alternate way of adding particular elements to the request. Wondering if anyone remembers the transaction code / table for add a element to the request.
Thanks,
BWer

dear BWer,
use following program (create first) to locate the query element
transport
REPORT ZQUERY_DEF_TEST .
Tables: rszeltdir, "query element table
rszelttxt, "query element texts
rszcompdir, "global query elements
e071. "objects in transport requests
*parameters
parameters: Req_id like e071-trkorr.
selection screen to input long ID 25 char generated name
select-options: long_ID for rszeltdir-eltuid.
*itab to hold related info
data: begin of i_query_desc occurs 0,
local, "Local to Query
eltuid like rszeltdir-eltuid, "25 char generated ID
compid like rszcompdir-compid, "technical name
deftp like rszeltdir-deftp, "element type
el_txt(16), "element type text
txtsh like rszelttxt-txtsh, "short text
txtlg like rszelttxt-txtlg, "long text
owner like rszcompdir-owner, "owner
end of i_query_desc.
data: xlocal.
sy-tvar0 = Req_id.
*find all query objects for transport request entered
select * from e071 where trkorr = req_id and
object = 'ELEM'.
add them to the select-options list
long_ID-low = e071-obj_name.
append long_ID.
clear long_ID.
endselect.
*loop through select option table and find details of Query element
Loop at long_ID.
clear: i_query_desc,
rszeltdir,
rszelttxt,
rszcompdir,
xlocal.
select single * from rszeltdir where eltuid = long_ID-low and
objvers = 'A'.
if sy-subrc <> 0.
write: / long_ID-low, ' Query element not found.'.
write: / .
else.
select single * from rszelttxt where eltuid = long_ID-low and
objvers = 'A'.
if sy-subrc <> 0.
write: / long_ID-low, ' not found in table RSZELTTXT.'.
endif.
select single * from rszcompdir where compuid = long_ID-low and
objvers = 'A'.
if sy-subrc <> 0.
write: / long_ID-low, ' not found in table RSZCOMPDIR.'.
xlocal = 'X'.
endif.
fill itab for list
i_query_desc-local = xlocal.
i_query_desc-eltuid = rszeltdir-eltuid. "25 char generated ID
i_query_desc-compid = rszcompdir-compid. "technical name
i_query_desc-deftp = rszeltdir-deftp. "element type
case i_query_desc-deftp.
when 'SEL'.
if xlocal = 'X'.
i_query_desc-el_txt = 'Selection'.
else.
i_query_desc-el_txt = 'Restricted K/Fig'.
endif.
when 'REP'.
i_query_desc-el_txt = 'Query'.
when 'VAR'.
i_query_desc-el_txt = 'Variable'.
when 'STR'.
i_query_desc-el_txt = 'Structure'.
when 'CKF'.
i_query_desc-el_txt = 'Calculated K/Fig'.
when 'FML'.
i_query_desc-el_txt = 'Formula'.
endcase.
i_query_desc-txtsh = rszelttxt-txtsh. "short text
i_query_desc-txtlg = rszelttxt-txtlg. "long text
i_query_desc-owner = rszcompdir-owner. "owner
append i_query_desc.
clear i_query_desc.
endloop. "@ long_ID
list results
sort i_query_desc by local deftp owner.
loop at i_query_desc.
write: / sy-vline,
i_query_desc-eltuid, sy-vline, "25 char generated ID
i_query_desc-compid , sy-vline, "technical name
i_query_desc-deftp , sy-vline, "element type
i_query_desc-el_txt, sy-vline, "element text
*write: / i_query_desc-txtsh , "short text
i_query_desc-txtlg(40) , sy-vline, "long text
i_query_desc-owner , sy-vline.
write: sy-uline .
endloop. "@ i_query_desc
hope this helps.

How to collect the deleted query in a transport request.

Hi Friends,
I have created a query and transported it to the Quality, the data content is all ok, except that i have not used the Project Naming conventions. Now i have a defect against my name for this. I have to copy the same query with the correct Naming convention and transport it.
My question is after copying the query with correct name i have to delete the old query (if not there would be 2 versions of the same query). How do i collect the deleted image of the query in a transport and send it to quality?.
I tried deleting a test query from Bex Designer, but this does not ask me for a transport. should i use RSZDELETE?. Not sure if it asks for a transport request when i delete the query.
Can someone pls tell me how to go about this?.
Thanks in advance.
BN

Hi BN,
I do agree that deleting directly in Quality and Prod is not good way and not recommeded.
I have not tried and deleted.But if the system is configured in such a way that if it doesnt ask for a request
then i feel you have no option.
If any object is deleted then you must have the deletion image collected into request at the same point when you are deleting.Because later when we go to transport connection we wont find the object itself.
What i think from your point as you said you have done earlier is you must have any open request regrding this query and when this query is deleted , the deletion image is also included in the same request.
So go to se03 and give your deleted query name and check all the requests.
Check in the requests when the deletion image is captured or not. we might be knowing that this is cpatured.
Regards
vamsi
Edited by: vamsi talluri on Nov 9, 2010 9:14 PM

Query regarding transport request

Hey guys,
I have a question regarding transport requests.
If only the report source code is included in the transport request, the text elements of the program will not be transported to the next box?
when you transprot the main program or the function pool, does it follow that all the changes in FM's under the function pool will be transported to the next box?
Thanks a lot!
Rgds,
Mark

Hello,
If you create transport request with just the report, text element will not be transported:
LIMU REPS <Program>
For text element, you need the following transport entry:
LIMU REPT <Program>
If you want to transport both, you can have the following entry:
R3TR PROG <Program>
If you have the following transport, all the components of function pool will be transported.
R3TR FUGR <Function Group>
Thanks,
Venu

Transport Request Number shown as Blank in Version Management

Hi Experts,
I am creating transport request for report programs using the function modules IW_C_CREATE_TRANSPORT_REQUEST and
TR_INSERT_NEW_COMM .Once created i am able to see the transport no in SE01 .But when i tried to make any changes in the program and save ,its asking for a new transport request.Also in version management the transport request is blank .
Please suggest me where i went wrong.
Regards,
Lakshman.

Hi
Just check if your report objects are getting linked to the Transport in se01.If not then it means that this FM only creates a TP# and not attaches that to Report Objects.
You then need to manually attach the Report object to this TP#.
Regards
Gaurav A

BI Transport Request Failure

Hi,
I have created a transport request to install business content- A SRM Report. The transport request failed. I am unable to understand whether the report has been installed properly or not. Can i re install the Query? Can i delete the transport request and create new one and try to assign the new transport request to the query while installing it newly? Please suggest me reagrding the same.
Thankyou.

Hi There,
Just check the log of errorneus Request.
Try to find out which element is missing.
then
Just Go to Se16 Table Name RSZELTDIR
in that mention the missing Object Namein ID field, Execute, you will get the Object description which needs to be transported first, create a new request add that missing object and then transport that Object with Grouping Option necessary.
and then again transport your previous request.
Regards,
Rajdeep Rane,

Transport request failed-inactive version of query element.

Similar Messages

Maybe you are looking for