Transport Lock by old transport request

Hi All,
My transport to prod has been lock by an old request. Do anyone know how i could get raid of this error.
Regards J

Take Basis help and cancel the job for request which is locked
Edited by: Srinivas on Sep 9, 2010 3:09 PM

Similar Messages

  • Unable to delete Transport Request which contain locked objects

    Hi all,
    I need to delete  some unusable transport requests but as they contain locked objects, it's not possible to delete them. Release operation is just allowed. After releasing these transport requests, I can not find them any more in queue. Please help to find these  transport requests which are released and also provide a solution to delete instead of releasing them.
    Thanks in advance,
    Sanaz.

    Hi,
    Thank you for the reply.
    1. What do you mean by transport request , Shipment Request, Shipment Order or Tour.
    A. I mean requests which can be transported between SAP Systems using TMS (Transport Management System).
    2. What are the objects which has been locked and due to that you are facing this problem.
    A. There are diffrent object types. For examle some customizing have booen done or SAP Note correction has been implemented, ... Therefore some objects have been locked due to these operations
    3. Let's say if it's an freight Unit, then Pls confirm that System dump / error is not the cause for this.
    A. I have no idea about "Freight Unit".
    Thanks,
    Sanaz.

  • How to find out the transport request that a report is locked to?

    Hello Experts,
    I have to transport a report to production system.
    The report has already been assigned to a transport request.
    How do I find as to which transport request is the particular report assigned to.
    Any place where I can check for the locks on a report ?
    Any advice is very much helpful...

    Hello Venkat,
    Thanks for the prompt reply.
    Actually i had tried it. but unfortunately, NO request number is shown. The Only nessage i'm getting is
    " Source systems can not be transported."
    The report is opening in RRMX in change mode.
    This implies 2 things,
    1. The report is already assigned to a transport request. OR
    2. Its assigned to $temp.
    But if the report is stored as $temp, while tranporting in transport connection, it should ask for a transport request and also ask for the development class. Which is not happening
    Any other places to look for ?????

  • The correct way to delete old transport request record ?

    Dear all,
    We want to delete old transport request record before 2008 (two years before) of our system.
    We learn that we should delete the records in the below two path:
    /usr/sap/trans/data
    /usr/sap/trans/cofiles
    Our target is that we will not see the old record after deleting in our PRD system.
    Normally, we see the transport request record in system by this way:
    STMS -->  import overview --> PRD --> Import Queue   system PRD --> Import history
    Our question is do we need to restart our system after delete the record to refresh the Import history?
    We have not delete the record now.
    Any experienced or expert, please kindly give advice.
    Regards,
    Allen

    Hello Allen,
    there are some notes and documentations for this process. Deleting the files from /cofiles and /data will not erase the request from the import history, as you already know.
    You should follow note #41732 to have the requests/data completely deleted from your system. There is a lot of complementary reading in notes #7224, #556734, #189841, etc.
    Note that you can remove the request from the import queue, import history, data and cofiles subdirectory, but still have it on the <SID> buffer (located in  /usr/sap/trans/buffer/<SID>). If this happens to you, please save a copy of the buffer file <SID>, then create a new, blank file named <SID> at a time when the import queue is empty (VERY IMPORTANT). Or, alternatively, please excute the tp cleanbuffer FIL command (which will erase the requests that are not found in /data and /cofiles directories).
    --> Please test this first on a test system, not directly on a productive environment.
    This should be enough to delete old transport requests on your system.
    Best regards,
    Tomas Black

  • Transport Request Locks on release!!

    Hello there,
    I am facing one problem; When I create a transport request of a smart form and try releasing it, the request gets locked, thus failing the release.
    I unlock the request via transport organizer tool (SE03), but again when I try to release the request, locking repeats.
    Any solutions??
    Thanks,
    Sumit

    Hi,
    Plz. check client settings via scc4.
    And check the owner of that request also via SE01.
    Plz. let us know, are u facing this lock issue, only for this smart form only or for all other requests also??
    Note: Points will always encourage me to reply!!

  • Transport overwrites original - although locked in transport request

    Dear all,
    we have a very special system landscape and therefore a very special transport problem.
    An include in the original system was overwritten by a transport although it was locked in a transport request.
    To explain the circumstances:
    We develop and support several releases of a pre-configured SAP Template for BW 3.5 and ERP 2004. After launching a new release we build up new systems as support stream for this release.
    For example BW development system for release 3.1 was TBD, after launching of release 3.1, we copied TBD to TBE. Thus, TBE is the support system for release 3.1 and TBD becomes the development system for the next release 4.0.
    Normally, a correction in release 3.1 (TBE) has to be included in 4.0 (TBD), too. Thus, all support systems are included in one transport landscape.
    It happened that a developer made a correction in an include in TBE and transported it to TBD. Unfortunately, another developer had enhanced this include in TBD and didn’t release the transport. So this changes were overwritten with the import from TBE although it was locked in a transport.
    I investigated this case and found out, that it could be overwritten because TBD is the original system of this include and therefore it has no repair flag when it’s locked in a transport which protects it against overwriting.
    We have to import the transport with the option “Overwrite originals” because in most cases a correction has to be imported in the original system.
    Do you have any suggestions how we can avoid this happening?
    Is there a possibility so set the repair flag in TBD manually?
    Thanks in advance for your help.
    Regards,
    Karin.

    Hi Max
    I tried this already but it doesn't work.
    Following system message occurred:
    Cannot change task type
    Message no. TR857
    Diagnosis
    You can only change the request type if this is permitted by the type of objects in the request.
    The requirement is not met in this case.
    Karin.

  • CHaRM-Handling old transport request before CHARM was activated.

    Hi All,
    Recently i just activated CHARM in solman-SM1 for new a project implementation. This CHARM was setup in in such a way that it tie to one of the local IMG project EPROJ in developmemnt-DEV.  Now i have one concern and that is those transport requests where created before i activated CHARM.
    These old transport requests were crerated directly in DEV without project assigned. Therefore, we tried to assign IMG project EPROJ (the same IMG project setup in CHARM) into those old transport request manually.
    Problem : When i tried to perform released step in CHARM tasklist it says that "No transport request found"
    Question : How do i make CHARM to pickup those old transport requests?
    Really appreciate your feedback as there are a lots of old transport request which needed.
    Thank you.

    Hi,
    If you use Change Request Management, you should always use Change Request Management means to create transport requests; that is, create transport requests in a change transaction or in the task list.
    Manually registered transport requests can be assigned to a task list only, not to a change transaction.  If you use change transactions ,,,,the system does not take into account transport requests that you added manually.
    This note is what you want
    Note 1150426 - Registering transport requests in ChaRM
    Hope it solve ur problem completely.
    Regards
    Prakhar

  • Remove unnecessary transport requests which are 7 days old

    Hi All,
    I would like to delete all the un-necessary transport requests which are displayed in STMS which are more than 7 days old.
    But, the import log should be available whenever i need to verify.
    Is there any script which can do this?
    Thanks
    Vijay

    Hi,
    I do have a similiar situation, I would like to write a script to remove transports that have successfully transported and are over 7 days old.   In STMS currently we have a list of every transport that has ever been sent and there is no need.  Note that via SE10 we still want to see transport history even for old transports just remove the old ones from STMS. Hopefully I feel some script does this job and no idea on this scripts.
    Can someone throw light on this and help me out.
    Thanks & Regards,
    Bharadwaj.

  • How to delete unreleased transport request where the objects are locked

    Hi Experts,
      I was created a transport request, but I am facing some probelms with taht request, now I want to delete transport request. I tried to delete them in SE10, I am getting message that the objects are locked. Please tell me how to delete unreleased transport requests where the objects belong to this transport request are locked.

    Hi,
    First go to transaction se03 Choose "Unlock Objects (Expert Tool)" option under "Requests/Tasks" and unlock your task,
    Than go to se10 and delete what you want.
    I hope it helps.
    Bulent

  • Old transport request for sap script (form)

    Hi,
    I want to find the old transport request for the sapscript(form). Just now it has been over written by the latest CTR. So i need to transport the old one.
    How to find out the old transport request.
    Thanks,

    Try giving the script name in OBJ_NAME field in table E071 and then execute and it will give you a list of all transports. You can sort it in descending and see the order of transports.
    Thanks,
    Srinivas

  • Function module to lock mulitple objects in a single transport request.

    Hello,
    I have a query regarding one of the requirments in my project. The requirment goes like this:
    ' On executing a transaciton lets say the user gets a list of data elements then the user selects say five data elemetns ( check boxes are there in the list display showing data elements ) and he sets that the documentations of each element as 'Self - Expalanatory' then the requirement is that all these data elements must get locked in a single transport request.
    Is there a standarad API which takes object ID , Object type as input in form of table and checks if there are any existing transports in which the data element is locked if yes locks it under it, if not creates a new one and locks all the other objects in that request.
    Atleast a FM which takes a table of object ids as input and locks them under a single transport request will also be helpful.
    Some place where I can look for it.
    Warm Regards,
    Naveen M

    If the objects are available in an existing request then they will be already locked.
    If they are not available in request you can assign all of them in one request using
    SE03 transaction.
    In SE03 transaction,select include objects in request and execute.
    there click selected objects radiobutton, give your objects and execute.
    save them in a request and they will be locked and you can transport them later.

  • How to create locked Transport Request

    Hi All,
    I have a requirement where I want to create a transport request that cannot be released to any other system i.e, locked transport. I need this transport to create a package to put my works related to a local tool that I want to create in the development server. This is an internal tool and need not be released to any other system. Please help in creating this transport.
    Any help in this will be highly appreciated and rewarded.
    Thanks in advance.
    With Regards,
    Rocky

    Instead of creating some "locked transport request" you can create your developments, that you don't want to be transported, as "local objects" (package / development class: $TMP). You decide about this when the system asks you for the assignment to the development class (package).
    In this case the system will not put these objects to any transport request - they will stay on your development system.
    regards

  • Object already locked under transport request by another user

    Hi Experts,
    While trying to generate transport request for my developments, the request is getting generated as a sub task under previously created request.The program has been earlier modified by another user and that request was not released.Can I create my own request number without creating it as a sub request? I cannot release or delete earlier requests.
    Regards,
    Sam

    This restriction is there for a reason. Somebody has already applied changes to the object you are changing now, so there would be a logical conflict if you would be able to lock it again under a different request. Before you release or delete anything, make sure you understand all changes done and if they can be moved together to subsequent systems. Speak to the "other user" if unsure.
    Thomas

  • Locking the Transport Request

    Dear Guru
    I have three system landscape. I would like to lock/protect all those request which had been transported or mark as "critical". So that no one can transport request by mistake,
    Regards
    Vimal

    Hi
    I am not sure of locking an individual request. But you can lock the import Queue itself if required.
    To do this, go to STMS->click on import (truck)-> choos the system whose import queue needs to be locked-> Either double click on the system or click on display -> now u can see a lock symbol-> click on that.
    It will lock the import queue which means that no one can import any transport request into that SYSTEM.
    To unlock, follow the same procedure. Instead of lock symbol u will see UNLOCK symbol.
    PS: PLease note that u need to lock the import queue onle WHEN u are sure that u dont need to import any requests

  • How to assign transport request for Dynamic selection in SE36

    Hi Friends,
    Please guide me how to transport or assign a request for the changes made in BRF selecion view.
    I have assigned and added BKPF-XREF1_HD field for FB03 transaction. Its working fine as per user requirement.
    I am facing probelm to assing a transport request for that. I didn't find any transport menu in se36.
    So please provide me how to assign a TR which need to import into Production client.
    If I have to assign or create a program (standard), then please provide me the program name.
    Please reply.
    Thanks & Regards
    Sankar.
    Edited by: sankar babu on Jul 29, 2010 12:27 PM

    Moderator message - Cross post locked
    Total Questions:  283 (131 unresolved)
    Please also close your old posts and assign po1nts to helpful answers.
    Rob
    Edited by: Rob Burbank on Jul 29, 2010 9:50 AM

  • ABAP Query Transport request related

    Hi,
    I have created a Abap query,
    1) User group
    2)Infoset
    3) Query
    But when i transport the request in to Quality, I can see only Infoset, not able to see User group and query which i created in the
    Development
    Please suggest, is this std behaviour or is anything missed
    Rgds,
    Jai

    Thanks to all,
    I just created TR with new package for user group and included ifoset and query in the same TR
    and imported, issue is resolved
    But my question is,where we can utilize below help material, I have spent much time to understand below given explaination and finally left without any conclusion
    Short text
    SAP Query: Transport tool
    Description
    The report RSAQR3TR handles all tasks concerning the transport of queries, InfoSets and user groups.
    General information
    Queries, InfoSets and user groups are stored in the table AQDB. This table is client-specific. For the transport of queries, InfoSets and user groups, there is a special client-independent transport table called TAQTS. You can carry out transports either
    ·     from a client (source client) of an SAP system to another client (target client) in the same SAP system or
    ·     from a client (source client) of an SAP system (source system) to a client (target client) in another SAP system (target system).
    In both cases, you have to perform similar actions.
    The objects to be transported must first be copied from the source client using an export from the table AQDB into the transport table TAQTS. At the same time, a transport request is created for the transport system that includes all entries created by the export from table TATQS (transport dataset). The name of this transport request conforms to the transport system naming conventions (sysKnnnnnn) and is included in the export log. The transport dataset is stored in the table TAQTS under a key which matches the name of the transport request.
    If you are transporting within one SAP system (from one client to another), you can import the transport dataset from the target client. The name of the transport request to use for this purpose is that specified during the export, since it should match the key of the transport dataset in the table TAQTS. With this import, the transport dataset is read from the transport table TAQTS and inserted into the table AQDB, where extensive checks ensure that there are no inconsistent statuses in the table AQDB.
    If you are transporting from one SAP system to another, you must first use the transport system to release and export the transport request generated by the export. This transports the transport dataset from the transport table TAQTS into the target system. Then, you can import from the target client of the target system, as described above.
    The transport datasets generated by exports in the transport table TAQTS are not deleted after successful import unless this is explicitly requested. Therefore, you can import a transport dataset several times (when copying a functional area to several different clients, for example).
    This report handles exports (generation of transport datasets), imports (reading of transport datasets) as well as the management (display and deletion) of transport datasets.
    As transport action, you must specify one of the values EXPO (export), IMPO (import), SHOW (display transport dataset) or DELE (delete transport dataset).
    Transport action EXPO (exports)
    If you select the 'Test only' parameter when exporting (no blank characters), the system determines only those queries, InfoSets and user groups that would be selected according to the selections for transport described below and generates an appropriate log. A transport dataset is not generated in the table TAQTS. This allows you to check whether a selection really includes the queries, InfoSets and user groups to be transported.
    With exports, there are four different options for selecting objects (user groups, InfoSets, queries) to be transported. These are 'Transport of user groups', 'Transport of InfoSets', 'Transport of InfoSets and queries' and 'Transport of queries'. You must choose exactly one of these transport types.
    In each case, you can also define an import option depending on the transport type. This allows you to determine how the transport dataset is inserted in the table AQDB of the target client during a later import.
    The import options, each of which has an abbreviated syntax,
    are as follows:
    REPLACE  or R
    MERGE    or M
    GROUP=ug or G=ug    (ug = name of a user group)
    UNASSIGN or U
    If you use the transport type 'Transport of user groups', all user groups are transported according to the select option 'user groups' and the selected import option. The import options REPLACE and MERGE are allowed.
    If you use the transport type 'Transport of InfoSets', all InfoSets are transported according to the select option 'InfoSet' and the selected import option. The import options REPLACE, MERGE, GROUP=ug and UNASSIGN are allowed.
    If you select the transport type 'Transport of InfoSets and queries', all InfoSets are transported according to the select option 'InfoSets' and the selected import option. The import options REPLACE and MERGE are allowed. Also, all queries are transported for each functional area selected, according to the select option 'queries'. In this case, the user groups of the queries are irrelevant and only the import option REPLACE is allowed.
    This transport type allows you to transport a modified InfoSet and all the associated queries.
    For the transport type 'Transport of queries', all queries are transported according to the select option 'User groups' and the select option 'Queries' as well as the selected import option. The import options REPLACE and GROUP=ug are allowed.
    The export log displays which user groups, which InfoSets and which queries are transported, as well as the import options used.
    Transporting a user group
    Transporting a user group means transporting all members of the group from the source client. However, the InfoSet assignment to the user group in the source client is NOT transported.
    The import option REPLACE first deletes all members of the group in the target client and then enters the members from the source client.
    The import option MERGE leaves all members of the group assigned in the target client and adds the members of the group from the source client.
    Entering a new member in a user group in the target client is possible only if a user master record exists.
    In the target client, the assignment of InfoSets to this user group remains.
    Transporting an InfoSet
    Transporting an InfoSet means transporting the InfoSet and the InfoSet assignment to user groups in the source client.
    Importing an InfoSet is possible only if the same logical database exists in the target client. Extensive checking is also performed to ensure that there are no inconsistencies between the InfoSet and the logical database.
    The import option REPLACE first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries dependent on the InfoSet. The InfoSet is then transported to the target client and the assignment of the InfoSet to user groups is copied from the source client, if user groups also exist in the target client.
    The import option GROUP=ug first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries referring to the InfoSet. The InfoSet is then transported to the target client and assigned to the user group ug of the target client, if such a user group exists.
    The import option MERGE leaves the assignment of the InfoSet to user groups in the target client and transports it to the target client. It then copies the assignment of the InfoSet to user groups from the source client if user groups also exist in the target client.
    The import option UNASSIGN first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries referring to the InfoSet. The InfoSet is then transported to the target client. No assignment of the InfoSet to user groups is performed.
    Transporting a query
    Transporting a query means only the query itself is transported.
    Importing a query is possible only if a corresponding user group (see below) and a corresponding InfoSet exist in the target client and if the InfoSet is assigned to the user group. To demonstrate the effect of the import options, suppose that the query has the name QU and belongs to the user group BQ in the source client.
    The import option REPLACE overwrites the query QU of the user group BQ in the target client if the user group exists.
    The import option GROUP=ug overwrites the query QU of the user group UG in the target client if the user group exists. In this case, the query is explicitly assigned to a user group in the target client. This target user group may be differnet from the user group in the source client.
    Transport action IMPO (imports)
    If you choose the 'Test only' parameter with imports, only a test import is performed. This means that the system performs checks as for a real import and generates an import log. The import log contains information on the locks that have to be set. With a test import, you can check whether a transport dataset can be imported without any problem and which changes it would make in the table AQDB of the target client. A test import itself never makes changes in the table AQDB of the target client.
    All transport datasets are imported according to the select option 'transport request'. In this case, the system outputs a detailed log of all checks carried out and all changes made in the table AQDB.
    If you select the parameter 'Delete after successful import', the transport dataset in the table TAQTS is deleted after the import of each transport dataset if no errors occur during the import.
    Transport action SHOW (display)
    All transport datasets included in the transport table TAQTS are output with name (also the name of the transport request) and contents in the form of an overview.
    Transport action DELE (delete)
    All transport datasets are deleted according to the select option 'transport request'. To avoid unintentional deletion, the select option 'transport request' must contain values, meaning that the transport action DELE is not performed if this select option is empty.
    Transport of ABAP Query
    I am involved in this upgrade project to 4.7 
    The users are not able to find any reports (in QA System) which were there before the upgrade in SQ01. But they can see them in production which is not yet upgraded. They want me to copy all the reports to the QA system now....I dont have any idea how to do that. 
    I remember a similar problem upgrading to 4.6C from 4.5B ...... 
    Take a look at OOS note 672784. 
    You can transport queries between systems in SQ02 (hit the lorry button) or run program RSAQR3TR. 
    You download the infosets, queries etc into a file and load them into whichever system you wish.
    Just wanted to share my experience of transporting queries:
    I needed to move a user group, 2 infosets and 3 queries from a 4.6 system to a 4.7 system. 
    When I tried doing this via the SQ* transactions I did not get the import/export option, so instead ran RSAQR3TR. 
    Step 1. Run RSAQR3TR in 'old' system. Select EXPORT and specify the objects to be transported. 
    (System includes these in an automatically created transport request) 
    Step 2. Release this transport and request it be transported to 'new' system. 
    (This results in the entries being populated in transport table AQTDB in 'new' system). 
    Step 3. Run RSAQR3TR in 'new' system. Select IMPORT and tick the Overwrite checkbox. Specify the transport number in the field labelled 'dataset with imports'. 
    (RSAQR3TR gives the message that stuff has been imported OK). 
    Step 4. In my example I still couldn't find the queries, so ran RSAQR3TR one more time, this time specifying 'Copy Standard Area -> Global Area'. 
    (Now my queries etc were available in new system). 
    Perhaps there are better ways, but after 1.5 days of struggling I was glad to get this far.  
    regards,
    Jai

Maybe you are looking for