call transaction system lock error

[Former Member]

Hi friends,

i am uploading data to some transaction using call transaction method with synchronus update.

when i schedule the same program as 2 jobs in the back ground (splitting the file in to 2) most of the records are failed with the error 'SYSTEM_LOCK'.....

any suggession on this? thanks

[Former Member]

After the first job finishes , then only schedule the 2nd job and checkout if it works

[Former Member]

if it is one after the other then works very much fine.

here our idea is to reduce the upload time, so we want to run 2 jobs simultaniously.

[Former Member]

Hi kiran,

You can do the coding like, after executing the First File then only start the Second file,

Normally this won;t happen, i mean the error only comes when you are using the same values in the same time, so may be your filwe is contains the same, so it is better run the first file, after completing the first one then only start the processing the second file

Regards

Sudheer

[Former Member]

my program is taking 8 hours to upload 100,000 records, so my idea to break that into 2 jobs so that we will reduce the time.

any ideas

[Former Member]

Instead of call transaction, use the session method. Run as many sessions simultaneously as you want. You will still get lock errors, but you will be able to resolve them by re-submitting the error sessions. Some may have to be submitted more than once.

Rob

[Former Member]

thank you very much, could you tell me normally how much time will take to upload 100 000 records using LSMW?? the transaction has 12 screens to process.

thanks Rob

[Former Member]

That would depend on a number of factors - the transaction you are using, your hardware platform and other system activity while the load is going on. So no, I can't tell you how long this will take.

But if you load say 1,000 records into your QA system (and multiply by 100), this should give you a rough idea of how long. The Production load will take more or less time depending on hardware and system usage.

Rob

[Former Member]

thank you for the information Rob and ramesh.

[Former Member]

You're welcome Kiran. If your question is answered, please close the thread.

Rob

[Former Member]

normally when call transaction is used it locks the transaction and starts posting the data so that duplicates doesnot occur. What u can do is first run the first file and after it gets finished run the second file. This way it won't give any errors and also almost all records will be posted to SAP.

[Former Member]

thanks to everyone,