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

Similar Messages

  • 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

  • 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

  • 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

  • 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.

  • 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.....

  • 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

  • Diff Bet'n Bex transport vs transport

    Hi guys,
    can some1 tell me the difference betn Bex transport and
    the ordinary transport for queries,Am i missing something here.
    i typically save the query when i modify one without using transport connection, i work on change requests. thanks,
    your help will be greatly appreciated

    Hi,
    Please refer the links,
    Transport.
    Once more about BEx transport request
    Bex transports: Package
    Regards,
    Hema.
    Reward points if it is useful.

  • BEx Transport Request is not available or not sitable

    Hi,
    When i try to install some queries from Business Content in the BW DEV box, the error was :
    <b>BEx Transport Request is not available or not sitable</b>
    Please let me know what has to be done in order to get out of this error
    Thanks & Regards,
    Kishore

    Hi Ken,
    Thanks for responding to my problem.
    You are right. I am installing from business content queries that have never been installed before.
    so when i am installing the queries from business content the error was :
    BEx transport request is not suitable or not available.
    How to proceed now ?
    Please give reply ASAP....
    Thanks & Regards,
    Kishore

  • 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

  • BEx transports

    Hi,
    I have created a Bex Transport and I know how to transport the changes. But just want to make sure, what is the diff between two truck symbols
    in the transport connection when we collect the objects. It looks like all my changes are already captured in my change request which I created
    using the Create Transport requests for Bex, now do I need to collect the query and Query elements in another request by clicking the transport objects
    Or just relesing the one I already have will update the changes in Porduction ? Please advice.
    I know that once I release my request, I need assign new one to capture all bex changes...thanks
    Sam

    Thanks Srinivas, yes it has already collected all my changes. So I'm wondering if just releasing this req will take care of the updates ?  Release the request it will transport all the changes to target system
    Do I need to collect the query in new request or not required ?.... Not required
    also once I release this requeste I need to create new one right ,  Yes. Create new for future changes if any, they will be saved in this new req
    so that all the bex changes will be captured...But I'm wondering what if some one dont want to import their changes in to production...Please advice. .. One person has to take incharge for all these things... he will co-ordinate all the people and will make sure which query to be transported! If there are too many people doing changes in the queries... better not to create Bex transport request.... assign your query modifications to one normal request and tranport to avoid conflicts

  • Personalization in BEx: transport activation to production ?

    Hi,
    on our development system (SAP BW 3.1) we have activated the "personalization in bex" via "BW Customizing - Implementation Guide - Business Information Warehouse - Reporting-relevant Settings - General Reporting Settings Activate Personalization in BEx".
    Is there a possibility to transport the activation to  consolidation/production system.
    Thanks for your help.

    Locking the users is the primary step. This is done so that while transporting the changes there are not entries made.
    If there are entries made, there is every chance that you will loose that data as your Data source has undergone a structural change.
    Users have to be locked. Its a must.
    You can minimize your downtime if you are not filling the Setup tables for History Data.
    Or if you are filling the Setups for history data, then you will have to plan it out in such a way that it requires minimum time.
    Users need not be locked if the change is not affecting any Data Source (Live or New). But in your case, there is a change to the DS. So, please Lock the users before transporting.
    Regards
    Vishal

Maybe you are looking for