Delete an already released transport request

Hello together,
I have a problem in SE09/SE10 with a transport request.
The request is as follows:
Modifiable
D01K939667 100 Username /Description
D01K939668 Username Customizing Task
The requests itself has the status "Modifiable". The task D01K939668 within the request is already released. I have to delete the whole request now, but when trying to delete it, it says "Request D01K939668 already released". How can I delete a task within a request, that is already released?
Thank you for any help!
Best regards
Klaus Hirschegger

Of course, you can
But you have to chnage status of the request:
Use transaction SE38 or SA38 and run program: RDDIT076
Set your request number and run the program
After request is shown double click on it
You should be able to change status from R to D
And now, you can delete the transport for example in transaction: SE10...
Help on ABAP: Few Tips for Transport Request Manipulation

Similar Messages

Delete Release transport request

Hi Gurus,
I need to delete a transport request which is already release. Please let me know what is the best way to do that.
Thanks
Liza

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

Is it is possible to delete released transport requests...

Hi Experts,
I had created transport request and it is released, moved to quality with errors. I dont know why I am getting errors while transporting the request, Now I am creating another transport request. Is it any possibility to delete released transport request or is there any solution for this. why I am getting errors while transporting from dev to quality.
Thanks & Regards,
RAJ

HI,
Its not possible to delete the released transport request. You should have to follow transport procedure .
T-code for Transport Connection- Check in SE09/se10 for creating requests.
For collecting objects you have go Transport connection without missing the objects.
SE03 for checking the Request objects.
Go to transport connection in RSA1 Select u r Data target or report what ever it may be in development sys & select only necessary objectsu2026 click on transport optionu2026u2026it will ask the transport request create new req. go to SE-9 release the objectu2026go to STMS import u2026RELEASE The objects in quality sysu2026same procedure to production sys.
Thanks
sudhakar.

Is it possible to delete a released transport request

Hello
I wander is it possible to delete a released transport request. Is it possible to delete a transport request with released only an task

You can but you have to chnage status of the request:
Use transaction SE38 or SA38 and run program: RDDIT076
Set your request number and run the program
After request is shown double click on it
You should be able to change status from R to D
And now, you can delete the transport for example in transaction: SE10...
Help on ABAP: Few Tips for Transport Request Manipulation

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

Database tables holding details for a non - released transport request

Dear All,
We are implementing SAP ECC 6.0 u2013 ABAP stack, on IBM iSeries / System i, i5/OS V5R4 -
SAP kernel release 7.00, kernel patch number 173
Could someone please guide me to the database tables holding the details for a non u2013 released transport request.
The problem is the following :
We encountered some data corruption in the database of our development system, so we did a restore from the previous day's backup (RSTLIB command) for the database library : R3DEVDATA, without restoring the /usr/sap/trans directory, then we did an APYJRNCHG command for the journal receiver spanning from the previous day's backup until the corruption time (remote journal on a remote system.)
We are now facing the following conflict :
One of our programmers is now un-capable of updating an ABAP program, which he previously added in a transport request, which he did not release.
( This was done during the day of the data corruption)
When the programmer is trying to update the ABAP program through the ABAP workbench, he receives the error :
'Request lock on non u2013 existent task / request DEVK921426'
No details for the transport request DEVK921426 exist in either of the two directories :
/usr/sap/trans/data , /usr/sap/trans/cofiles
The way I see to solve this conflict (eliminate this lock) is to delete the different entries related to the un-released transport request from the database tables.
Any clues would be highly appreciated.
Thank you in advance for your cooperation.
Best regards.
Reda Khalifa

Dear Volker,
Thank you very much for your interest.
The transport request of interest did not appear in transaction code SE03
Eliminating the record from table TLOCK indeed did solve the problem.
Thank you again.
Best regards.
Reda Khalifa

Creation date for released transport request

Hello everybody!
Does anyone know how to find the CREATION date for a released transport request? I've already checked table E070CREATE and it only has entries for modifiable requests.
Best regards,
Luís Andrade.

I think transport is released date field in E070 is overwritten with the releasing date.
a®

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.

Releasing transport requests with job roles take forever after upgrading to Netweaver 7

Dear experts,
Some time ago we've out SAP ECC 5 system to ECC 6. Since then, it takes a very long time to release transport requests containing job roles.
For example, a request containing 154 job roles (1 template and 153 derived roles) took 4 hours to release in our DEV system. Before the upgrade this only took a couple of minutes.
Afterwards, the import in our QAS and PRD system don't take longer than normal.
Apparently this time is taken by the Export phase:
Checks at Operating System Level
17.04.2014 09:50:03
(0) Successfully Completed
Pre-Export Methods
17.04.2014 09:50:37
(0) Successfully Completed
Export
17.04.2014 13:51:02
(0) Successfully Completed
Does anyone know what causes this and how to solve?
Kind regards,
Nicolas

Hello Nicolas,
What I understood from your description is that ,it takes very long time to release the job. Once it is released, execution does not take much time.
To me it seems to be background job/work process issue. Maybe all the background work process are busy to execute current jobs and no free work process available for the jobs which are in the queue. In that case, if possible try to increase number of bg work processes.
Check for any performance issues during that period. Check if there is any locking issue and jobs are stuck because of that.
Hope this helps to investigate the issue
Regards,
Archana

Releasing Transport Requests

Hi,
I want to release trasport requests weekly once,guide me for the same.
Thanku

Hi Harshit,
Releasing a transport request automatically is not a recommended practice .
It can lead to number of errors and inconsistencies .
Who will monitor the logs or may be developer want to add some more stuff in same TR.
So there should be no suggestion like releasing transport request automatically from consultant end.
Still if you need you can get some idea from here
Re: Automatic Release of Transport Request: By ABAP Program
Regards,
Gagan Deep Kaushal

How to delete released transport request

Gurus,
We are doing a system synchronization and for that we are going to make a system copy from BWP TO BWD. Hence I am told to delete all modifiable transport requests, which I did without any problem.
But in BWQ there are some transports which are already released and how I can delete them. They don't show under modifiable transports , rather they show under released transports.
(For your information in my company any transport released from BWQ does not automatically go to production, we have to send a manual e mail request with the transport # to basis. Therefore these transports even though they show released they will never make it to production as I have never sent release request to basis and these transport are of no use any ways.
So please guide me how to delete these released transports in BWQ.
Thanks
MK

Hi MK,
Goto Import queue of target system(T Code: STMS) and delete(Shift+F2) from import queue. or from menu --> Request --> Delete.
In this way it only deletes from import queue.
Hope it Helps
Srini

Error in FM DDIF_NAMETAB_GET when deleting BI objects via transport request

Dear all,
when importing a transport request in which several types of BI objects are deleted (Infocubes, DSO's, transformations, routines, DTP's, query elements, infosets, process chains). The import terminates only when transporting from acceptance to production with return code 12 due to an uncaught exception:
Transporting from development to acceptance did not raise this exception.
The ST22 dump (see below) refers in the "contents of system fields" section to a DSO, and to post-import activities. The DSO and the associated tables could not be found (rsa1 & se16), since they are deleted as desired.
Some of the relevant notes that I have found do refer to DSO related problems, but they all indicate to install SP19 which we already have installed (BW 7.0 Patch Level 23)
Could you please assist in pointing out potential solutions based on the information from the ST22 Runtime Error below?
Kind regards,
PJ
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_RS_PROGRAM_ERROR
Date and Time          08.02.2011 10:48:14
Short text
    An exception occurred that was not caught.
What happened?
    The exception 'CX_RS_PROGRAM_ERROR' was raised, but it was not caught anywhere
    along the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
    'CL_RSDD_DS====================CP' has to be
    terminated.
Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_RS_PROGRAM_ERROR', was not caught
    and therefore caused a runtime error.
    The reason for the exception is:
    Error in BW: Error in DDIF_NAMETAB_GET
How to correct the error
    If the error occurs in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "UNCAUGHT_EXCEPTION" "CX_RS_PROGRAM_ERROR"
    "CL_RSDD_DS====================CP" or "CL_RSDD_DS====================CM001"
    "APPEND_DS_TEC_FIELDS"
System environment
    SAP-Release 700
    Application server... "dp1ci"
    Network address...... "<removed>"
    Operating system..... "HP-UX"
    Release.............. "B.11.23";
    Hardware type........ "ia64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 45
    Shortdump setting.... "full"
    Database server... "spisap02"
    Database type..... "ORACLE"
    Database name..... "DP1"
    Database user ID.. "SAPBIW"
    Terminal................. " "
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Dec 14 2009 20:47:35"
    create on........ "HP-UX B.11.23 U ia64"
    Database version. "OCI_102 (10.2.0.1.0) "
    Patch level. 236
    Patch text.. " "
    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
    SAP database version. 700
    Operating system..... "HP-UX B.11";
    Memory consumption
    Roll.... 5979936
    EM...... 0
    Heap.... 1459888
    Page.... 40960
    MM Used. 6988880
    MM Free. 415648
User and Transaction
    Client.............. 000
    User................ "DDIC"
    Language key........ "E"
    Transaction......... " "
    Transactions ID..... "4D5111661004210BE10000000AFA2502"
    Program............. "CL_RSDD_DS====================CP"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
Information on where terminated
    Termination occurred in the ABAP program "CL_RSDD_DS====================CP" -
     in "APPEND_DS_TEC_FIELDS".
    The main program was "RDDEXECU ".
    In the source code you have the termination point in line 61
    of the (Include) program "CL_RSDD_DS====================CM001".
    The program "CL_RSDD_DS====================CP" was started as a background job.
    Job Name....... "RDDEXECL"
    Job Initiator.. "DDIC"
    Job Number..... 10475900
Source Code Extract
Line SourceCde
   31         RAISE EXCEPTION TYPE cx_rs_program_error
   32           EXPORTING
   33             text = 'Invalid DSO subtype'.                   "#EC NOTEXT
   34     ENDCASE.
   35
   36 *   get table name from DDIC
   37     CALL METHOD cl_rsd_odso=>get_tablnm
   38       EXPORTING
   39         i_odsobject = n_infoprov
   40         i_tabt      = l_tab
   41       IMPORTING
   42         e_tablnm    = l_tablnm
   43       EXCEPTIONS
   44         OTHERS      = 1.
   45
   46     IF sy-subrc <> 0.
   47       RAISE EXCEPTION TYPE cx_rs_program_error
   48         EXPORTING
   49           text = 'Error in CL_RSD_ODSO=>get_Tablnm'.        "#EC NOTEXT
   50     ENDIF.
   51
   52     CALL FUNCTION 'DDIF_NAMETAB_GET'
   53       EXPORTING
   54         tabname   = l_tablnm
   55       TABLES
   56         dfies_tab = l_t_comp
   57       EXCEPTIONS
   58         not_found = 1
   59         OTHERS    = 2.
   60     IF sy-subrc <> 0.
>>>>>       RAISE EXCEPTION TYPE cx_rs_program_error
   62         EXPORTING
   63           text = 'Error in DDIF_NAMETAB_GET'.        "#EC NOTEXT
   64     ENDIF.
   65
   66
   67   ELSE.
   68 *   model table only needed for standard datastore objects, for
   69 *   write optimized DSOs target table is a changelog that is fully described by
   70 *   dta_pro (infoobjects)
   71     CHECK n_s_dta-odsotype = rsdod_c_type-standard.
   72
   73 *   get model table fields to add
   74     CALL METHOD cl_rsd_odso=>get_mod_tab
   75       IMPORTING
   76         e_mod_fld_ur = l_t_comp.
   77   ENDIF.
   78
   79 * according to T.B. ( 13.04.2007) the correct position is
   80 * not needed in the D version
Contents of system fields
Name     Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 1
SY-DBCNT 1
SY-FDPOS 0
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE Execute Post-Import Methods and XPRAs for Transport Request
SY-MSGTY E
SY-MSGID DA
SY-MSGNO 300
SY-MSGV1 /BIC/AV_AMOFCB40
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20110208
SY-UZEIT 104759
SY-XPROG SAPLSYST
SY-XFORM SYSTEM_HOOK_OPEN_DATASET

Hi All
We are also experiencing this same error when transporting deletions of multiple objects.
Although the transport was cancelled in the destination system (production) it appears to have largely deleted all objects successfully except for DSOs.
The DSOs still appear in the table RSDODSO (via SE11) but are not visible anywhere else. When you try to view the DSO via RSDODS a warning appears saying "DataStore object to be deleted by transport -> delete only allowed". If you try to delete them in this transaction the same ABAP runtime error as the transport appears.
Any assistance would be greatly appreciated!
Regards
David

Delete an already released transport request

Similar Messages

Maybe you are looking for