while processing ALEAUD - "Error when locking the audit statistics"

[SujitSK]

Hello,

I am sending out IDOC for HR data and then prcessing ALEAUD inbound idoc immediatley (setting is done in WE21 partner profiles).

While processing these incomming idocs, I am getting this error "Error when locking the audit statistics for P01LOGSYS1 IMTIMEDEP HRMD_A" for few idocs. e.g. out of 1000 for 100 idocs this error will happen and IDOC goes to status 51.

If I try to process thes idocs ALEAUD using background processing and if I schedule 2 jobs at a time then I will get same error and IDOC goes to status 51.

Can someone help me out?

[DavidLY]

Hello,

First of all, check the following SAP note 573991 and change to background

processing (WE20) as suggested and post these idocs with RBDAPP01.

although the message type is different and the reason is simple.

Note 1333417 gives explanation regarding to collection mode, you could

have a look also.

Regards,

David

[SujitSK]

Hi

I tried processing the idocs in background processing as you have suggested using program RBDAPP01 (inbound).

There are 2 options in this program serial processing and parallel processing. When I select serial processing everyhting goes smooth but it takes long time. But when I select parallel processing I get same locking error mentioned above and only few idocs will get processed successfully with status 53 and all other will error out with status 51.

If I schedule 2 different jobs in background program RBDAPP01 (inbound) using serial processing then same thing will happen. only few idocs will get processed successfully with status 53 and all other will error out with status 51.

And I will get locking error ....

Note 1333417 says, " these IDocs will be processed via background runs of report RBDAPP01 \ RSEOUT00 (using background work processes) in batch mode leaving dialog work processes free for users and mission-critical processes. Hence you will not encounter the resources problems you are currently experiencing. The only other option would be to try increasing the number of available dialog work processes. The number of dialog processes must be greater than or equal to the total of the number of update and background processes per application server and must be configured across all operation mode

switches (see SAP note 74141). *However when there are a large number of IDocs being processed this is not a practical solution."*

Does that mean there is no possoble solution for this issue. If I increase dialog work processes will it be helpfull ?

[DavidLY]

Hello,

I think it should be helpful.

Regards,

David