Errors when releasing some transports in prodction system

[Former Member]

Hi all, I am currently trying to close open transports found in my production systems prior to an upgrade. I am running an SAP 4.6B system and am going to upgrade to 4.6C.

While trying to release them, I got the following errors:

First error:

<h6> This type of request cannot be released

Message no. TK 465

Diagnosis

Request "xxxKO00144" has type "M" and can therefore not be released in

the Workbench Organizer.

System Response

Request "xxxKO00144" is not released.

Procedure

Requests with type "F" are object lists and cannot be released.

Requests with type "M" are client transports and can only be released

with the client maintenance transaction. <h6>

Second error:

<h6>Only requests/tasks of type "P45Knnnnnn" modifiable in this R/3 System

Message no. TR 775

Diagnosis

In this SAP System, you can only change requests/tasks of type

"P45Knnnnnn". The function you selected tries to change a request/task

from another system.

Requests/tasks have a special namespace for each system and can only be

changed in their original system.

System Response

The function terminates.

Procedure

If necessary, repeat the function with a request/task that originated in

this system.</h6>

Note for the second error I was trying to release some transports with different SIDs from the current system. I am not sure how they got there as I only took over the system recently

Please help as I need to release them before my upgrade can proceed.

[Former Member]

Hi,

There is an emergency procedure to release these requests. It is documented in SAP note 7894, point 2. In your case the SQL statements would look as follows:

delete from sapr3.tlock where trkorr in ('P45Knnnnnn','xxxKO00144');
update sapr3.e070 set trstatus='R' where trkorr in ('P45Knnnnnn','xxxKO00144');
update sapr3.tadir set srcdep=' ' where srcdep='R';
commit work;

In SAP issue a /$TAB or /$SYNC to invalidate the buffers.

I stress that this is an emergency procedure only. Don't use this on requetss you can release in the normal way.

Good luck,

Mark

[Former Member]

Hi AC you got it right. R3Up is asking me to release these transports. That is why I have been trying to release them without success.

And yes the transports cannot be released cos it either is not generated in this system or some other unknown reason.

Hi Rohit, see above for the reasons why I need to release the transports. These transports are not found in the development nor quality system so I cannot release them there and transport to production.

Hi Joe, my reply to AC for the reasons as well. System did not alert me to another locked objects inside.

[Former Member]

Is the R3up asking you to release this specific transports? the first one looks like a client copy using export/import and the second can´t be released because it was not generated in the PROD system where you are right now.

[Former Member]

Is there a specific reason you are trying to release a client transport request? Has the system alerted you to any objects that are locked within the transport?

Thanks,

J. Haynes

[Former Member]

hii

you dont need to release the transports in your production system

you should release the transports in development system,then transport to quality and production

Rohit