Figuring out the IDOC reference from XI

[Former Member]

Hi All,

Is there anyway where we can get the reference of the IDOC that is posted from R/3 to XI, in some tables..like we have for R/3.

I want to find out with the this Identifier...what happened to it, when it reached XI..

Basically the status of the IDOC...can be got from the MONI..but if it is 15,000 records..i Guess i would need some table rather than a log.

[Former Member]

No,

Actually, couple of my IDOCs are in message to be processed(green flag) mode.

And I am unable to process those messages. I want to find out a place where I can get the list of all the IDOCs which were not processed.

[moorthy]

Hi,

go to transaction SM58 in the R/3 system and check the tRFC status..

If it is in the green flag , it may be because of Queue stuck up. Go to transaction SMQ2 in the XI box and check the Queue status..

This blog may help u on Queue-Admin part~/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically

Regards,

Moorthy

[Former Member]

Hi Vijaya,

also have a look at transaction SM58 in XI, if the RFC destination for the target system is wrong or simply the user is locked you'll see the a stuck tRFC call there.

Note that you can schedule report RSARFCEX on XI that tries to resend tRFC in error (specially usefull in case of temporary error).

Kind Regards,

Sergio

[bhavesh_kantilal]

Hi,

><i>. I want to find out a place where I can get the list of all the IDOCs which were not processed.</i>

In SXMB_MONI, after you say monitor for processed messages --> in the selection screen make the status as per your requitrement and you can see only the Idoc's in the status that has the problem!!

Regards

Bhavesh

[Former Member]

<i>In SXMB_MONI, after you say monitor for processed messages --> in the selection screen make the status as per your requitrement and you can see only the Idoc's in the status that has the problem!!</i>

Its a out of curious Question, does it happen that, there are some 1000 IDOC sent and only 995 are processed. I have seen this happening in my IDOC to file scenraios(BPM). That when I send some huge IDOCs some of them are not processed and remain in the "to be processed state".

<b>This should not happen in XI, as it will lead to unreliability.</b>

[bhavesh_kantilal]

Hi,

It depends on a number of factors.

1.Are all these 1000 Idoc's hitting XI at the same .
2. Are you using a BPM?

We faced a smilar problem once when the SAP system was sending us around 5 k Idoc's at the same time. We had to avoid a BPM as 5 K idocs hitting XI would mean 5 k BPM instances running parrallely which ofcourse would have lead to memory and Queue issues/

We also had SAP fine tune our prod and pre prod systems to take such high load and after that never faced this issue.

Likewise, if you are on dev, i guess the hardware etc would not have been quicksized and configured for ideal perfromance. But , as you move into higher environments, if all settings are done fine, you are not going to face this issue in an ideal situation!

Regards

Bhavesh

[Former Member]

<i>1.Are all these 1000 Idoc's hitting XI at the same .

2. Are you using a BPM?</i>

1. Yes, they are hitting the XI at the same time. In the WE20 of R/3, Output Mode is Collect IDocs and I am running a Job which sends at a shot, those 1000 IDOCs.

2. Yes

So If I have to overcome this..i need to contact the SAP guys or can it be done by the basis. If Yes, what parameters needs to be fine tuned?

[Former Member]

Hi,

Could you please elaborate on the BPM design?

Is your BPM based on the time based collect pattern?

In case, there are no correlations in your BPM, then, as Bhavesh said, it would result in a number of BPM instances being created, which would result in system slowdown, which wuld inturn result in messages being unprocessed.

Regards,

Smitha.

Message was edited by:

Smitha Rao

[Former Member]

<i>Could you please elaborate on the BPM design?

Is your BPM based on the time based collect pattern?</i>

My BPM is time based and it collects for every 15 mins. So what i understand is, it will create an instance for each hit of a IDOC, but again the lot will be different from the other IDOC lot. Please correct me if my understanding is wrong.

[Former Member]

Hi,

Please make sure that you have specified, the correlation that you are using, at the block step too. (and also at the receiver step).

This is a BPM Best practice that needs to be followed.

Your understanding of the time based collect pattern is right.

Regards,

Smitha.

[stefan_grube]

Use transaction code IDX5:

http://help.sap.com/saphelp_nw04/helpdata/en/c1/bab13bb3acd607e10000000a11402f/frameset.htm

Is this, what you are looking for?

Regards

Stefan