Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from Pierre_Richer on Mar 14 at 10:11 AM Hi Robert,
If there is a way for you to use the standard lock objects in SAP, I would
first try to do this.
It depends to how long it takes to do the updates.
Suggestions.
1 - Package your updates an execute them in an RFC or Update Task, or even
using "starting new task"
2 - Try to lock the objects. In a loop, try to lock until they are lock.
3 - Once lock is ok, perform the updates.
4- Commit if everything is ok, or rollback if not.
4 - Unlock
5 - Send by email any errors that could occurs
6 - In case of errors, you can even try again.
Regards,
Pierre
| | | ---------------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. __.____._ | In the Spotlight Become a blogger at Toolbox.com and share your expertise with the community. Start today.   _.____.__ |
