Transport Error - tp finished with return code: 152

[Former Member]

Howdy All,

I put through some transports into Production on Thursday 22/06/2007 which worked succesfully.

Nothing has changed in the instance profiles, TP Parameters or the TMS. Now when I try to transport a different request I get the following :

26.06.2007 TP 1

-

---

Transport executed for: E75K913986 with command string:

This is E:\usr\sap\P75\SYS\exe\run\tp.EXE version 340.16.31 (release 640)

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBNAME is no longer used.

The import of the transport request E75K913986 for system P75 was not performed.

Please check the tp command. The buffer entry is printed out below.

P75 buffer:

TASK .CLI|PROJECT |P|CMD I |DD Im |Activ |MainI |MC A

-

---

----

---

-----------+--+--+--

E75K913986 .300| | |0000 | | |0000 |

tp returncode summary:

TOOLS: Highest return code of single steps was: 0

SWARNS: Highest tp internal severe warning was: 0152

tp finished with return code: 152

meaning:

Nothing done.

Transport function error: Call failed

E75K913986 has previously been imported. It needs to be re-imported because since it went in another transport (which was created before it) has gone and overwritten some of the objects.

Your advice / guidence would be greatly appreciated, there doesn't seem to be too many articles about this error.

Cheers

[Former Member · Accepted solution]

Hi,

While importing, select option import transport request again.

Regards

Ben

[Former Member · Accepted solution]

As Ben says,

select option "import transport request again"

if that doesnot work select the following 2 options.

select option "import transport request again"

select option "overwrite originals"

if you are applying from OS Level,

tp addtobuffer <transportno> <TrargetSID>

tp modbuffer <transportno> <targetSID> mode=u+12

tp import <transportno> <targetSID> client=<clientno>

hope this helps!

[former_member187281]

I know it has passed 7 years since this problem was recorded, but since we ran into this issue and were looking for assistance, the provided answers above did not apply to our case.  Therefore, we add some tips for the readers:

Check the TMS alert in the system where the transpor was created.  It can be done in many ways, but you ca do STMS >  Monitor > TMS Alert > TMS Alert Viewer

Our issue was with retrofit, which did not exist in 2007.  Basically TMS is reporting that the transport of copies that is being expected does not exist, hence "Nothing done".

Solution was to generate in SolMan via report RETRO_SERVICE_CREATE_RFIT_DATA the missing transport of copies.  Once that was done, we could perform the transport move.

Regards,

Juan Carlos

[Former Member]

This has worked cheers guys.

We've just done a few server changes which sent me looking for a more technical solution rather that the obvious one.....

Thanks for the prompt response