Structural Authorizations

[Claude Bourque]

Mike,

We use it for MSS purposes and Admin assistants that have reporting
access to their "own" org structure. Since some of these have R/3 access
we don't want them running reports for other areas.

WF piggybacks on this as far as if someone forwards you a workitem, you
can't approve it unless you are structurally authorized to do so.

We do have HR taking care of this.

We're on 4.7, EP 6.0

Claude

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mike Pokraka
Sent: September 19, 2007 7:19 AM
To: sap-wug at mit.edu
Subject: Structural Authorizations


Hi Wuggers,

Quick opinion poll on the use of Structural Auths: Do you use it? How
heavily is the WF team involved - or is it all taken care of by HR? Does
anyone use them *only* for WF?

Background: ECC 6 client wants business units to maintain their own
organizational data. So I'm thinking give then am org chart with
structural auths and away we go.

The issue is structural auths can become quite hairy and I've never used
them without HR. In other words, I've always had an HR consultant/team
to
take care of the nasty stuff :-)

Here we have no HR whatsoever and I'm wondering whether structural auths
are the way to go or if it will massively overcomplicate things and/or
throw the security folks into a fit. Initial tests seem to indicate no
major problems, but I'd just like to get some input nevertheless...

Cheers,
Mike


_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
====================================================================================

La version française suit le texte anglais.

------------------------------------------------------------------------------------

This email may contain privileged and/or confidential information, and the Bank of
Canada does not waive any related rights. Any distribution, use, or copying of this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediately from
your system and notify the sender promptly by email that you have done so. 

------------------------------------------------------------------------------------

Le présent courriel peut contenir de l'information privilégiée ou confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient par une
personne autre que le ou les destinataires désignés est interdite. Si vous recevez
ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à
l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre
ordinateur toute copie du courriel reçu.