Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from ERPel on Mar 16 at 9:15 AM Hello Pierre,
The reason why I want to use background task is to enable a repeat try if something went wrong.
My assumption is that if the update fails and I raise an error that the LUW will be placed in sm58 where it could be repeated.
However my call in background task seems to do nothing.
You are right starting new task worked - in success case it did an update but when the object was locked there was no hint that it failed. So no chance to try again.
Btw. I do the commit in FM2 to enable the raise error.
Robert
| | | ---------------Original Message---------------
From: Pierre Richer
Sent: Friday, March 15, 2013 1:24 PM
Subject: [Possible SPAM!] In Background Task
Robert,
By using In background task, don't forget that your RFC will be called
after a COMMIT WORK is done, not right after the CALL. If there is no
COMMIT in FM1, a COMMIT will be done at the end of current process and FM2
will be started after.
For testing, try using STARTING NEW TASK instead and you will see right
away in SM51 if something is running.
Pierre, |
| Reply to this email to post your response. __.____._ |   _.____.__ |
