Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from sapwes on Mar 15 at 1:52 PM Robert:
You should be able to call the same enque function modules that the BAPI is using before calling the BAPI. I'd modify Pierre's suggestion only that in step 2 - attempt to lock using the appropriate enque FM(s) , if lock is granted then unlock and call the BAPI.
As a note, you haven't told what BAPI you are calling. Help can be more specific if you are
wes.
| | | ---------------Original Message---------------
From: Robert Seehafer
Sent: Thursday, March 14, 2013 6:02 AM
Subject: Asynchronous Update of Objects (Batches)
Hi Experts,
We have a process where specific objects (batches) need to be updated.
I would like to avoid that the update fails because e.g. the object is used by another user or process.
How can I archive that the system is periodically trying again to perform the update?
I am not sure if below solutions are really doing what I want (except 3)
1) Using "in background task". But I don't know if this won't already raise an unresolvable error if there is a lock on the object
2) Using "in update task". Same concerns as in 1
3) Monitor if the update was successful. If not store respective data in a z-table and implement a report scheduled by a job which is trying the update again.
I don't like option 3. Do you have any good ideas with Standard SAP?
Regards
Robert |
| Reply to this email to post your response. __.____._ |   _.____.__ |
