Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from R. N. Wilhite on Mar 21 at 4:41 PM 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
| | | ---------------Original Message---------------
From: R. N. Wilhite
Sent: Wednesday, March 21, 2012 3:17 PM
Subject: Subsequent RFC Calls Fail to Update DB
I have an RFC that is issuing an update through TCODE FB09, to BSEG-SGTXT. The first time after the user logs into SAP that the RFC is called, everything goes fine. There after, it always fails.
This failure did not start happening until the users machine went from XP to Win7. Has anyone seen anything similar that could help me refocus my search for an answer. I've been bashing on this for a week to no avail... No notes that I can find. The RFC doesn't even return a failure...
Neal |
| Reply to this email to post your response. __.____._ |   _.____.__ |
