Concurrent idocs error .

[alejandro_sedanogonzlez]

HI,

We are having a big problem with the WMMBXY idoc.

Pi send multiple idocs to the R/3 system in the same second. In the we02 we can see the following error for exactly half of the idocs received (one works fine, the next one fails, the third one goes fine, the fourth one fails again, etc.....):

Function module MB_CREATE_GOODS_MOVEMENT cannot be executed.

The function module MB_CREATE_GOODS_MOVEMENT is called up for the second time. After it was called up the first time, the function module MB_POST_GOODS_MOVEMENT was called, but a COMMIT WORK was not carried out in the calling program.

The partner profile is configured with the "Trigger immediately" option selected. Processing the idocs with a Background task (RBDAPP01) and with the package size= 1 works fine (A package size = 5 produces the same error).

It looks like the system is trying to process all the idocs at the same time, and we are getting some database lock. Is there anyway to make R/3 to process the idocs one at a time without launching them in a  background program? We need to process them "online", as soon as they arrive.

Thanks in advance for your help.

[michael_kozlowski]

Serialization of IDoc as described in SAP note 752194 may be an appropriate solution (setting a unique serial number in the IDoc header record in field EDIDC-SERIAL).

[alejandro_sedanogonzlez]

Hi Michael, and thanks a lot for your answer.

Adding the value to this header record does not solve our problem.

If the partner profile is configured as "trigger immediately", I have the same error.

Also in the 752194 note, I cannot see any reference to the EDIDC-SERIAL field. Am I missing something?

[JL23]

Have a look into OSS note

65954 - Error processing IDocs in WM-LSR / MM-MOB

https://launchpad.support.sap.com/#/notes/65954/E

It explains that the function module is not capable of mass processing

gives further a good background on the IDOC processing and the settings