Sender RFC Adapter only processes first message

[Former Member]

Hi there,

we have a R/3 - XI - 3rd party scenario, where the R/3 - XI communication will be established through a RFC.

The RFC destination was properly configured in SM59 in R/3 and also was the XI's sender RFC adapter, with the same program ID.

We called the RFC in R/3 Abap code and the message succesfully arrived at XI (it could be found in SXMB_MONI). However, any other call from R/3 would not result in a message arriving at XI (no new entry in SXMB_MONI nor in Message Monitoring, at RWB). New messages only appear again if we set the status of the adapter to inactive and then active again. Then the message arrives, but again, only the first one.

Can anyone help with this?

Is there any misconfiguration in XI or RFC Destination?

Or is it the abap calling that should be processed in another way?

Thanks in advance,

Henrique.

[moorthy · Accepted solution]

Hi,

-Can you refresh Adapter Metadata for RFC adapter.

-Just check the SAP Note~ 730870

-For cache refresh-

Hope this helps,

Regards,

Moorthy

[Former Member · Accepted solution]

Hi,

If you are calling your RFC in a loop, please can you put COMMIT WORK after every call.

Regards

Vijaya

[henrique_pinto · Accepted solution]

Actually, I'm not familiar to ABAP language, so I can't say how the calling is being proceeded. Our scenario is online, meaning, when R/3 generates a XML, it immediately must be sent to XI via this RFC and then transmitted to the third party. But it appears that it's being sent to a job scheduling and then it's started. We think the problem's here.

I'll send your tips to the R/3 ppl. Thanks a lot!

[henrique_pinto]

Problem solved.

It was some problem with background tasks handling at application server (R/3).

Regards,

Henrique.

[MichalKrawczyk]

Hi,

>>>Or is it the abap calling that should be processed in another way?

the important thing is the commit work

which must be done after call function

and you can only have one call function

before the commit work

do you see any other errors in SM58?

>>>Is there any misconfiguration in XI or RFC Destination?

Or is it the abap calling that should be processed in another way?

one or the other - no doubt about that

Regards,

michal

-

---

<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>