Re: How to check which causes locking in masterdata loading

Hi guys,

I asked the BASIS about this and said that the locking occurs because the loading process already reached the maximum number of locking argument in our system which is 3600..They said that it's already the maximum that they can give to the current setup of the server..

That answers why the loading stops at around 3.5 million+ records, as I have said in my first post, since each package currently processes 1000 records (1000 * 3500 = 3.5 million)..

So, I am thinking of increasing the number of data processed per package..How can I do it? Since the package size cannot be adjusted in the DTP of this object..

Thank you..

Loed