Transport BEx Query

Hi
i am trying to transport queries from Dev to QA
In the BI transport workbench,
1) I collected my query and related objects,
2) clicked on the BEx Truck, added a package and assigned a request to it.
3) the package in the right collection window is still $TMP
4) do i need to again click on the transport object truck? if yes it ask me to enter the package again?
how to proceed...

Hi Ramesh,
When you are using the Transport Connection, to collect and transport queries and the necessary objects from Dev to QA, you need to use the Transport Objects button to specify the Package and request. Similar to a normal transport like the DSO or Cube. This request should then be released in the Dev system and imported into your QA system.
When you specify a package and request by clicking on the Transport Request for BEx button "BEx Truck" you are actually specifying a collector request for all queries changed in BEx. What this means is that once a query has been transported from one system to the other it is lock and any further changes need to be captured in a request. By default all changes made in BEx would then be saved to the request that you assigned to the Transport Request for BEx.
Hope this helps.
Demetrius

Similar Messages

What is the use of transporting BEx query to production from development ?

Hi !
if create a query by copying an existing query and make some modification in production and sent it to client..and client is happy as it satisfies all his requirement .
Then what is the use of creating Bex query in development and transport it in quality and then to production if we can create directly in production ?

Hi,
There is something called as SOX compliance..and three system landscape.
First of all you are not suppose to make changes to standard qeuries.
You can give it to the client a new copied query wirth required changes and it is very much accepted as well but how will it be tracked for future support.
Suppose there is a change in the underlying cube...this will affect all the queries and the new copied query which no one knows about will be affected too.How will you test it if its workinf fine with the new flow.
If you want to do the testing in production as well.... then you are not following SAP guidelines and may be you are violating the contract signed by you and your client.
Thanks
Ajeet

Transport BEx-Query backwards

Hello Experts,
I have the problem that I created a lot of complex Queries in production system. I need them now in developement system and dont want to create them again.
Is there a possibility to export a BEx Query backwards? Or to export (like a web template)?
I'm looking forward for your ideas.
Regards
Jesper

Hi Jesper,
Surely you can do the backward transport of not only queries but any transportable object.
The transport process remains same, just few of the things which you need to make sure that,
1) There exists a STMS path from production to development or quality to transport any request. This you can either check from STMS transaction or just check with your BASIS team.
2) Once the path is available then you need to check that you have sufficient authorization to create TR and collect all the objects in TR from RSA1 transport connection in production system.
Once your TR is created simply release it and let your basis team import it in development system.
Regards,
Durgesh.

Urgent: Bex query

Transported Bex query, now when execute this query it gives message that Initial RANGE-LOW for customer exit variable ABC corrected to #.
Any suggestions to fix this.
Points will be assigned.
Thanks
MK

Hi
I suggest you to transport the query newly
The reason is some query related modifications done in customer exit..or variable might not have captured properly
So transport them along with the query and error will not occur
Assign points if useful
Thanks
N Ganesh

BEx Query Transports (NW04s)

I transported a few queries using transport connection collection from DEV to QA.
<b>These were the first transports.</b>
After these transports queries that had not yet been transported are requesting a request when they are being saved in query designer:
<b>error msg:</b> BEx transport request '' is not available or not suitable; Choose an existing request.
To correct this problem I created a standard BEx request in transport connection. But now, when a query is saved entries are entered in the standard request, even though the query was never transported. (??????)
I thought the query would go to standard BEx request the first time it was changed after it was transported.
Also, I want to create multiple requests assigned to different packages:
How do I assign the BEx query elements to the packages for transport?

You get that message when you try to modify a Query that has been previously transported, hence the "transport not suitable" message. Therefore you need to assign a new transport to the query. You can do this in two ways, Sameer mentioned one of the methods.
Sameer's solution is risky, keeping a transport open (assigned) picks up any changes made in the BW environment. That means that if some other BW developer is modifying objects, they will be saved to your "assigned" transport. Therefore you must be careful and coordinate with your BW team if you are to use this method. You must also remember to "delete" the assigned transport to "close" it in Transport Connection.
What I recommend is to go to Transport Connection via RSA1, object types, then query elements. Collect the queries you wish to modify and create a new transport for them. Next, make your query changes. Make sure to exit all BW sessions (if you're on BW3.5) after you're done changing your query. Then recollect the query in transport connection to pick up the new changes you made (assign it to the original transport).

Xcelsius based on BEx query. Issue when transporting from DEV to PRD

Hi all,
I am facing an issue as described below:
I created dashboard based on bex query in Query Browser. Everything is working find in DEV. Then I transport the dashboards to PRD, I also use the override settings to point from BOD-BWD to BOP-BWP, my connection changed accordingly. Everything seems ok. One day when we stop the BOD system. Dashboards in BOP are not working. Then I start BOD, everything is ok then.
The issue I got:
Internal: BOP....
External: BOD.../XcelsiusWebServices.
Is there any chance that dashboard in BOP using the BOD xcelsius web service?
I have resolved this issue by:
- Open the dashboard in BOP, then in each of the query in Query Browser, I clicked edit and click next, next until end.
- Then re-save to BOP, then it is working
For your information, I used BEx query in Query Browser only, not use BIWS.
Dashboard 4.0 SP04
BW 7.3
Does anyone face this issue before? And how you resolved it? Please kindly share with me.
Thanks,
Quan Vo.

Hi Quan,
Found few points regarding this.Please check might help you.
Migration of Dashboards (using Query Panel) on BI 4.0 environment - Business Intelligence (BusinessObjects) - SCN Wiki
Regards,
Javed

Can't modify a Bex query, it is tied to a released transport

Hello BW expert,
I could not change a existing Bex query. It is always tied to a released transport.
I have tested I can create a new BEx query and transport it to QA without errors.
The issue is when I opened an existing query, it has a error.
Bex transport request xxxxx is not available or not suitable.
double click the errors, below is the details.
No request has been set up as the standard transport request for BEx objects.
The (set up) request 'DB2K901272' (for the package '' ) has already been released.
The (set up) request 'DB2K901272' (for the package '' ) is not of the type 'transportable change request'.
I have released transport 901272 before opening the query, I don’t know why this query is still tied to it.
I tried to create a new BEx transport (DB2K901277) and opened the query again, but an error is still there.
Third, I tried to collect all query elements for the query in the transport connection, and put them in a standard transport, then I opened the query, but it is still tied to the same released transport.
I never see an error like this before. Is there something we could change in the setting so the query is always in changeable mode?
Thanks in advance!
Jun

Hello Vinod,
I tried, still have the same issue.
I collect the query by query elment, select all the elements and the query in the transport connection, then click the the BEx transport. I see a Bex transport created, but no elements are included in the transport, it is a empty transport request. could this be the issue?
Thank you very much!
Jun

Transport or import bex query to test environment

hi gurus
is there a way I can move a bex query from production to my test environment?
I guess : RSA1- Transport - Export / Import, but i never used them...
regards

HI,
I am also facing the same issue.
: "Manually start the maintenance transaction for objects of type CWM Document"
@5C\QError@ SAP object 0CURRENCY () cannot be imported @35\QLong text exists@
SAP object 0CURRENCY () cannot be imported
Message no. RSOXML218
Diagnosis
You attempted to import SAP object 0CURRENCY of type into the system via the
XMI interface. However, you are not allowed to import SAP objects.
System Response
The object will be ignored during the import.
Note: It can be that the import is incomplete when the required SAP objects
are still not active in the system.
Procedure
Install the specified objects from BI Content. Only import the metadata
afterwards.
If any one resolved this issue , can you please let me know how to resolve it.
Regards,
Anil Kumar

How could be delete bex query name those have already transport in bw prd??

Hello Expert,
I would like to delet bex query technical name with description those have already transport in bw prd ,
Beacuse I have to enchanment same name of report. I did copied and save as different name of dev bex qurey in dev.
I would like to delete old report name and rename
so, how could be achieve
Regards
Wasem

Hi Wasem,
Confirm first your reports are transported to BW PRD,if transported successfully to BW PRD.
Then manually delete report by open that report in query designer by simple choose delete option from query menu.It will prompt to collect in a request.Keep in mind do not transport that request to BW PRD.Just delete that request in BW Dev system.
Regards,
Rajesh

Transport Error For Bex Query to BW Production

Dear Experts,
We are facing an issue during transport of a Bex report.
The RC 16 error has taken place. After I did google; I found this as below, but not the exact steps to solve this:
Return code (16) indicates import is cancelled.
Ex: RC 16 error
1. Import cancelled due to system down while importing.
2. Import cancelled due to user expires whileimporting
3. Import cancelled due to insufficient roles.
Would you please suggest me how to encounter this error, solve the error and successfully transport the Bex Query?
Please help.
Regards, Aparajit

Hi all,
The issue is resolved with Re transport.
The Query is in production now.
Thank you very miuch for your guidance Rama,
Ganesh and Nikhil
Regards- Aparajit

Bex Query Transportation Error

Hi Guru's
While i try to access bex query for transportation using transport connection>queryElements>Query, sap throws Dump Error.
Is any body came across with this pls help me for solution.
Asap.

Hi,
This happens whenever there is not a sufficient memory available for processing. This can happen with any activity in the system like data loading, deletion, creation of objects etc.
Please ask your basis team to make sure that there is sufficient memory (tablespace) available in the system.
This will solve the issue.
Regards,
Yogesh

How to transport a simple BEX query ?

Hi guys
We have a new BI system. And i am trying to transport a Query from DEV to QA. I believe transporting query is slightly different from transporting other BI Objects like cube DTP etc..
Can some one tell me how to do this? right now i goto the "Transport Connection" in RSA1 and try to find my query but i cant find my info provider in there, queries show under the info providers, and hence i cant collect my query.
Its a custom infoprovider. and starts with a "Z..."
Regards
Adnan

Hi Adnan,
Goto RSA1---> Transport Connection, after that on left hand side pane click on Object Type.
Once the list is displayed in middle pane, you have to expand "Query Element" tree and expand "Query" option and click on select object.
Give name of your query in search option and the query will be displayed. Select the query and click on transfer.
Now in the extreme right hand side area you will see the query , now you will have to select the main query and once you expand the tree you will see all the dependent objects, including your infoProviders.
If your infoProvider is already transported you don't need to select the check box. But for query elements I will recommand you to select all the objects.
And the final step is to click on "Bus", transport button and all the objects will be written to Transport Request.
Rest of the process is similar to general transport.
Regards,
Durgesh.

Structure copy in BEx query Designer?

I created structure in BEx Query Designer in BI PRD which is our BI production system.
I'd like to copy structure to BI DEV which is our BI development system.
Is is possible?
If you have any solution, tell me about that.
Thanks.

Hi
If you want the object which is there in PRD to DEV system means, the only way is to do transportation. but to do reverse transportation, you should have STMS connection from your PRD to DEV system.
The better way is to create the structure again in DEV system.
If you want to go with reverse transportation, consult your basis person.
Regards,
Venkatesh

BEX Query Views - Reqd in PRD but need to create in Dev - Data Issues

Hello Bw Gurus
BI 7.0 ECC 4.7
We have a BEx Query in BI production which uses a work centre hierarchy. The user wants to create query views on this query to use in BI production.
Our normal transport procedure of a new development object would be BI DEV - QA - PRD
However the DEV environment does not have all the work centres and the data of PRD. So if the query view needs to be created in DEV then we could not set up the view correctly as there is not the workcenters or the data in DEV.
Hopefully that makes sense?
Apart from allowing Query Views to be created in BI PRD directly is there any solution?
Best,
Steve Jones

If you need exact char values for workcenter to create your views you can quickly create the master data (just the values you want) in Dev and use them to create the views...

RC 8 error while transporting the query from Dev to Qa - Element missing

Hi All,
I have made a multiprovider by copying one existing one.
I have copies one of the Bex queries using RSZC from the source to Target MP.
While transporting the query from Dev to QA i have got the following error. (I have already moved the Multi Prov in a previous TR)
Has anyone seen similar types before. Any inputs will be highly appreciated.
Start of the after-import method RS_ELEM_AFTER_IMPORT for object type(s) ELEM (Activation Mode)
Error when activating element 4LUSZK561QN74UDBJ7BPU9GFM
Element 4LUSZJXHIS1HM7TVDD9DK7HPU is missing in version M
End of after import methode RS_ELEM_AFTER_IMPORT (Activation Mode) - runtime: 00:00:06
Start of the after-import method RS_ELEM_AFTER_IMPORT for object type(s) ELEM (Delete Mode)
End of after import methode RS_ELEM_AFTER_IMPORT (Delete Mode) - runtime: 00:00:14
Errors occurred during post-handling RS_AFTER_IMPORT for ELEM L
RS_AFTER_IMPORT belongs to package RS
The errors affect the following components:
   BW-WHM (Warehouse Management)
Post-import method RS_AFTER_IMPORT completed for ELEM L, date and time: 20110517070045
Post-import methods of change/transport request BDAK959603 completed
     Start of subsequent processing ... 20110517070025
     End of subsequent processing... 20110517070045
Kind regards,

Hi Jith,
First of all try to consolidate all your objects in a single TR and then move to Q from D.
In this case check for the list of objects that you have in your TRs. If TR 3 have all the Objects that were in TR1, TR2, then transporting TR3 alone will work.
Also, you can find the information related to the elements that were missed in your TR1,TR2 by following process.
1. Go to your transport Logs and then to the entries marked as Error.
2. There you will find the Query Element Ids, copy them
3. Now, go to Table(Se16) RSZELTDIR, there enter those query elements.
Now, you can able to find the elements that you have missed in your TRs. Hope this helps you.

Transport BEx Query

Similar Messages

Maybe you are looking for