Customizing issues with WF-BATCH password after client copies.

[Rick Sample]

We have Training clients set up. They get client copied once a week for new classes.
Every time we do these client copies, we have to go into all the training clients and 
reset the pwd for WF-BATCH. Why?
 
>From what I read:
We have to create a logical destination in transaction SM59 (typ 'L') called workflow_local_<client>. 
Looks like they are there:
WORKFLOW_LOCAL_500
WORKFLOW_LOCAL_511
...
 
User-ID: WF-BATCH, password: the same as in SU01 for user wf-batch. 
User wf-batch have to be a 'SYSTEM' User in SU01.
Confirmed. 
 
I have a question. Is the SU01 password for WF-BATCH the same as the WF-BATCH password 
in SWU3 customizing for the RFC?  I thought they were the same.
 
I looked at the document for the "Create logical destination for tRFC":
>>The logical RFC destination "WORKFLOW_LOCAL_xxx" is created automatically. 
>>If this logical destination did not yet exist, a user is requested (including password). Specify the background user 
>>WF-BATCH, which must have been created in the current client.
The "If this logical destination did not yet exist, a user is requested (including password)." raises a question.
We are wiping out (client coping) our training boxes. If this is so and WORKFLOW_LOCAL_511, 512, etc, do not 
exist yet, would this be a reason as to why I have to reset / sync WF-BATCH?
I am just taking a stab at understanding how this works.
 
 
4.6c
Thanks!