Problem with ALE link

[Branco_Marcina@national.com.au]

Hi David,
One option could be to create a variant for RHALEINI (the ABAP that is run
by transaction PFAL) so that the Transfer mode of update is selected and
also protected (to do this change the attributes of the variant).
You would then copy the transaction PFAL to your own, say ZPFAL, and for
that transaction start with the new variant.
 
>From then on only give the users access to use ZPFAL.
 
Regards,
Branco Marcina
ISI Project
P&C ITA Team
 
( +61 3 8641 6815 { 0418 958 002 }   2  +61 3 8641 6780              :
branco_marcina at national.com.au
 
National Australia Bank Limited
Desk 54, 14th Floor/ 505 Bourke Street
Melbourne, Victoria 3000
 
 
 
 
 
"David E. Yung" <davideyung at yahoo.com.ar>@MITVMA.MIT.EDU> on 19/11/2003
09:54:25
 
Please respond to SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
 
Sent by:    SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
 
 
To:    SAP-WUG at MITVMA.MIT.EDU
cc:
Subject:    Problem with ALE link
 
 
Fellow workflowers,
 
in my client, we have the Org. Structure set up in a development client and
it is sent via ALE to the Testing/Production clients.  I have also
distributed an entry in OOTR for S/1001/A008 so that the users assigned in
development are not imported in the Testing/Production environment.
 
Security profiles are also assigned via the Organizational Structure so
that
roles are assigned to positions in development.  When a user is assigned to
a position in Production, they automatically inherit the roles assigned to
the position.
 
Now, the problem that we are having is that if you run transaction PFAL in
Update mode, there's no problem.  In this case the users in Production are
not touched by the update.  However, if a user runs PFAL in Insert mode by
mistake (has already happened), the users that were assigned to the
structure in Production are all deleted.  Since the default in PFAL is
Insert mode, it is possible that this may happen again in the future.  As
you can imagine, the impact is quite great, as the users in production
suddenly loose all access rights...
 
My question is, does anybody know if it possible to restrict it so that
Insert mode is not available in PFAL or is there any configuration that
will
help me prevent the users being overwritten in Production when PFAL is run
in Insert mode?
 
Thanks a lot and apologies for the extent of this message.
 
 David Yung