RFC Destination Settings for Workflow

[Rickayzen, Alan]

Hi,
"Synchronize passwords" in transaction SWUB does simultaneously set the RFC
destination and user record to the password that you have typed in. I
verified this in 4.6D.
 
The test-RFC-destination feature uses a different algorithm to SWU3.
Unfortunately this routine has been corrupted and ALWAYS fails (except in
early releases). In other words, do not use the RFC test in SWUB, rely on
SWU3 instead. In fact, don't use SWUB for anything other than synchronizing
the passwords.
 
In later releases a test was derived for SWU3 that did not involve user
interaction. So the warning "not yet tested" no longer reappears every time
you logon. In fact SWU3 does test the RFC connection every time it is
called, but it does so discretely.
 
If someone has set up an RFC destination that does not use a logical
destination you will indeed see a red traffic light in SWU3. However, most
people doing this are experts (squeezing more performance out of the system)
and will have included a very rude comment in the RFC destination saying
do-not-touch. The next Basis release (6.10) logs changes that are made to
the workflow customizing (including userid and date of changes).
 
Yes, client copies can cause problems. SWU3 (pre Release 6.10) does not
overwrite data so if the wf-batch user already exists its password will not
be reset to match that of the RFC destination created. The "synchronize
passwords" in SWUB is a Godsend in this situation.
 
*************
My approach to RFC destination problems is:
 
1. Run the verification workflow. If it works then leave everything as it is
and go home.
 
If the verification fails:
 
2. Check the RFC destination to see if there's a do-not-touch comment in it.
If there isn't then delete it.
 
3. Run the auto customize in SWU3 to create a new destination.
 
4. Synchronize the passwords using transaction SWUB .
*************
 
Alan Rickayzen
 
 
 
 
 
 
-----Original Message-----
From: Rob Bates [mailto:rob.bates at itnetplc.com]
Sent: Mittwoch, Juli 25, 2001 10:53 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: RFC Destination Settings for Workflow
 
 
Weidong,
The 'Synchronize Passwords' button does not make the passwords for the
WF-BATCH
user and the RFC destination the same - it simply means that if they are the
same, then any password change for WF-BATCH will update the RFC destination
password at the same time.
 
To get the passwords in line from the start, you have to make sure that the
password entered for WF-BATCH in SU01 and the password entered on the
'Create
logical destination for tRFC' transaction are the same (this may require you
to
change both passwords on each screen).
 
If the new client was created as a copy from client 000, then the
auto-customize
function will do all this for you. However, you may find that the new client
was
created using a client copy from another client (e.g. development) or using
homogenous or heterogenous system copies - in this case the WF-BATCH id will
already exist with its password from the previous client, so the
auto-customize
doesn't completely work.
 
Hope this helps,
Rob Bates,
eBusiness & Workflow Consultant
ITNET plc.
 
To:       SAP-WUG at MITVMA.MIT.EDU
cc:        (bcc: Rob Bates/ITnet)
From:     weidong chen <weidong_chen_cn at yahoo.com>
Date:     07/25/2001 02:42:01 AM
Subject:  Re: RFC Destination Settings for Workflow
 
 
 
Hi Everyone,
 
We are in the verison of 4.6C.
 
I am also facing such problem about RFC Destination
Settings for Workflow .
 
When AutoCustomizing the 4.6C workflow environment
under transaction SWU3,
the RFC destination continues to show the message 'RFC
destination has incorrect password'.
 
when in 'Create logical destination for tRFC',click
the icon 'Synchronize Passwords'.
there is no error.However, when I do a test on the RFC
destination, it shows that
the ping was performed unsuccessfully and that the RFC
destination for SAP Business
Workflow is fully configured.
 
What am I missing?
 
Also, am I correct to assume from this message that
WF-BATCH and password are fine
since SAP did not prompt me for either one during the
test?
We currently have destination WORKFLOW_LOCAL_420 set
up on 4.6C.
 
As a side note, when user another user 'Mzhang' test
shows that the RFC has been configured completely.
 
Any reply will be appreciated!!!
 
Thanks,
Weidong Chen
 
 
 
 
 
****************************************************************************
*******
http://www.itnetplc.com
http://www.itnetplc.com/eb  -  Click here to see ITNET's ebusiness
capabilities
 
Any opinions expressed in this email are those of the individual and not
necessarily those of ITNET plc and/or its subsidiaries. This email and any
files transmitted with it, including replies and forwarded copies (which may
contain alterations) subsequently transmitted from ITNET plc and/or its
subsidiaries, are confidential and solely for the use of the intended
recipient. If you are not the intended recipient or the person responsible
for delivering to the intended recipient, be advised that  you have received
this email in error and that any use is strictly prohibited.
 
If you have received this email in error please notify ITNET Customer
Service Centre by telephone on +44 (0)121 683 4043 or via email to
csc.com at itnetplc.com, including a copy of this message. Please then delete
this email and destroy any copies of it.
 
****************************************************************************
*******