‎2008 Feb 06 3:03 PM
I'm having a problem which seems to stem from the Commit Work and Wait
command. If I try changing certain quotations using va22 the process
appears to work , however on reopening the quote no changes are made. I
get an error message in the update request sm13 ; ( 01 289: There is no
address data for user KSINCLAIR) [this is the person who originally
created the quote]). I also get this error when using bapi
quotationchange followed by bapi_transaction_commit. The quotation
change is successful but the commit fails hence the changes never get
made. I've spent a considerable amount of time trying to debug to find
this but am not doing too well. Any help or info would be greatly
appreciated.
‎2008 Feb 07 6:59 AM
Hey,
You say the change is succesful and the the commit fails. The way I
understand it, however, the problem is that you change quotations that
have a reference to user KSINCLAIR. Somewhere in the update modules a
check is being performed on address data for user KSINCLAIR, and this
data is not maintained. This leads to an A-message, which rolls back the
complete update and sends the SM13-message.
If you are not familiar with Update Modules (V1 updates) in relation
with Commit Work statement, I think you should first read the
documenation on that issue. Basically, what happens is that VA22 calls
function modules that are stored temporarily in an update queue. The
statement COMMIT WORK triggers the execution of these function modules.
Regards,
Chaitanya.
‎2008 Feb 06 3:27 PM
Have you checked the address data for the user? Can you add it?
Rob
‎2008 Feb 07 6:59 AM
Hey,
You say the change is succesful and the the commit fails. The way I
understand it, however, the problem is that you change quotations that
have a reference to user KSINCLAIR. Somewhere in the update modules a
check is being performed on address data for user KSINCLAIR, and this
data is not maintained. This leads to an A-message, which rolls back the
complete update and sends the SM13-message.
If you are not familiar with Update Modules (V1 updates) in relation
with Commit Work statement, I think you should first read the
documenation on that issue. Basically, what happens is that VA22 calls
function modules that are stored temporarily in an update queue. The
statement COMMIT WORK triggers the execution of these function modules.
Regards,
Chaitanya.
‎2008 Apr 21 10:20 AM
Hi Reethu,
I am also facing the same problem while changing PO through Me22n.
Can u please let me know how u have solve this problem.
Thanks in Advance,
SVS