Released transport not present in QA Worklist

Hello,
We have a transport that is "stuck" betwen our DEV and QAS system. The transport has been released, and it is visible in the QAS system import queue in status "waiting for QA approval", but it is not present in the QA Worklist, and cannot be approved. That makes it impossible for us to transport it furhter.
Has anyone come accrosss a similar problem (and solved it)?
Thanks,
A.

Hi
First check whether that request has been created as "Local Change request"...if that is the case you cant see the request in import queue of QAS or PRD.
Secondly, if the request has a target system ( check from SE01 in DEV system), check if you have datafiles and cofiles for that request  in usr/sap/trans/data urs/sap/trans/cofiles directory from Operating system level
If everything is fine, try to forward the request from DEV system import queue or add the request in the import queue of QAS system manually

Similar Messages

  • Released transports not showing in queue

    We released many transports a few weeks ago and ended up changing our transport routes and target groups.  Now, those transports are not showing up in queue.  Is there a way to make those transports appear in the queue again in the sequence they were released?

    Hi Mary Jane,
    Can you tell us a bit more? So this is a brand-new two-system landscape? Is the /usr/sap/trans folder on your DEV system? Is your DEV system the transport domain controller? Also, I'm a little confused by your statement about being able to see the transports from SE10 in the target system (i.e., PRD). Normally this would only be the case in the source system, i.e. DEV. From PRD I would only expect to be able to see transports via STMS, and then only those that have been released.
    In STMS, go into Transport Routes (Shift+F7). You should be able to see both your DEV and PRD system there, and neither of them should show up as Single Systems. Instead, they should show up under Transport Routes under either or both the SAP standard transport layer or a ZDEV transport layer. It should look something like this:
    DOMAIN_DEV
    --Configuration Status
    ----DEV (or PRD, or both, depending which you're logged into, with a green light)
    --Transport Routes
    ----DEV System
    ------ZDEV Transport layer
    --------PRD System
    ------SAP Transport layer
    --------PRD System
    You might instead see this in a graphical view; you can toggle this with Extras... User Settings. I like the Hierarchical List Editor better, but I think the Graphical Editor is the default.
    If you don't see something like this, but instead DEV and/or PRD as Single Systems, this is probably the issue. In this case, choose Configuration... Standard Configuration... Development and Production System. I think it will give you a choice to distribute and activate immediately on all systems in the group.
    Regards,
    Matt

  • Transport not Release in QA

    Hi,
    I am Angeline, I having problem in BI Transport Release issue, under windows 2003 server, BI 7.0,  when I release Transport in DEV system, some objects have been released to QA, but when I look at in QA system thats does't exist there...
    is that anyone tell me step by step procedure to checking... transport...
    Thanks a lot in Advanced

    Hi Angeline,
    Releasing transport will not make the objects available in the next system you have to import the transport request in the QA system for the objects to be available.
    STEPS
    1- Create transportable tranport request .local request will be released but will not be transported to the next system.
    2- release the request in the Development system and check the log for the success of the transport.
    3- login to the next system and execute tcode stms_import you can see the released transport request in the quality system queue.select the request and import check the log for success.
    4 - then check for the objects.
    Regards
    Ashok Dalai

  • Transports not automatically released SDMJ

    Hi-
    I am at the step where I confirm a successful test in my charm scenario. According to the SAP process for normal corrections (sdmj), at this point the status turns to Consolidated and the original transport request gets released automatically. The transport is not being released.
    Any thoughts?

    There is one possible reason.. check your all transport of copies has been imported or not. . Because once you select "Confirm successful teat" first system change status to "Consolidated" then after trying to release transport. Before releasing actual transport.. system check all transport of copies has been successfully imported in QA or not. If one of request is waiting for import then transport will not be released.  Please check Display/Close message window. Your CR will return status message over there... Hope this will help you to understand.
    Thanks
    Jignesh

  • Request not appearing in QA Worklist

    Hi,
    We have a 3 system landscape and the QA approval procedure is configured. Any transport request that is created and released in the DEV box is automatically trnapsorted to the QA (batch program) and then gets appended to the QA worklist for the approval to be transported tot he PRD system.
    We have a typical situation here - we got a transport request from a third party, we added that in the DEV queue and imported it there, then we forwarded the request to the QA box and it was imported by the regular batch program. But it does not appear in the QA worklist.
    Can anyone help - how to get this in the QA worklist or is it that the 3rd party request cannot be added to the QA worlist.
    Regards,
    Hasnain

    Hi Ahmed, It seems that you have resolved the issue. If you did can i have a small clarification since am facing the same problem.
    We have 3 system landscape and when the request is released from DEV system it does not appear in QA worklist, for which we need to manually import the request without approval from QA and the same exists in QUA system QA worklist once imported.
    Do you know why the request is not displayed in DEV system for QA once released. Though we have batchjob running every 5 mins to import the TR we are manually importing the same since it doesnot appear in import queue of QUA as they were not approved my DEV QA worklist.
    But in your case that was 3rd party request which is not appearing in QA worklist.
    I hope everything will be fixed once the QA worklist for DEV is fixed.
    Can you help me out..?
    Thanks in advance...
    Suri tyson

  • Checking Transport requests present in two different clients.

    We have around 200 transport requests that have been transported by consultants from D01 to R01-client1/client2 and I need to check that which transport is present in which R01 system client.. i.e. a) how many of them are present in client 1, b) how many are in client 2 and c) how many are in both. We can check the logs of every transoprt through SE10 but Is there any quick/automated way of checking mass Transport Requests status ?

    Dear Raichandi,
    Please follow the below steps to get the desired information.
    1. Login to D01 (Dev client) to find the released transports..
    2. Execute transaction SE01
    3. Go to "Transport" tab
    4. Give User as "*"
    5. Select "Request Type" by tick mark as Customizing Requests and Workbench Requests
    6 Select "Request Status" by tick mark as "Released" only
    7. Click on "Display Button"
    8. It would display all the released transports requests.
    9. From here you can copy and paste all these requests numbers in the spread sheet
    (CTRL + Y) then use Mouse to select the requets, (CTRL +C), and then paste it in exel sheet.
    1. Now Login to the R01 (QA client) to find the import status of the release transports from D01.
    2. Execute transaction STMS
    3. Click on "Import Overview (F5)" or the Truck Symbol.
    4. It will take you to the Import Queues for the Import Domain D01.
    5. This is the option where you can select the Queue to see the desired information for Quality/Stag/prod system.
    6. Now double click on the required "Import Queue" for R01 (Quality system).
    7. Now Go to  "Import History or (CTRL+ F7)"
    8. Change the Filters as required (may be for time interval or remove any filter on client -Clt)
    9. The import History will display all the Imported requests in all clients in one system (SID), so for your case it will display requests for R01/client1 and R01/client2
    10.  Copy  the same in the spread sheet...
    11. Do the VLOOKUP to find which are not imported in which clients.
    Please provide the feedback if it works.
    Thanks,
    Vinod

  • Oracle SQL Developer  error - "The file-based source procedure Name is not present in the database."

    I recently started working on the Oracle SQL developer. I have 'select' privileges on the QA schema and when tried to execute proc in QA. It is giving the error as 'The file-based source <procedure Name>  is not present in the database.  Was it compiled?'
    instead 'you do not have sufficient privileges to execute this procedure'. Did research on internet but with no luck.What configuration changes needed to be done to make it work.Guide me.

    Sounds like you do not have the correct privileges.  What should have been granted to you by the QA user, or some other user with appropriate privileges, is...
    grant EXECUTE on "QA"."<PROCEDURE_OF_INTEREST>" to "<YOUR_USERID>" ;
    Note that a grant of execute on a procedure has nothing to do with grants of select on some or all of QA's tables and views.
    So, as Vadim suggests, from your connection node in SQL Developer's Connections view, if you expand the Other Users node, then expand QA and look in the Procedures node, do you see the procedure of interest?  If not, you cannot expect to be able to execute it from your userid's connection. And even if you do see it, you may have some other privilege that permits viewing but not executing, like...
    The role SELECT_CATALOG_ROLE
    The system privilege SELECT ANY DICTIONARY
    And even if you do not see it there, then having certain other privileges granted to you could permit executing it in general, like...
    The role EXECUTE_CATALOG_ROLE
    The system privilege EXECUTE ANY PROCEDURE
    Also, note that the 3.0 release is a bit dated nowadays. Upgrading to 4.0.3 production or even the 4.1 EA2 (early adopter) release will, in general, give you a better experience.
    Best wishes,
    Gary

  • Unable to release transport request because of control program tp

    I have create a customized transaction type as a copy of urgent correction SDHF. I am not able to release the transport requests using the action in the toolbox 'Release Transport Request' and I obtain the following error in the log:
    could not start transport control program tp
    But if I directly execute the task 'Release Transport Request' in the task list, it works.
    Another strange thing is that at the beginning both ways worked, but after some days I started to have this problem.
    Thanks
    Antonello

    I did not find any note about this error.
    Someone can help me?
    Thanks.
    Antonello

  • Releasing transport request taking long time

    Hi All,
    I am releasing transport request in SE09, for releasing child request it was taking long time and for parent request taking much more long time.
    In SM50, i didn't find any processes running.
    Can anyone tell me the solution.
    Thanks & Regards
    Uday

    Hi Uday,
    >> I am releasing transport request in SE09, for releasing child request it was taking long time and for parent request taking much more long time.
    You didn't note what release your are running on, but you can check the note 1541334 - Database connect takes two minutes
    >> In SM50, i didn't find any processes running.
    It is normal, because the system exports the transport request by "tp" command at the OS level, after TMS complete its job on a DIALOG wp.
    Best regards,
    Orkun Gedik

  • Problem of calling BAPI to release transport request

    Dear Friends,
    I want to automatically release Transport Request using BAPI (BAPI_CTREQUEST_RELEASE), but I met a difficult during the process that only TR TYPE 'K'or 'W' can be release using this BAPI, if I create an addon program which TR Type is 'S' (stand for Development/Correction), then this BAPI does not work. 
    BTW, you can refer table E070.
    Could you please kindly give me some idea to solve this problem?
    Thank you in advance.
    Best regards,
    Nick

    Dear Li Nick,
    The reason that you cannot release a request of type 'S' is that type 'S' names a local correction, which cannot not be transported (and therefore of course not released).
    Regards, Tino

  • PROBLEM IN RELEASING TRANSPORT REQUEST THROUGH SE10

    Dear all,
    I am trying to release transport request of development server via. transaction se10.Now my problem is that the child(DEVELOPMENT/CORRECTION) is getting released while the parent request is not getting released.
    I checked everything and its showing 'test call of transport control program ended with return code 0208.' I even checked overview of system,overview of connection type,over view of transport protocol and they are fine.my only doubt is after going to se10 when I click transport proposals its showing "WORK FLOW NOT ACTIVE' .
    Is my problem is because of this. Please help its very urgent as due to this I am not even able to transport any request on production server.
    Helpful contribution will be duly rewarded.
    Thanks & Regards,
    VICKY

    hi
    vicky just went through your Query regarding release
    of requests..first of all U be sure of TMS configuration
    see whether it is consistent or not.then after Refresh
    the system and then come to release of requests.
    its true that we can transport through scc1 but first
    check about STMS configuration and the way you set
    that.
    Regards
    manjula.

  • Urgent Correction: Release transport request (transport is red)

    Hello!
    Has some one experience to solve the problem bellow:
    By an urgent correction it is not possible to release transport. In the field "Task" I can see a red point that not allow to proceed.
    If I release the transport manually in the satelite syytem, without CharM, my import runs with error:
    AGR_1016 table class is 'C'. Entries are only imported to client '000'.
    AGR_1016B table class is 'C'. Entries are only imported to client '000'.
    AGR_PROF table class is 'C'. Entries are only imported to client '000'.
    AGR_USERT table class is 'C'. Entries are only imported to client '000'.
    AGR_TIMEB table class is 'C'. Entries are only imported to client '000'.
    Main import
    End date and time : 20071115141115
    Ended with return code:  ===> 8 <===
    The question is:
    I would like to copy some existing role to  cutomer's namespace Z... save the rolle and transport the role via CharM.
    Is it usual to get the error I get?
    Thank you very much!
    regards
    Thom

    Hi Liza:
    You cannot delete released transport requests.
    Don't import them into QAS or PROD.
    If you already imported them, then your only option is to delete the Objects manually in DEV, capture the deletes in a new request and transport th enew one.
    As you know if you released a request, you can ignore it without moving it anywhere.
    Ram Chamarty
    Message was edited by: Ram Chamarty

  • Can TMS warn of objects on released-but-not-imported requests?

    I'm sure this is a common problem: Developer A makes a change to an ABAP program, releases his transport, and imports it to the QA system. Developer B makes a subsequent change to the same program (unaware of Developer A's changes), realeases his transport and imports it to QA. Developer B's QA testing completes first, and his transport is imported to the Production system. Some time later, Developer A's QA testing is completed, and his transport moves to Prod, wiping out Developer B's changes!
    How do we avoid this situation? Is there a way to configure TMS so that it warns Developer B of Developer A's released-but-not-yet-imported-to-Prod transport?
    I am open to all suggestions, including activating user exits in TMS, and coding the warning myself. If that's the only solution, some guidance on TMS user exits and TMS tables I would need to query would be helpful.
    Thanks in advance.

    Well, this thread may be 4 years old, but I have answered my own question (some time ago), and would like to share the answer with the SDN community.
    I ended up activating the BADI CTS_REQUEST_CHECK. In the CHECK_BEFORE_RELEASE method I added my own code to check for "incomplete" transports for any of the objects on the transport being released. The code is pretty involved, but the basic trick is to SELECT all transports for each of the objects in the request from database tables E070, E071, and E07T, then use function TR_READ_GLOBAL_INFO_OF_REQUEST to get the details of each request to determine if it has been imported into the production system.
    Once I have a list of "potentially conflicting" transports, I display it for the user in an ALV grid. I then allow the user to decide whether to go on with the release of the transport, or to cancel the release.
    Cheers,
    Terry

  • 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

  • CMNS support is not present in this image

    Hi,
    We are using a C1721 router to connect a X25 line to an ethernet port. We need to enable CMNS and we get the following error:
    GDM_Cisco#configure terminal
    Enter configuration commands, one per line.  End with CNTL/Z.
    GDM_Cisco(config)#interface fastethernet0
    GDM_Cisco(config-if)#cmns enable
    CMNS support is not present in this image
    This is the device information:
    GDM_Cisco>show hardware
    Cisco Internetwork Operating System Software 
    IOS (tm) C1700 Software (C1700-ADVSECURITYK9-M), Version 12.3(15), RELEASE SOFTW
    ARE (fc3)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2005 by cisco Systems, Inc.
    Compiled Tue 24-May-05 21:33 by ssearch
    Image text-base: 0x8000816C, data-base: 0x81012AF4
    ROM: System Bootstrap, Version 12.2(7r)XM2, RELEASE SOFTWARE (fc1)
    ROM: C1700 Software (C1700-ADVSECURITYK9-M), Version 12.3(15), RELEASE SOFTWARE 
    (fc3)
    Any help would be useful.
    Regards,
    Fernando L

    Dear sir, you should throw cisco from the top of the mountain !
    ilker

Maybe you are looking for