Issue In processing an IDoc with Huge Segments

[Former Member]

Hi All,

When we are trying to process an Huge IDoc which has large number of segments. The IDoc process starts and stops in the middle and remains in 64 status ( there are no short dumps etc).

Currently the IDoc is configured to be Trigger Immediatly. However when we schedule the same IDoc in a background the IDoc is processed successfully.

So wanted to check what might be the reasons for Idoc to stop the process in between.

Regards,

Swaroop

[tushar_shukla]

Possible reasons :

- Huge memory consumption

- Large processing time for Idoc segments .

Idoc parsing and processing happens inside a LOOP statement around EDIDD table , now if you have larger no of segments this will lead to larger execution time .

There may be other performance reasons e.g. Read Table without Binary Search ; check the IDOC processing function module code .

Also check the SAP notes for the IDOC processing function module code ; just mentioning a similar SAP note 381942 .

[Former Member]

Hi Thushar,

Thank you for the reply. I understand large no of segments corresponds to large memory consumption but my question was if the partner profile is configured as Trigger Immediatly I understand it will start the process in a back ground mode. So it should not stop the process in middle. As I told if the Same Idoc is schedule through RBDAPP01 in a background Job it works fine. So was curious to know why it does not work with Trigger Immediatly Option.

Regards,

Swaroop

[tushar_shukla]

 my question was if the partner profile is configured as Trigger Immediatly I understand it will start the process in a back ground mode .

Trigger Immediately option does not uses background work process , it uses dialog work process . Even SAP does not recommend to process large idoc in foreground i.e. Trigger Immediately .

I hope it clears your doubts .