WF_BATCH ID

[Tom Jull]

Ditto Martin's comments.  I would add the following:
 
1) While it does not matter what you call this user (WF_BATCH vs.
WF-BATCH), make sure that the user you specify in the logical RFC
destination matches the ID of the background user you have created.
2) While you can maintain this information via the IMG, it is not
customizing data.  Remember that you have to create the user and the RFC
destination in every system and client in your landscape.
3) Your security team should be aware that even though WF-BATCH is only
a background user, a mischievous developer could create a background
method that does destructive things.
 
Tom
 
"Martin Maguth (USA)" wrote:
>
> the wf-batch user does not necessarely have to have the sap_all and sap_new
> profiles. it is recommended to give this user the profiles though.
>
> (1) the wf-batch user is a background user. logon in dialog session is not
> possible.
> (2) the wf-batch user conducts all the background steps in a workflow.
> hence, he needs all the basis profiles, workflow profiles and most
> application profiles (i.e. posting invoices in the background etc.)
> (3) i have seen some companies who set up their own profiles for the
> wf-batch user and it works fine. the profile that is used has to be
> sufficient to allow wf-batch to conduct all the background steps that need
> to be processed during the workflow.
>
> i hope this helps,
>
> - martin
>
> -----Original Message-----
>> From: Scanlon, Christopher P. (Chris)
> [mailto:Christopher.P.Scanlon at pmusa.com]
> Sent: Friday, March 31, 2000 11:25 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: WF_BATCH ID
>
> Hello,
>
> We are bringing up a new SAP system (from 3.1h to 4.5b) in which we will be
> using Workflow....
>
> What are the reasons why the WF_BATCH id needs to have SAP_ALL, SAP_NEW
> authorization profiles attributed to it ?