cancel
Showing results for 
Search instead for 
Did you mean: 

Inbound IDOCs to XI triggered from SAP going missing... !!

Former Member
0 Kudos

Hi ,

We have been recently facing issues with idoc messages missing in XI. The IDOC is in status 3 in source SAP system. Running bd75 shows the staus as 12.We do not see an entry in the trfc queue of source system(sm58) to conclude it is stuck in the source system.

Now, the idocs are not visible in IDX5 in XI either and not in sxmb_moni. Is there any other way , say a log/table in XI where we can check to be sure it has not reached XI at all. Or Is it possible that the idoc has reached XI but there is an issue with the Sender IDOC adapter. If its possible , where can we check this idoc is persisted in XI and the IDOC-XML conversion failed ?

Appreciate any pointers!!

Thanks

Saravana

Accepted Solutions (0)

Answers (3)

Answers (3)

STALANKI
Active Contributor
0 Kudos

https:///people/sravya.talanki2/blog/2005/12/20/inconsistencies-while-transporting-rfc-objects-from-... [original link is broken]:///people/sravya.talanki2/blog/2005/12/20/inconsistencies-while-transporting-rfc-objects-from-dev-to-qa-150-sp12

CHECK POINT 6 AND 7 .MGHT BE USEFUL

former_member184154
Active Contributor
0 Kudos

Check out developer traces (RFC specificly) with ST11 on XI side.

Shabarish_Nair
Active Contributor
0 Kudos

something similar to this came up a week ago ...

can you check into this thread and see if it helps

>>

former_member184154
Active Contributor
0 Kudos

Maybe obvious, but I'd also check <b>ST22</b> in XI.

More, <b>check your network</b>: do a

ping -t hostname > ping_hostname.txt

from XI to R/3 and viceversa, say for at least one hour. Put collected stats somewhere like an excel sheet and check you don't have <i>holes</i>. In that case you need help from network guys (maybe a naughty switch?)

Alex

Message was edited by: Alessandro Guarneri

Former Member
0 Kudos

Thanks for the pointers. we plan to check the dev rfc trace files in XI, but look like the problem may be with the sender source system. We checked two tables , ARFCSSTATE (sender SAP system) & ARFCRSTATE (receiver XI system) and could see all the idocs that have been successfully receieved in XI are listed here with the same transaction id as found in R/3 system, for each IDOC.

We could not see an entry in these tables for the IDOCs that have been in status 12 in SAP , but has not reached XI. Looks like the sender program in R/3 failed a COMMIT WORK or if it comes to worse like Alessandro says , a network glitch that we never did anticipate. but then no entry in the above tables may mean no n/w issues , any one has more ideas about when these tables get updated exactly in sender & receiver side?

Thanks

Saravana

Former Member
0 Kudos

Well, looks like it is a problem with the sender SAP system , it is on WAS 6.2 and notes 869627 & 901878 refer to the issue.The limitation we faced in the course of this issue was not able to prove convincingly that the idocs have not reached XI. dev rfc trace files give a lot of junk info and nothing we could decipher based on the timestamps.

This is just to give an update on this thread, so if at al any others face a similar issue , this may help as a pointer.

Thanks

Saravana

STALANKI
Active Contributor
0 Kudos

sara,

Goto SE11 and check idx* and these are all the tables related to Idocs and you have some history and log and audit data tables also which can be found by description of tables.