Issue with BAPI & Commit

Question

Dear All,
I have been working with an assignment and facing a strange issue.
I have used the 'BAPI_SALESORDER_CHANGE' to modify sales order and then I call 'BAPI_TRANSACTION_COMMIT' with wait = X. So, this bapi modifies the sales order schedule lines and also in turn updates the info structure linked to it (In our case, say it is S800)
Immediately after this I have a select statement on S800 to fetch the records.
On debug, if I break at select statement, I get correct records from S800  but If i break one step after select it gives me different records.
I think there is some delay in updation of infostructure, hence, If i use wait statement before select for 1 sec, it works fine, but cause performance issues.
for over 15000 order items, it will wait for around 8 hours, hence, i would like to know is there any way I can avoid wait and also read the infostructure for correct records.
<< Moderator message - Everyone's problem is important. Please do not ask for help quickly. >>
Edited by: Rob Burbank on Feb 24, 2011 9:45 PM

Answer 1

Hi Chandanrs,
with COMMIT WORK (or BAPI_TRANSACTION_COMMIT) with WAIT addition, processing is continued after all high-priority ("VB1") update function modules are executed in the order of their registration and in a shared database LUW.
That means that the info structures are probably updated in low-priority ("VB2") update.
I never faced this situation but I think that the info structure should still be locked. Try to find the corresponding lock object, in a (test) run, locks may be visible shortly in SM12 lock overview.
If possible, after commit work, try to call the enqueue function with the same arguments as it is done within the BAPI processing. You should get a foreign lock error until the end of the second level update process.
while lv_locked is initial.
  call function 'ENQUEUE...
  IF sy-subrc = 0.
    lv_locked = 'X'.
  endif.
endwhile.
  call function 'DEQUEUE...
  clear lv_locked.
This lets your program wait until the info structure update is complete. Sorry I do not really know which lock object is used here. Anyway, I still do not know why you have to read the S900 directly after update.
You may also process all orders to the to set the order quantity to delivered qty, COMMIT every 1000 or so orders, put the original quantity to internal table. Then do the same for restoring.
BAPI processes run a great deal faster if you do not COMMIT after every single document. But you can't take too many because than you risk a lock table overflow.
Hope it is some help anyway.
Regards,
Clemens