Call Transaction Update Option :synchronous

[Former Member]

Hi all.

I have qeusiton related to call transaction synchronous mode.

Question is, how far the parameter 'S' gurantee synchronous update in the call transaction bdc.

I went through some of the related threads, and found similar one but did not reached to conclusion what i wnated to know.

I think my question is similar to the one below.

Within a program,

1.created material master using call tran update option S.

2.next process, select material record created step1 from material master table.

what happen is step 2 fails.

It seems database commit is not synchronous.

is it due to oracle commit performance?

May be program proceeds next step when commit was issued at oracle level.

But data base is slow to process update physical table entry after commit issue.

And step 2 process select statement is issued before end of actual DB updade.

(I am not familiar with oracle so this may be pointless...)

[Former Member]

check if call transaction does not return an error.

[Former Member]

it is not returning error.

I traced the program and the result shows 2 update process.

One for material master related table and the other for history related tables.

And if I insert wait commands it is fine. But interms of performance, this solution is not good at all.

So if someone had same kind a experience to share, i will be gratefull.