No dialog work processes

[Former Member]

Hi,

our abap team created IDOCs(type WMTOCO) around 30k for a month , of which 21 are not processed, All other were sent sucessfully.

They state, For 21 IDOC which are not processed there were no free dialog work processes and they doubt, issue seems to be related to memory as there were no free dialog work processes available to start the processing.

we analysed the dialog work processes, there are 21 dia work processes, and the no of users logging in per day around 200.

need clarifications on the following questions

Is the problem of idocs not processed, because of Dialog work processes ?

Is it an memory issue ?

Will increasing the no of dialague work processes will solve the problem ?

Thanks in Advance,

Satish

[Former Member · Accepted solution]

Satish

The responses above are all correctu2026 some research should be done to determine the cause.

In addition to checking logs, processes, etc., please check the status and logs of the IDocs from transactions WE05 (or BD87).

Youu2019ll need to drill down to the status records, but this should tell you what has not be sent and possibly the reason.

Hope this helps.

PJ

[Former Member]

Hi,

You may avoid this problem by reducing the packet size. I suggest that you activate the BG processing in your system so that IDocs will be processed in your system with the help of BG jobs and your dialog threds will be free for end users. Please refer the below link for the steps to bo done.

"http://help.sap.com/saphelp_sm32/helpdata/en/5f/45f93b4139b478e10000000a11402f/frameset.htm"

With Regards,

Saurabh

[Former Member]

Hi

Ask your ABAPers about what led believe them this it's a memory issue....is there any log or trace error in support of that? Besides you may check in sm21 or st22 or st06 for memory related issues & post them here.

Ravi

[Former Member]

Hi,

Go to Transaction SM50(process overview screen) and see for what the dialog process are waiting.

If all the Dialog processes are busy with running report related to Idocs. Ask your abapers to check once.

Also check in Transaction SM35.

Also check if there is any load executed from any other system on this system where you are facing this problem.

Regards,

Ravi