Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from horacio zapettini on Mar 21 at 4:46 PM The problem I see is that you've changed the Operative system. This may imply a change in the way threads are being treated...
As I said, we aren't working with W7 so my knowledge is limitated to some hints (things that could fail).
| | | ---------------Original Message---------------
From: R. N. Wilhite
Sent: Wednesday, March 21, 2012 4:41 PM
Subject: Subsequent RFC Calls Fail to Update DB
Thanks Horacio,
There's push back however. The original project was to increase throughput. Perhaps 50 times a day, they have to run this process. It used to be 4 transactions, 20ish screens and a lot of data mapping. The project made it 1 transaction, 1 screen, and a little data mapping. This would take it back up to 2 transactions, 6ish screens, and some additional data mapping. Additionally, it breaches security along the SOD lines, again. Not really designed to make anyone happy. If it was new, that would be one thing, but they've had it for 2 years...
So, question...
Know any techniques that cause RFC components to reset that I might not?
Neal |
| Reply to this email to post your response. __.____._ |   _.____.__ |
