No messages flowing in XI

[former_member188885]

Hi All,

I have a RFC to File scenario. This was working fine. But now, for few days there are no messages in XI. The files are also not in the ftp. I tried to check activate the channels, but still there are no messages.

Need your replies and suggestions.

Regards,

Lavanya R

[Former Member · Accepted solution]

Hi,

I suppose this is not productive system if the problem already persists a few days

Anyway, if the messages are not reaching PI , but they left ECC in good shape, it is most likely they can be found in SM58.

If they are leaving PI (as seen in SXMB_MONI) but not arriving in teh file system see if you can find errors in the Communication Channel Monitoring (in RWB)

Good luck.

Robert.

[Former Member]

Hi Lavanya,

Refresh the cache once, if you still face the problem,STOP and Restart the communication channels once,it may work.

Thanks,

Amar.

[former_member188885]

Hi all,

Thanks for your replies.

I have checked the RFC destination and it is working fine.

I have checked the communication channels and also the monitor, but there are no messages.

There are no messages in Queue in PI.

The jobs are showing as successful in R3, but messages have not reached PI.

Please suggest

[Former Member]

Hi,

As you do not mention it explicitly i must ask again:

Have you checked SM58? (check it on ECC!)

It is really likely the errors can be found there.

kr

Robert

[former_member188885]

Hi den,

Can the data be seen in SM58 or does it show the errors alone?

[Former Member]

Hi,

First: when you open SM58 you get a selection screen. Make sure there are * in all fields.

Then execute.

Should be a list of entries.

If the error is there you should see the top entry with some error status.

If all is empty than the error is not there.

kr

Robert

[venkatagiri_gongadi]

Hi,

Another point:

check SM58 at R3 side..

Girii

[sugata_bagchi2]

Hi Lavanya,

As the files are not there in ftp, please check the message in RWB adapter engine and check if the messages are stuck there.

Possible reasons-

1) If you are using EOIO as QoS then if one message has failed that will block the entire queue and prevent the processing of subsequent messages. Please cancel this message from the queue of the adapter engine while searching the messages.

please check the conversationID while searching the message it will show you the queue name.

2) Check the RFC connection and check the parameter "Maximum Connection" of the RFC channel if it is 1 try to increase to 10 or 12 .

3) Check the outbound queue of the R3 even though the job has finished processing.

Thanks

Sugata B Majumder

[Former Member]

Hi Lavanya,

Check the sender communication channel in RWB if the process is success or not.

Regards

Deepthi Premnath

[Former Member]

Hi Lavanya,

If you could not see the message in PI, then definitley it is not reached PI.. and blocked at R3 end.

Check at R3 side.. whther the Outbound queue is stucked?

Thanks,

Anudeep

[former_member188885]

Hi Anudeep,

I checked at the R3 end. The job is finished in the R3 end.

[Former Member]

Hi Lavanya,

Check in SMQ1 transaction of R3, and also try with "BD75 / BD87" mostly IDOCs will stuck in these transactions on R3 side.

If these all did not solved your poblem.. just have a check with other RFC and monitor the result, you can find some differences or some other optins.

Thanks,

Anudeep

[naveen_chichili]

Lavanya,

Though the job is finished in r/3 check the RFC connectivity from SAP R/3 to PI if the RFC connection is not working data will not enter to PI.

Regards,

Naveen

[Former Member]

Hi Lavanya,

Check if the RFC connection is working fine. This could be one of the reason.

Regards,

Deepthi Premnath

[Former Member]

Check RFC destination if it has been changed recently.

Regards

Raj