09-23-2005 1:01 PM
HI
When I am trying to do a repeat update on a failed V1 FM from sm13 I am getting the message 'This update request can not be carried out retrospectively'. As per the manual this message comes when we try to do a repeat update on a synchronous update. But strange thing is that info column in sm13 does not show that it's a synchronous transaction.
Moreover in the same transaction if V1 goes thru but V2 fails then we can safely do a repeat update and the system does not throw any error.
Why same standard transaction (say VL01) sometimes work in synchronous and sometimes in asynchronous update mode (as evident from sm13 log)
Regards
Saurav
09-23-2005 2:13 PM
OSS 47645 explains your problem.
Cause and prerequisites
If an error occurred when executing an update request, all SAP locks
that belong to this update request are released, and the update request
is given the status "Error". In the various SAP applications, there are
function modules that can only run if the SAP locks exist. If a
cancelled update request contains one of these modules, it cannot be
updated and the generating transaction must be re-executed. Otherwise,
data inconsistencies may appear.
09-23-2005 2:13 PM
OSS 47645 explains your problem.
Cause and prerequisites
If an error occurred when executing an update request, all SAP locks
that belong to this update request are released, and the update request
is given the status "Error". In the various SAP applications, there are
function modules that can only run if the SAP locks exist. If a
cancelled update request contains one of these modules, it cannot be
updated and the generating transaction must be re-executed. Otherwise,
data inconsistencies may appear.
09-24-2005 6:12 AM
HI
Sanjay
Thanks a lot for the help. This definitely clarifies my point.
Regards
Saurav