SAP_ALL SAP_NEW

[Madgambler]

Presumably you have tried regenerating SAP_ALL in the target system?

Worth a mention just in case somebody forgot?

Mike GT

Sent from my iPhone

On 2 Jun 2011, at 20:41, Edward Diehl <edwarddiehl at hotmail.com> wrote:

> Thanks, Eddie, but therein lies the problem.  We've applied the note and we are still left with tasks failing because of no-authorization - and these failed to show up on the Security's authorization trace.
> 
> As I asked, is anyone out there successfully using workflow where WF-BATCH does not have SAP_ALL AND SAP_NEW?
> 
> Ed
> 
> From: eddie.morris at sap.com
> To: sap-wug at mit.edu
> Date: Thu, 2 Jun 2011 20:54:19 +0200
> Subject: RE: SAP_ALL SAP_NEW
> 
> Hi Ed,
> 
>  
> 
> Take a look at note 1251255 which introduces SAP_BC_BMT_WFM_SERV_USER. It takes care of the authorization for the workflow runtime but you still need to add application specific authorizations.
> 
>  
> 
> KBA 1574002 also gives details.
> 
>  
> 
> Regards,
> 
> Eddie
> 
>  
> 
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Edward Diehl
> Sent: 02 June 2011 19:33
> To: sap-wug at mit.edu
> Subject: RE: SAP_ALL SAP_NEW
> 
>  
> 
> Is anyone out there successfully using workflow with WF-BATCH carrying something other than SAP_ALL & SAP_NEW security roles?
> 
> I'm sure many of you have confronted this issue.  I would be interested to hear your experience(s).
> 
> Thanks,
> Ed
> 
> 
> _______________________________________________ SAP-WUG mailing list SAP-WUG at mit.edu http://mailman.mit.edu/mailman/listinfo/sap-wug
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20110602/b89f1d66/attachment.htm