Skip to Content
avatar image
Former Member

Delayed in updating table VBRP?

I need your inputs. There's an implicit enhancement after commit in tcode VF01. In the enhancement, there's a wait statement (wait up to 10 seconds) and followed by select statement from table vbrp. During first run of tcode VF01, it seems that table vbrp is not yet updated even though there's a 10 second pause after commit (select from vbrp ---> sy-subrc NE 0). However, during the succeeding runs of tcode vf01, select from vbrp ---> sy-subrc EQ 0. How could that be? Is there any suggestions?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Oct 13, 2016 at 03:28 PM

    Hi

    What do you need to do?

    Add comment
    10|10000 characters needed characters exceeded

    • +1. It's impossible to answer intelligently without understanding what is the purpose of such enhancement. Seems like a rather bad design to me. VF01 (create) and already a record should be in VBRP for something, wtf?

  • Oct 13, 2016 at 03:48 PM
    -1

    Check this blog out https://blogs.sap.com/2016/09/14/waiting-for-lock-objects-to-release-using-lock-modes-u-v-w/

    I have had similar issues - not quite 10 seconds - but using the ENQUEUE with Mode U or V and the Wait seems to be better for performance (than using the WAIT statement) and will accurately proceed when the previous commit is done.

    Add comment
    10|10000 characters needed characters exceeded