topic Re: Saving data in call transaction in Application Development and Automation Discussions

Saving data in call transaction

Former Member — Thu, 10 Apr 2008 20:01:35 GMT

Hi,

I' am using call transaction to update certain data of employees (PERNR). After that I' am trying to lock the same pernr. But sometimes I' am not able to lock the PERNR. The reason it seems the transaction in call statement is still executed. How to complete the execution of call transaction and then proceed further?

Thanks in advance.

Aravind

Re: Saving data in call transaction

venkat_o — Fri, 11 Apr 2008 02:10:29 GMT

Hi Aravind, 1.Which update mode you are using whether it is A or S. If you use Update mode 'A' Asynchronous Update. It will be ok. 2.How are you locking the employee? in the same transaction call when updating infotype itself , are u locking ? If yes, I think it is somewhat problematic. Instead update the infotype and again use Call transaction to lock the employee. Regards, Venkat.O

Re: Saving data in call transaction

manubhutani — Fri, 11 Apr 2008 09:01:27 GMT

ther's nothing related to transaction

use FM -BAPI_EMPLOYEE_ENQUEUE

to lock the pernr before updating the employees information

then use call transaction method.

Please reward points

Re: Saving data in call transaction

venkat_o — Fri, 11 Apr 2008 10:05:29 GMT

Are you locking the pernr or locking the record of pernr for the infotype ? Regards, Venkat.O

Re: Saving data in call transaction

Former Member — Fri, 11 Apr 2008 19:09:01 GMT

Hi Venkat,

Right now, I' am using synchronous mode of update.

It is a program and the 'call transaction' is done first which will update infotype records and immedietly after call transaction I' am locking the employee.

Also can you let me know why you felt asynchronous mode will work aganist synchronous mode.

Thanks in advance.

Aravind

Re: Saving data in call transaction

venkat_o — Fri, 11 Apr 2008 20:07:21 GMT

Hi Aravind, When I gave message i thought differently. Synchrounous update only right, because the called transaction waits for any updates that it produces to be completed. Execution is slower than with asynchronous updating because called transactions wait for updating to be completed. However, the called transaction is able to return any update error message that occurs to your program. It is much easier for you to analyze and recover from errors. I still want to know whether you are locking the the employee no after updating infotype or locking the record of the infotype. because we have lock indicator for infotypes. Regards, Venkat.O

Re: Saving data in call transaction

Former Member — Tue, 15 Apr 2008 13:51:53 GMT

Hi Venkat,

I' am locking the employee number.

Thanks,

Aravind

Re: Saving data in call transaction

Former Member — Tue, 27 Oct 2009 02:59:03 GMT

Solved