STMS issue with status request

[Former Member]

Hello!

I have a request that finish with Import Status "Request is ready for for import again" although I've transported it without option "Leave Transport Request in Queue for Later Import" and my transport strategy is "Single transports". The rest of requests are working ok and finish with "Request already imported". It's a strange issue. I could delete the request from the transport queue, but I would like knowing why it's happening.

Many thanks in advance!

Any idea????????

Best regards,

Martina

Edited by: Martina on Jan 25, 2011 9:16 AM

[Former Member · Accepted solution]

This is a flag set during the import, check the 3rd tab 'Options' -> Leave Transport Request in Queue for Later

Cheers Michael

Edit: ah, you already mentioned it, are you sure you disabled the flag? Did the import end without error/warning?

[Former Member · Accepted solution]

Hi Michael,

Thank you very much for replying.

As I've said the option "Leave Transport Request in Queue for Later Import" has NOT been checked in this case, because of this it's so strange.

The request has been transported successfully, but with that yellow import status for "import again".

Best regards,

Martina

[Former Member · Accepted solution]

Hello,

Has somebody any idea?

Thanks for your help!!

Best regards,

Martina

[JPReyes · Accepted solution]

Any additional info?... whats sort of transport it is?, is it attached to a project?

Any info in the tp logs? or import monitor?

Regards

Juan

[Former Member · Accepted solution]

Hello Juan,

It is a HR customizing request. All the other requests of that user and project finishes correctly.

Import monitor for this request said: Maximum Return Code: 0000 - tp ended

SLOG1103.SID tp log of this request: START imp single SID 20110121141439 TRANSPORT_USER server 20110121141438775 INFO TBATG CONVERSION OF SID N not needed TRANSPORT_USER server 20110121141438775 START MOVE NAMETABS SID 6 20110121141440 TRANSPORT_USER server 20110121141438775 START tp_getprots SID P 20110121141440 TRANSPORT_USER server 20110121141438775 STOP tp_getprots SID P 20110121141441 TRANSPORT_USER server 20110121141438775 STOP MOVE NAMETABS SID 6 20110121141441 TRANSPORT_USER server 20110121141438775 START MAIN IMPORT SID I 20110121141441 TRANSPORT_USER server 20110121141438775 STOP MAIN IMPORT SID I 20110121141443 TRANSPORT_USER server 20110121141438775 INFO TBATG CREATION OF EN SID n not needed TRANSPORT_USER server 20110121141438775 START SET VERSION FLAGS SID V 20110121141443 TRANSPORT_USER server 20110121141438775 START tp_getprots SID V 20110121141443 TRANSPORT_USER server 20110121141438775 STOP tp_getprots SID V 20110121141444 TRANSPORT_USER server 20110121141438775 STOP SET VERSION FLAGS SID V 20110121141444 TRANSPORT_USER server 20110121141438775 START EXECUTION OF REPORTS SID R 20110121141444 TRANSPORT_USER server 20110121141438775 START tp_getprots SID R 20110121141444 TRANSPORT_USER server 20110121141438775 STOP tp_getprots SID R 20110121141450 TRANSPORT_USER server 20110121141438775 STOP EXECUTION OF REPORTS SID R 20110121141450 TRANSPORT_USER server 20110121141438775 STOP imp single SID 0000 20110121141450 TRANSPORT_USER server 20110121141438775 START INFORM SAP-SYSTEM OF SID Q 20110121141450 TRANSPORT_USER server 20110121141438775 START tp_getprots SID Q 20110121141450 TRANSPORT_USER server 20110121141438775 STOP tp_getprots SID Q 20110121141451 TRANSPORT_USER server 20110121141438775 STOP INFORM SAP-SYSTEM OF SID Q 20110121141451 TRANSPORT_USER server 20110121141438775

ALOG1103.SID tp log of this request: ALL SID.ALL 6 0000 20110121141441 TRANSPORT_USER server 20110121141438775 DESK979635 SID:900 I 0000 20110121141442 user1 TRANSPORT_USER server 20110121141438775 DESK979635 SID < 0000 20110121141442 user1 TRANSPORT_USER server 20110121141438775 DESK979635 SID.ALL V 0000 20110121141443 user1 TRANSPORT_USER server 20110121141438775 DESK979635 SID.900 R 0000 20110121141448 user1 TRANSPORT_USER server 20110121141438775 ALL SID.ALL Q 0000 20110121141451 TRANSPORT_USER server 20110121141438775 ALL SID.ALL 6 0000 20110121142103 TRANSPORT_USER server 20110121142101087 DESK979635 SID:900 I 0000 20110121142106 user1 TRANSPORT_USER server 20110121142101087 DESK979635 SID < 0000 20110121142106 user1 TRANSPORT_USER server 20110121142101087 DESK979635 SID.ALL V 0000 20110121142107 user1 TRANSPORT_USER server 20110121142101087 DESK979635 SID.900 R 0000 20110121142111 user1 TRANSPORT_USER server 20110121142101087 ALL SID.ALL Q 0000 20110121142114 TRANSPORT_USER server 20110121142101087

Best regards,

Martina

Edited by: Martina on Jan 26, 2011 12:51 PM

[Former Member · Accepted solution]

One more question, does the target system have multiple clients and do you have client depending transport routes (i think this is called extended transport management or something)? Looks like in your case the import went into client 900.

I did a few tests myself, but am not able to reproduce it given you have single requests...

Cheers Michael

[Former Member · Accepted solution]

Hello Michael,

It is an isolated case and because of the peculiarity, I'm investigating it. Only this one request is having this behaviour.

The target system does not have multiple clients and you are right, the import went into client 900.

Many thanks for your tests. I think I will delete this request without a reasonable explanation...

Best regards,

Martina

[Former Member · Accepted solution]

Hello,

I have another request in the same case, I've transported it without option "Leave Transport Request in Queue for Later Import" but it finished with the "Request is ready for import again" yellow warning.

Please, could somebody help me with this issue?

Best regards,

Martina

[Former Member · Accepted solution]

Hi.

The status: Request is ready for import again:

The request has already been imported into the target system. To avoid inconsistencies that can occur when changing the import order, this request is imported again during the import of the entire queue. Therefore, this request stays in the import queue until all the requests have been imported.

Check the import log and paste here any warnings.

Regards

William Neira

[Former Member · Accepted solution]

Hello William,

Thank you for your reply.

I've neither warnings nor errors at all.

Best regards,

Martina

PS. Thanks all, I'm closing this issue. I'll delete these requests.