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

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

  • 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

  • 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

    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

  • 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

  • Error while Releasing a transport request - DSO 0SD_O03: Active version

    Hi all,
    I am getting below error when I am trying to release a transport request.
    Object ODSO 0SD_O03: Active version differs from modified version.
    I activated DSO again,but I was not successful to correct the error.Please help me correcting this error.
    Regards,
    Bob

    check
    match and copy while installing the business content
    Match (X) or Copy
    If the SAP delivery version and the active version can be matched, a checkbox is displayed in this column.With the most important object types, the active version and the SAP delivery version can be matched.
    When a match is performed, particular properties of the object are compared in the A version and the D version. First it has to be decided whether these properties can be matched automatically or whether this has to be done manually.
    A match can be performed automatically for properties if you can be sure that the object is to be used in the same way as before it was transferred from Business Content.
    When performing matches manually you have to decide whether the characteristics of a property from the active version are to be retained, or whether the characteristics are to be transferred from the delivery version.
    The Match indicator is set as default in order to prevent the customer version being unintentionally overwritten. If the Content of the SAP delivery version is to be matched to the active version, you have to set the Installindicator separately.
    The active version is overwritten with the delivery version if
     the match indicator is not set and
     the install indicator is set.
    check following thread
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/102906a4-f13d-2e10-7199-ce316ff254b8?QuickLink=index&overridelayout=true
    Thanks and regards
    Kiran

  • We couldn't release any transport request!

    Hi experts,
    We could't release any transport request on DEV from today.
    We could do it until yesterday.
    We have never changed any settings.
    Except release, we can use SAP system, and
    we can import released transport request to QAS .
    Also I could tp addtobuffer on DEV.
    [Operation]
    SE10 -> select transport request -> click [release] button
    and, we can see the error message as below.
    Error Message *****************************************************
    Test call of transport control program (tp) ended with return code
    [Transport Log]
    We can see the log as below.
    ERROR: No connect due to DbSl Load Lib Failure
    ERROR: environment variable dbms_type is not set.
    ERROR: Connect to RDV failed (20090220140504).
    ERROR: Connect to RDV failed (20090220140740), failed to read table SVERS.
    [Our Action]
    1. Change Environment variable & Restart SAP (note 351586)
    2. replace tp & saptrans
    3. change parameter (note 175627)
    4. add full control to everyone on sap/trans
    5. see note 534765，98678，128126，592514，799058，879941，508140，610640
    Thank you in advance.
    BR,
    Toshi

    Hi,
    Thank you for your reply.
    I did r3trans -d, and the result is as belllow.
    F:\usr\sap\RDV\SYS\exe\run>r3trans -d
    This is r3trans version 6.13 (release 640 - 07.01.08 - 14:25:00).
    unicode enabled version
    2EETW000 sap_dext called with msgnr "2":
    2EETW000 -
    db call info -
    2EETW000 function:   db_ntab
    2EETW000 fcode:      NT_RDTDESCR
    2EETW000 tabname:    TADIR
    2EETW000 len (char): 5
    2EETW000 key:        TADIR
    2EETW000 retcode:    2
    r3trans finished (0012).
    Also I checked TP_DOMAIN.pfl, but it seems that there is no problem.
    But I found doubtful point.
    It is environmental variable, and now it is differnt from last friday.
    Example,  last friday , there was variable as bellow,
    but today I couldn't find them
    In the meantime , I will deal with them.
    dbms_type=MSS
    MSSQL_DBNAME=RDV
    MSSQL_SCHEMA=rdv
    MSSQL_SERVER=<hostname>\RDV
    Toshi

  • Error when releasing a transport

    Hello experts,
    I am getting an error when releasing a transport. The error message is telling me that
    Object DTPA DTP_009C8T81IIB6H4UFC7FQUVRFL was set to 'inactive'   
    The detailed error message isnt very helpful. The performance assistant gives the error message RSO 407.
    I found another thread,  scn.sap.com/thread/3428031
    The answer in this thread appears to be very close to a solution for me, I just need a little more information I think. As it says, I have looked in the table RSTRAN for the transformation that this DTP processes. There are three rows, with a different OBJVERS. A and M are both set to ACT, but OBJVERS = D is set to OBJSTAT = INA.
    I suspect that this is the problem with the releasing of my transport. Do you agree?
    If so, how do I go about getting this activated?
    Many thanks.

    Hi Simon,
    The D version will be always inactive as it indicate SAP Delivered version of the transformation.
    I will suggest just have a look at any existing transformation, you will find same status i.e D version INA also check last change it will be SAP also under content column you will find info for D version.
    I still say, just go ahead and release your transport by ignoring the message, it should work. You are all set to move your transport.
    Rest upto you.
    I have tried releasing transport by ignoring messages many times.....and worked all time
    Thank-You.
    Regards,
    VB

  • Releasing a Transport Request ends with error code 0012.

    Hi,
    We have a Development system and a Production System (both running on separate windows machine) but they are not connected in STMS. We perform transporting of Requests at o.s level and NOT through STMS.
    We are facing this new problem - We are trying to release a Transport Request in SE01 and it ends with error code 0012. The task inside the Request is released without any error. There is no Notes in SAP Marketplace for this.
    Test call of transport control program (tp) ended with return code 0012
    Message no. TK094
    Diagnosis
    Your transport request could not be exported, since all requirements were not fulfilled.
    Calling the transport control program tp
       "tp EXPCHK EFIK900025 pf=E:\usr\sap\trans\bin\TP_DOMAIN_EFI.PFL -Dtransdir=E:\usr\sa"
    which checks the export requirements, returned the following information:
    Return code from tp: 0012
    Error text from tp: ERROR: Buffer check failed.
    System Response
    Further processing is terminated.
    Procedure
    Check the following points:
    Feasibility of the transport control program tp
    Parameter settings in the transport profile
    Availability of the transport directory and the subdirectories (cofiles, data, log, sapnames, bin)
    Write authorization for the subdirectories
    Write authorization for the files of the subdirectories cofiles, data, log, sapnames
    Release the request again when the error has been removed
    Please help.
    Regards,
    Mohan.

    Hi Mohan,
    Nice to hear that that your problem is resolved.
    For Pamater CTC, please check the below links:
    Automatic transport between DEV clients ?
    http://sapsolutions.searchsap.com/kw;ExtendedTransportControl/content-sap.htm
    Regards,
    Hari Kishan

  • Error 12 when releasing a transport

    I am trying to release a transport, but get an error 12 "The request's target VBQ.500 is client dependant but the target system cannot handle that". VBQ.500 is a virtual system. Anyone have any suggestions for me to check out? I'm at a loss.
    Thanks,
    -- Jackie

    Hello Jackie
    I cannot tell you the reason for the error code. Somehow the CTS "believes" that the target system cannot handle clients and client-dependent objects.
    For the moment I think your main problem is to release your customizing request (or is it a workbench request containing client-dependent repository objects?). Try to change the target of your request. Perhaps the CTS can handle that. It might be necessary to adjust transport routes (transaction STMS) in order to get a "decent" target.
    Is your virtual system VBQ.500 a <b>consolidation system</b>? If not then try to change this (Note: this is a critical SAP basis activity).
    As soon as the request is released you can try to import it into your VBQ.500 system.
    Regards
      Uwe

  • Error when releasing a transportation order

    Good morning.
    I am trying to release a transportation order that contains a nonstandard table which has been added two fields, and the corresponding data elements and dominions of the new fields.
    When releasing the order, dumps an error and cancels the export.
    The status of the order now is "Initiated liberation".
    The error code is:
    "Error SQL 932 when accesing SPROXDAT: ORA-00932: inconsistent datatypes: expected %s got." And makes reference to data elements, but i think they are OK.
    Please,  ¿someone can help me?
    Thanks a lot.
    Regards.

    well the problem is very likeley that the table has enhancement options which allow only character and NUMC append fields.
    you most probably violated those preferences.

  • 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

  • Object locked after Release and Transport to QAS/PRD

    During an attempted recovery of our DEV system, a tranport request that had been previously released and transported to QAS/PRD was copied back into the DEV system, over-writing an open change request (and associated lock) on the program.
    As a result the object shows as 'Locked' in DEV, but the lock entry is on a 'Released' transport.
    I have reviewed tables E070 and E071, and as expected the entries for the program show that the transport was released. 
    Table TLOCK contains an entry for the program indicating that it is locked under the change request described above, that has already be released.
    I logged a message with SAP, and was directed to create a new change request and assign the program to that request.  While this does work, and allows me to make corrections and transport them, it does not assign a lock to the new transport, and does not clear the existing lock.
    The other comment in the message was that once a transport is released, the only other option is to 'hack the tables', but I am not sure I am ready to go that route.
    Has anyone ever encountered this situation, and if so, do you have any situations as to how to clear the lock entry ?
    Thanks in advance for any assistance you can provide.
    R. Runtz
    SAP Support, Government of Manitoba

    Hi Robert
    You can unlock objects using transaction SE03:
      SE03   > Requests/Tasks   > Unlock Objects (expert tool)
    Imre Takácsi-Nagy
    Senior Support Consultant II.
    SAP Global Support Center Austria
    Netweaver WEB Application Server ABAP / JAVA

Maybe you are looking for