BAPI_TRANSACTION_COMMIT with WAIT = 'X' does not work. Any suggestions?

Question

1) 'BAPI_PRODORD_CREATE'
2) CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
        EXPORTING
          wait = 'X'.
3) BAPI_PRODORD_CHECK_MAT_AVAIL
Sometimes it works fine, other times the BAPI_PRODORD_CHECK_MAT_AVAIL passes an error that says the "Order does not exist."
I tried a "Wait up to 10 seconds".  That makes the processing go extremely slow and even that doesn't make it work 100%.
Any suggestions?

Answer 1

From what I found,
1) the commit_wait is automatically ran in many BAPI's, but not all.  It is oftern duplication to add it yourself
2) The commit_wait logic appears to end on the application server.  Once the application server passes the commit to the database then the application server thinks it is done and continues processing the program.  In reality the database is still processing and the record is still locked in the database.  This means the commit and wait code is not a 100% guarantee.
Solution:
1) Function module ENQUEUE_READ (or transaction SM12).  This checks to see if the database lock is in place.  Set a break-point in the code and in a separate window run one of these.  You will see the locks.  Now you know the lock condition add some ABAP code to Do loop at reading the results on the relevant lock. Exit and continue processing when the locks are removed.  See my comments in step 2 about a wait a few seconds between loops and providing an exit time to avoid infinite loops.  I think solution 1 is better than solution 2, even though I implemented solution 2. 
or
2) loop on a select from the database (you need to know the table being updated by the bapi to do this).  exit the loop when the record is inserted.  This is what I did since I hadn't found the solution in step 1 when I implemented my fix.  Don't put a wait statement in the loop though.  The wait is taxing on the database because it executes a commit.    I used "get time field" to handle a 2 second wait between database reads.  I also used this to exit after 30 seconds to avoid an infinite loop.
Below is some sample code of solution 2.  I used it in between a BAPI production order create and BAPI check production order material availability.  I was getting an error saying the production order hadn't been created in the material availability check when in fact it had been created but just not committed to the database.
  DO.
Only select from DB every two seconds
      CLEAR do_time3.
      do_time3 = do_time1 - do_time2.
      IF do_time3  GT gc_000002.
* Determine if confirmation has committed to database
        SELECT SINGLE aufnr FROM resb INTO lv_aufnr WHERE aufnr = g_aufnr AND
                                                          xloek = space   AND
                                                          xwaok =  gc_x    AND
                                                          kzear =  gc_x    AND
                                                          matnr IN r_range.
        IF sy-subrc EQ 0.
          EXIT.
        ENDIF.
      ENDIF.
      GET TIME  FIELD do_time1.
      do_time2 = do_time2 + gc_000002.
      do_exit = ( do_time1 - do_time ).
      IF do_exit GT gc_000030.
        EXIT.
      ENDIF.
      CLEAR do_exit.
    ENDDO.