on 04-08-2008 9:54 AM
Hi All
We are using a custom transaction (on a PDA) to call transaction MB1B, with movement type 201. But from time to time we get a double posting, which is highly problematic.
Can any of you come up with an ides of how this can happen? SAP does not support this.
Br
Karsten Bindesbø
Hi Venu
Your answer led me to something that turned out to be the answer to the problem. Our own program, calling MB1A, did not refresh the internal tables properly, so after posting, it tried again, and if enough IM stock, the posting was done twice. This we thought of because the double postings were allways for free stock and never from sales order stock.
Thanks for your help
Karsten
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
In custom transaction before calling MB1B, you can validate whether such an entry already exists in movement tables MKPF/MSEG. If so, a warning/error may be issued.
Thanks,
Venu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.