A Question that Challenges Your Talent and PI Skill: Issue of Bundled IDocs

[Former Member]

Hi,

We are caught up by a bizarre situation. We are migrating from R/3 to ECC 7.1. There is an external system that is currently receiving Material Master (MATMAS) IDocs directly from the R/3. The R/3 sends IDocs in packs of 50. This external system is not a SAP system. It has a proprietary program to convert IDocs from R/3 to its own format. Currently, the R/3 and the external system work well.

Now, in our new, migrated environment, the ECC sends IDocs to PI, and PI forwards the IDocs to this external system. IDocs are delivered from ECC to PI one by one, and PI also delivers IDocs to this external system one by one. However, in the PI XML Message Monitor ( T-Code: SXI_MONITOR ), <b>if more than one IDocs end the PI processing within the same second ( as is shown by the u201CEnd Timeu201D column in the XML Message Monitor ), that external system may receive some of those IDocs as one single IDoc, that is, multiple IDocs are somehow merged into one, sharing the same control record. </b>

Two Questions:

(1) Do any of you know why this happens? Have you ever encountered such a case?

(2) We have tried to delay the IDoc processing in PI so that IDocs could be processed by one per second, that is, no more IDocs are processed within the same second in time. We used various methods, such as Java sleep, meaningless calculations in a loop, etc. But all those methods failed. Some IDocs are still processed within the same second, and there is no pattern. It seems PI is not good at controlling the processing time to the precision of seconds. Do you have any advice/suggestion?

Thanks in advance for your help!

[Former Member · Accepted solution]

Hello sir,

Kindly check whether IDoc bundling is enabled?

/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm

That should fix this issue.

Regards

Vivek

Edited by: vivekwali on Apr 18, 2011 8:24 PM

Edited by: vivekwali on Apr 18, 2011 8:35 PM

[Former Member · Accepted solution]

Thanks a lot for your help! But our problem is the opposite. That is, we have to let PI send Idocs one at a time. But our PI just does not do that. For example, when we send out 10 IDocs, PI may send one IDoc at its first RFC call to the external system, then send three IDcs at the next RFC call to the external system. The external system only accepts one IDoc per RFC call.

<b>Out goal is to make PI achieve the same effect as the ABAP program RSEOUT00 with the Maximum Number of IDocs = 1. </b>

Actually, we tried using RSEOUT00 with the Maximum Number of IDocs = 1 on ECC to send IDocs to PI, hoping it would have some impact on how PI sends out the IDocs. Unfortunately, it did not help.

[Former Member · Accepted solution]

Hello Baohua

In Integration Directory there are parameter settings which you need to visit.

Just have a look at processing and content conversion parameter for that particular communication channel which is being used.

Regards

Vivek

[Former Member · Accepted solution]

This morning, the problem is solved. At the beginning, we were not clear what causes the problem. Later, it was found the cause of the problem is that PI sends out IDocs in packs of multiple IDocs. Then, we switched our focus on how to make PI sends out one IDoc per pack; and finally we got this SAP note (1058366) about how to configure the PI Idoc packaging. We followed the instructions in the note, and the problem was solved.

Again, vivekwali, thank you for your help!