topic abap insert commit issue in Application Development and Automation Discussions

abap insert commit issue

former_member229036 — Mon, 03 Feb 2014 09:30:17 GMT

Dear Guru!!

i have two issue regarding commit issue.

#1. there is one RFC for synchronous has insert statement and then commit

but disappear data with mass calling RFC, it seems to be not committed .

insert into zcct002 values gs_log.

commit work.

#2. there is one RFC for receiving data.

firstly execute select statement for getting data inserted by above #1 RFC .

but when selecting performed ,, Sometime ABAP does not pick it up from that table even though a record inserted into table at almost same time.

wait up to 1 seconds for 3 times, it does not work. sometime comes to same issue

if sy-subrc <> 0.

do 3 times.

wait up to 1 seconds.

select single *

from zcct002

into gs_log

where modid = gs_appr_in-modid

and objkey = gs_appr_in-objkey

and docid = gs_appr_in-docid.

if sy-subrc = 0.

exit.

endif.

enddo.

endif.

Re: abap insert commit issue

former_member223133 — Mon, 03 Feb 2014 10:32:47 GMT

Hi David,

It seems like an issue with COMMIT. Try with the below options.

In 1st RFC FM, check sy-subrc after insert statement and commit. Then write a statement "wait up to 3 seconds."
For 2nd RFC, increase the wait time for 3 seconds.

Thanks

Gangadhar

Re: abap insert commit issue

ThangaPrakash — Mon, 03 Feb 2014 11:40:24 GMT

Hello David,

Try to close the first RFC connection after the Insert and commit using the FM "RFC_CONNECTION_CLOSE".

Might be first RFC is not closed and it means the execution has not completed, so the data has not been updated in table or the RFC connection might have stuck. So it is better you close the first RFC connection after the insert

Regards,

Thanga Prakash T

Re: abap insert commit issue

Katan — Thu, 06 Feb 2014 21:16:42 GMT

Have you tried "commit work and wait"? If you need these records to be commit before processing any further, then you should use this. It will ensure your high priority updates are executed synchronously and processing will not continue until the update is complete. Note your RFC will hang until this has happened.

As you are using just "commit work". This pushes the commit on an asynchrounous queue and it will be processed whenever the system has bandwidth to do so. The time it takes to perform this is relative to the available load on the system and the number of processes allocated to updates.