cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Error while Transporting Bex query from Dev to Qa

Former Member
0 Likes
2,099

Hi Guys,

I have a really simple Bex query that i was trying to transport from the Dev environment to QA. The BEx query throws know errors when i check it, it does not have any restricted or calculated key figures, Like i said it is a simple query with some prompts, dimensions and key figures.

But for some reason, everytime i transport it, it transports with an error. Attaching the Screenshot. I am not able to figure out what is causing this error, so any help would be greatly appreciated. It keeps sayign error when activating a certain element, i tried deleting the element and it still doesnt work.

Thanks in advance!

Accepted Solutions (1)

Accepted Solutions (1)

abdullahqureshi
Contributor
0 Likes

Hi Siva,

You have to check that error query element in table RSZELTDIR at Quality system from there you come know what exactly the type of query element it is.

Also you have to ensure that your Data target (that query you doing transport) is activate or not in QA.

For collection of query from transport connection you can follow the guideline by experts.

Regards,

Abdullah

Former Member
0 Likes

Thanks for replying.

I cant even see the query in the Quality system after i transport it.

I checked the element in table RSZELTDIR.  This is all i see

Former Member
0 Likes

Hi,

Can you check if the query is captured in any Transport request in Quality box, I have faced similar issue once, then I deleted the Transport Request in quality and moved the Query from Dev box.

Thanks,

Jaya

Answers (2)

Answers (2)

sander_vanwilligen
Active Contributor
0 Likes

Hi,

Please expand the transport completely, to the most detailed level. Please make then a screenshot of the messages near to the error message. There must be a message with a hint to the root cause.

Thanks,

Sander

Former Member
0 Likes

hope this helps

ccc_ccc
Active Contributor
0 Likes

Hi Sivakumar,

Where did you got error while import or method execution.

Ex

if error occur at import, pleas share that error also.

Thank you,

Nanda

Former Member
0 Likes
KodandaPani_KV
Active Contributor
0 Likes

Hi,

you got  the return code - 8 means some thing wrong while collecting the TR.

please click on the green marked symbol.

then you will find the which object getting error and according to you need check each and every object.

Thanks,

Phani.

sander_vanwilligen
Active Contributor
0 Likes

Hi,

Unfortunately the expanded log does not provide any useful hint. The most likely cause is a missing dependent object.

I suggest to go to the Transport Connection and collect the BEx Query and all dependent object once again. Please make sure to select Only Necessary Objects and Collect Automatically. Then the List display is very convenient so that everything is grouped by object type.

Now select every object and check carefully for any local object (Package $TMP).

Let's hope that the new transport request can be imported successfully.

Best regards,

Sander

RamanKorrapati
Active Contributor
0 Likes

Hi,

RC-8 belongs issue with collected objects sequence. Some elemts are not active at dev system.TRy to run or regenrate your query from RSRT.

Save and activate your query at dev and recollectinto TR.

at Dev system lets try to run your report and see the output.

if it worked as expected way then again collect your bex query(all elements ckf,rkf,view erc..) into transport form RSa1-->transport connection.

Release and import to bwq.

Lets as suggested thru my first reply.

Thanks

RamanKorrapati
Active Contributor
0 Likes

Hi,

Before have you transported bex objects?

Are you sure about collected objects are stored into custom package?


Go to Bw, RSA1-->transport connection->object types-->bex query-->find your query.

Use grouping options as only necessary objects and drag bex query from middle pane to right pane.

At right side pane, expand bex query and select all components which are below.


under package see which package name was exist.

if it shows $tmp then change package to custom package by choosing pencil mark package icon.

Later collect into new bex transport.

Later you can check request any issues or not thru SE09/10, enter your transport request number and display it.

Menu request-->complete check-->inconsistency check.


Later release and import at Qua.


Thanks

Former Member
0 Likes

I already assigned a package when i collected the Query and its elements. Package is not @tmp.

The highlighted element is the element that is throwing the error. Idk what that element is, even if i manually delete the element in Dev before releasing the transport, it does not work as i am not able to see the BEx query in QWI.