Bex transport in SAP BW 3.1

Hello everybody,
how do you organize Bex transport in SAP BW?
In our installation, we find it necessary that some queries need to be designed in development system and tested before transport in production. We would like the person who's creating these queries to be able to create and release the transport for his query himself. With just one standard Bex transport this seems difficult to implement: In our constellation, the standard Bex transport can not be transported to production system, because it may contain test queries, which are not wanted in productive system at all and collects changes of different projects and persons, so it may contain objects that are still in test status, while others need to be transported to production system. Collecting into different requests is only possible if the concerned objects belong to different packages?
Collecting the needed objects in a transport request manually can't be done without releasing the Bex transport first because otherwise the objects are locked.
How do you organize Bex transports in your system landscape?
Thanks for any suggestions, Kathrin!

Hi Kathrin,
if you create a query in the development-system, the query will go to the Package $TMP, so no Transport is necessary. If you have a naming-convention, like <InfoProvder>_QU_nnnn or someting else for non-test Queries, it is easy to fetch them in the Transport Connection (Admin Workbench) and transport them in the production-system.
Hope this helps,
Regards
Frank

Similar Messages

Documentation on Bex Transports

Hi
Im looking for a good documentation on transports, especially for, Bex transports. Could any one please share any link or document with me?
Thanks a lot.
Regards
Ram.

Please search the forum...there are a lot of good discussion and steps provided for BEx transports, and also links to SAP documentation for the same.

What is the difference between Bex transportation and Normal Transportation

Hi experts,
I have doubt with Transporting queries , in this I've used the normal transport (truck icon) rather than Bex Transport. I would like to know which is the preferable one and what is the main difference between them.
Suggest me if I can go for normal Transportation rather than Ibex transport, as I've not tried Bex transportation before.
Give me some valuable inputs please.......
Regards
Kumar

Hi Kumar,
We have a Bex transport because we may make changes in the query very often and these changes will be automatically taken care by Bex transports.
Generally this is how it goes.
You will capture the queries by creating a transport request and immediately you will create a Bex transport request and you have to assign the previously created transport request number to this Bex transport request, so that everytime you make changes to the query will be taken care by the Bex transport.
You can even create a Bex transport request individually.
Hope this tip may be useful.
Assign points if you find useful
Thanks
Regards
Sam Mathew

Problem Running BEX report from SAP.

Hi All,
We are getting the below error message when we are executing BEX report from SAP.
"Analyzer requires version 140. The currently installed version is 066
Message no. RSR_LAUNCH_EXCEL107."
when i run the report for first time it is displaying correctly but, when i run it for second time (first one is already opened) then i get the above message.
Please let me know is there any setting or oss note related to this issue.
Thanks,
Shiva.

Hi,
Where is it happened? in Tx RRMXP, RRMX or when you execute Bex Analyzer?
Probe with this notes: 1086904, 1152929.
Regards.
Edited by: Conrado Linquet on May 11, 2009 9:55 PM

Transport layer SAP between development & quality

Should we have to use two transport layers ( SAP& ZDEV(created )) between the development & quality system as their consolidate route ?
Transport layer
SAP- Transport layer for SAP standard objects
ZDEV- Transport layer between Devlopment & quality systems
I assigned the consolidate route ZDEV between the Development & quality systems.Now ,How can I assign the transport layer SAP between the both systems as a consolidate route. Help me with your steps..

HI,
Z<SID> and SAP both are consolidation route as well as transport layer having different characteristic.
->A transport routes can be either a consolidation route or a delivery route. For a standard three-system
landscape, the transport routes are as follows:
-> A consolidation route connects the development system and the quality assurance system. This
transport layer is named Z<SID>, where <SID> is the system ID of the development system.
->A delivery route is created between the quality assurance system and the production system.
->In the development system, if changes are made to objects whose development class refers to the
(standard) transport layer corresponding to a consolidation route, these changes are recorded in
requests and transported to the quality assurance system and then to the production system.
If you change SAP objects, these changes are recorded in repairs, which can be transported in the
same way but using the consolidation route "SAP".
regards,
kaushal

Query transport-normal transport or BEx transport?

I could able to transport the backend objects but not sure about query transport. I would like to know difference between normal TRUCK transport and TRUCK-BEx transport in transport connection for queries. Can I use any or there are specific rules when to use what.

HI,
Bex transport truck mean you can create a global transport for you queries, when you transport your queries from dev to qa those queries wont be editable in development system unless you define this global transport. Everytime you make the changes in those queries these changes will be automatically gets updated in this global transport. Finally you dont have to retransport these changed queries, you have to simply release this global transport and the changes gets updated into quality server. The second transport truck is normal transport, and can be used to transport reports from dev to quality.
So bex transport is useful and you dont need to create a request after every change in report.
Hope this will help
regards,
ray

"Error #2032" while trying to import BEx query through SAP Netweaver BW connection in Dasboard

Hi Team,
BO server version: 4.1 SP3 Edge edition
Dasboard Version: 4.1 SP3
BI Version: NW 7.4 SP7 (ABAP only)
We are getting Error #2032 while trying to import BEx query through SAP
Netweaver BW connection in dasboard Xcelsius.
Please suggest to sovle this error.
Regards,
Vinay Shrimali

There are several notes about this error - please see http://service.sap.com/sap/support/notes/1856691
http://service.sap.com/sap/support/notes/1801130

How do i check who imported transport in SAP System

Can some one please tell me the table name where i can find who has imported the transport in SAP System

E070 table only shows the day the transport was imported it does not record the user who imported the transport. I was able to check TPLOG table and I found some transports getting recorded but not all of them. I am not sure what logic it uses to record the information.
I am not sure where else I need to look to get the person who imported the transport. Please any other suggestions

Transport.of SAP script form , printer def and device type is not enaugh

I transported the SAP script form , printer definition and device types of a thermal printer.
On original system the printout is ok but on target system not. What should I do?

Thank you for your fast answer
As the matther of fact I am technical person. I think Output type belongs to application. However the difference is visible in se71 ->Utilities->Printing test -> output device ->print preview.
As I wrote I transpored corresponding. SAP script form , printer def and device type

Abort Released BEx Transport

Hi all,
I made a mistake when I want to transport my ODS and infosource to production from Development by clicking the BEx transport. I realized that I made a mistake is when I try to open Query designer in development. it give me an error "BEx transport request '' is not available or not suitable". anybody know how to solve this problem without overwrite the query in production?
thank you in advance

Hi,
The query will not be overwritten till the released request is imported to prod. If imported it will overwrite with the changes. If released but not imported to prod you can collect the ODS and Infosource in a new request from transport connection (manual collection) and release the request. If the request is already imported to prod just collect the query in a new request and revert the changes and transport it again.
Check the possibilities.....

BEx transport prob

hi All,
I have one bex garbage collector already. but when ever i try to change query in BEx it gives me error message:
"BEx transport request not available or not suitable"
"use existing request"
i chked the component, package everything for that request....any clue?

solved my own

Question on how Bex transports work

I need help understanding how Bex transport works. We transport from Dev -> Q for testing -> Prod. I make a change to Calc1 in Qry1 and transport to Q in Transport1. During testing they decide Calc2 needs to be changed also. So I change Calc2 in Dev and collect all query elements in transport2 and transport to Q. Now it is ready to go to Prod. Do I have to send Transport1 and then Transport2 or will both changes be in Transport2? Can I only send Transport2?
When I collect all query elements for a transport does it collect everything that is there at the time or does it only pick up things that have changed?

Hi SJB,
Yes it will collected, all query elements will be collected.
You can also check in your transport request, Double click on request and see elements in it. Or from Transport connection also you can see all objects.
Hope it Helps
Srini

BEx Transport Requests '' ist not available or not suitable

hi, all,
I want to change a query, that has been transported back from Prod.System into TestSystem. Changes in the query aren't possible - the error message is
" BEx Transport Requests '' ist not available or not suitable ".
Now, there is a Standard BEx Transport Request and, in the RSA1 -> Transport Connection I see the query complete with that Transport Request.
What can the reason be? Any Idea?
Thanks a lot in advance.
neven

Ciao, Paolo,
thank you for the quick responce.
I did exactly as described :
The easiest thing to do is the following:
1) collect your query in transport connection
2) check if it is already assigned to a transport
2a)if assigned to a transport check if this is the standard bex transport. If so go to step 3, If not see if you should just tranport that request (or you can just go to step 3...but i wouldn't advise that)
3) unlock the standard bex request
4) now go back to transport connection and put the collected objects in a new request
5) release and transport your new request
It still doesn't help. I can't change the Query. The error-message is stil the same.
best regards
neven

Bex Transport request is not available or not suitable

Guys,
I need to make changes to query when I open it...it's saying Transport req is not available. So I have collected the query in a new transport in transport connection, but when I go back to the query its still giving the same error message. How do I resocve this error?
The transport it is showing in the query was deleted, so I cannot use the old transport.
Thanks,
Kris

Hello Kris,
What Mahesh said will solve your issue but once you transport that request you will again get the same error when you open any query in BEX. One way to get around this issue is for the first time create a request using the BEX transport button in transport connection and always keep this request open. If you want to transport a query that is assigned to this request just unlock this request using se03 and then collect your query and the corresponding objects in a new request in transport connection and transport the new request. This way atleast everytime you open a query you will not get the error.
Hope this helps.
Thanks

Bex Transport request is not available

Hi guys
I want to change the Bex query from query designer, when i go for change mode it didnu2019t allow me to change and throws error message "Bex transport request " is not available or not suitable" and in second line it gives "choose an existing request.
Can any one tell me how to change the Bex query with a transport request?
Gaurav

Hi,
You get this message if you have captured the query in a transport request and released or transported the request.
You can somply capture the query in a new request again from transport connection and then you will be able to edit the query.
even after capturing the query in the request is not allowing to edit then you need to try the option as explained by our friend above.
Regds,
Shashank

Bex transport in SAP BW 3.1

Similar Messages

Maybe you are looking for