asynchronous update

[Former Member]

Hi to all Guru's,

1.can anybody explain me what is asynchronous update?

2.Which one of the following is an example of an asynchronous update?

a) insert wa into ztable.

b) call function 'update_table' in update task.

c) update ztable from ztable.

d) modify ztable from wa.

Thanks

Priya

[ThomasZloch]

which test are you taking there, my friend?

async update -> process A triggers a DB update in process B, but does not wait for process B to finish.

2.b)

[Former Member]

Hi Thomas ,

can you explain me what is asynchronous update?

it will be a fever for me

Thanks

Priya

[Former Member]

hi,

asynchronous update means at single shot we can update 'N' no of records to database...

reward points if helpful...

[Former Member]

Hi maddipatla,

can u tel me Which one of the following is an example of an asynchronous update?

a) insert wa into ztable.

b) call function 'update_table' in update task.

c) update ztable from ztable.

d) modify ztable from wa.

Thanks & Regards

Priyalatha

[Former Member]

Hi,

B&C.........

[Former Member]

Hi ,

The perfect solution is Calling the Update Function module i.e b.

Because,

whenever u use a standard update Function module, it will update the data into all the relevat tables , with validations .

where as the other options like insert/update /modify will change/insert the data from datbase table without any validations.

Revrt back if any issues,

Regards,

Naveen

[Clemenss]

Hi,

I'm so happy I found the answer:

[sap abap asynchronous update|http://www.google.com/search?num=100&hl=de&newwindow=1&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=sapabapasynchronous+update&spell=1]

Regards,

Clemens

[Former Member]

hi

good

Synchronous calls are slower but should be used for transactions that are updating the database because control is not passed back to the program until a successful database commit (or rollback) has been executed. Note this the real SQL commit at the database level not the ABAP command COMMIT WORK. Synchronous calls will set the return code (sy-subrc) if an error is encountered. There are actually two synchrounous update modes:

'S', Synchronous update mode makes database entries describing the updates to be done and an update task (potentially running on a different computer) reads those database entries, does the update, and then deletes the entries describing the update task.

'L', Local update mode describes the updates to be done in the memory of the current process. No entries are made in and then deleted from the database describing the update task.

Asynchronous calls are the default if the UPDATE parameter is not specified. Asynchronous calls do not effect the return code (sy-subrc).

Note - This is opposite of how synchronous/asynchronous workflow tasks behave, in the sense that control is returned to the workflow in a synchronous step even if there is no commit or rollback encountered!

c-> updte ztable from ztable is the example of asynchronous update.

thanks

mrutyun^