IDOC locked

[vkaushik82]

Hi All,

We have a scenerio in which IDOC once reaches SAP system gets locked because many IDOC are created at a time.

Is ter any way we can handle this locking of IDOC.

Please advice

Regards,

Vikrant

[former_member216353 · Accepted solution]

Hi Vikrant,

Try to increase the packet size at the Partner Profile for this Idoc Type.

This will basically help you in processing bulk idocs at SAP. Please try this option and let us know the results.

Regards,

Younus

[Former Member]

Could you explain how you solved the issue so that others facing the same problem can take the benefit of it.

[Former Member]

> We have a scenario in which IDOC once reaches SAP system gets locked because many IDOC are created at a time.

To handle this you can change the Processing mode in WE20. Under your inbound parameters select "Trigger by background program" radio button and then schedule the job to process them.

So by this way when your idocs will come into SAP they will be in status 64 and later they will be processed by the job.

These are the program names which you have to use in your jobs.

RBDAPP01 This will process the IDOCs which are ready to be processed (status 64)

RBDMANI2 This will process the IDOCs which went into errors

So you have to schedule 2 jobs.

This is the best way to handle this kind of situation. So just try and let us know.

P.S. Scheduling a job is one time activity for this. You job will keep on running at defined time interval to process the IDOCs.

Regards,

Sarvesh

[Former Member]

Hi Vikranth,

I had also seen similar issues while working with MATMAS,DEBMAS and CLFMAS IDOC's. from One variety 3

IDOCs used to get triggered and there were times when we had these locking issues in SAP.

I remember it was solved by SAP team by modifying the ABAP code , they have used some logic to delay the

idoc posting using wait logic.other option suggeted were using some background jobs in sap.

Also we did some R&D to use EOIO (using a simple BPM) to serialize the posting ,but it didn't worked out i think.

The changes in the FM done by ABAP team did the trick at last.So would suggest you to check with ABAP counterpart if he can include some delays while accepting the idoc.

Regards,

Srinivas

[Former Member]

Hello Srinivas

I am facing the same issue . Could you please tell me the OSS note number or the place where SAP has modified the code to write wait logic.

We have use immediate processing so will packet size really matter ?

Background Job will have some delay!!

Please Suggest!!

Thanks

Samyak

[sugata_bagchi2]

Hi ,

can you trace the user ? you can just get the user in sm12 and ask him to release the same . just need to release the transaction of movement, you can also reprocess the IDocs from the program - RBDAGAIN.

Thanks

Sugata