Maximum number of work process reached Message no. /SCWM/MFS309- SAP MFS

[former_member663735]

Dear MFS Experts ,

We are stuck at a position where our EWM system is not able to send message at a certain point of time to PLC system and it shows in the error log with below message.

Message no. /SCWM/MFS309

Our Pallet is at the conveyor system where it is picked up by SRM machine .SAP system has received EMPTY telegram and it is about to send the deletion message but it is not sending to PLC system and when we are checking logs we are getting below information always for such issues.

Due to above error below message can be seen at the Conveyor system .Pallet is picked up physically by SRM system but in system the Transport Order still remains at the Conveyor system(which should be deleted based on the Telegram -EMPTY received by the PLC system).

Need your suggestions and advice as how to handle this situation. Thanks.

[former_member663735]

Hi ykbbrn ,

Yes .We have solution to this problem. Root cause of this issue is due to the reason that processing of task in warehouse in high due to which the work processes are not able to proceed .We set this work processes based on the volume that is going to be handled in our warehouses.

We can solve this by increasing the appropriate work process count (Dialog,Update,Background etc).

Second option to this problem is from the MFS technical side :If there is an issue similar like this .There should be a mechanism to re-try the execution of task once again after few seconds.

For ex: If there is a queue record created ,we need to make sure that this queue record is again processed after sometime provided that the data which this is going to process is not archived .

You cannot identify/see the worker process its available or not in real time since the execution is done in milliseconds and its gets released after that and hence this work process is available for the execution of next task.

Hope this is going to help you. Please let me know your feedback on this. Thanks.

[former_member730503]

Hi any resolution on this issue. We also got the same error in production recently where the work process is showing ok but it gave error and when we reprocess the telegram from incoming buffer it worked fine. Not able to pin point the root cause. Thanks.