R/3 --> RFC --> XI Message stuck in R/3 SM58 with error "invalid date"

[Former Member]

Hello,

we have a scenario where we send a message via RFC from R/3 to XI and further on to a file. Everything is setup according to blog 1438 and most of the time it works fine. But sometimes the messages get stuck on R/3 side in SM58 with error "program ID not registered". I can then execute the LUW and it starts working immediately. One strange thing is that the time in SM58 for that message is in the future and there is a comment "invalid date". The R/3 system is a 4.6b and XI is SP16.

Can someone explain why the time is in the future for this message only and is this probably the reason that it hangs?

Thanks for your help.

/Michael

[Former Member]

I should maybe also add that we now schedule a job every 5 min to push on the "hanging" entries in SM58 - as a workaround so to say.

[prabhu_s2]

Does ur RFC take any date parameters from R3 ?

[Former Member]

How can I check that?

[prabhu_s2]

Check in code using the tcode for f/n mod (SE37). Maybe some date field doesnt match the date format