Triggering Workflows from SE16

[Martinek, Jerry]

Hi David,
 
If you can't seem to achieve the required access restrictions to SE16 =
via
the authorization object S_TABU_DIS then maybe in this partcular =
scenario
you should replace SE16 with either Query or Quickviewer. Use a custom
infoset with the required/desired fields (basically a view equivalent). =
This
should give you the required access and controls that you seem to need.
 
Thanks,
Jerry
 
-----Original Message-----
From: Bibby, David [mailto:david.bibby at Linklaters.com]=20
Sent: Wednesday, February 25, 2004 6:46 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Triggering Workflows from SE16
 
 
Heinz,
It's something our BASIS team are looking into. However, they need some
people to have access for support purposes. I know it seems a little =
crazy
to restrict access to the data to just a few people and then keep logs =
on
who access the data, but apparently it's for legal reasons that we need =
to
keep audit data. Rgds David
 
-----Original Message-----
From: Schmidinger, Heinz (Unaxis IT BZ)
[mailto:heinz.schmidinger at unaxis.com]
Sent: 25 February 2004 13:26
To: SAP-WUG at MITVMA.MIT.EDU
Subject: AW: Triggering Workflows from SE16
 
 
Hi Dvid,
 
can you use authorization to restrict access to table (AO ??TABU_DIS?? =
or so
if I rember right) ?
 
 
regards
 
Heinz
 
-----Urspr=FCngliche Nachricht-----
Von: Bibby, David [mailto:david.bibby at Linklaters.com]
Gesendet am: Mittwoch, 25. Februar 2004 13:08
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: Triggering Workflows from SE16
 
Michael
The requirement is to report on users and support staff accessing =
sensitive
information. We have a custom transaction that people use to view and =
edit
the sensitive data. We can amend custom transaction to log when a user =
views
data through this transaction. However, anyone who has access to SE16 =
can
easily view this data, and as SE16 is standard SAP we cannot put our =
own
code in there to log what they are doing. The reason I asked about =
workflow,
was that I thought if there was a way of triggering a workflow when =
certain
tables were viewed, I could write this information to a log table.
 
Another option is to upload an audit log file of the SQL trace, but =
this
isn't user friendly. The people using this report are special SAP users
within the firm and not technical.
 
Regards
David
 
 
-----Original Message-----
From: Michael Pokraka [mailto:workflow at quirky.me.uk]
Sent: 25 February 2004 11:58
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Triggering Workflows from SE16
 
 
You mean someone wants to be alerted when people start poking around in
things they shouldn't? If so, I would in any case only consider this to =
be a
half measure as there are many ways to look at a table without SE16....
Explain your requirement and we may be able to help. Perhaps table =
logging
is an alternative.
 
Cheers
Mike
 
Bibby, David wrote:
> Hi All,
> Has anyone ever triggered a workflow from a user accessing SE16 e.g.
triggering a workflow when accessing a particular table in SE16 ? Is =
this
possible ?
> Many Thanks
> David
>
>
>
> ________________________________________________
> This message is confidential. It may also be privileged or otherwise=20
> protected by work product immunity or other legal rules. If you have=20
> received it by mistake please let us know by reply and then delete it =
 
> from your system; you should not copy the message or disclose its=20
> contents to anyone. All messages sent to and from Linklaters may be=20
> monitored to ensure compliance with internal policies and to protect  =
 
> our business.
>
> Please refer to http://www.linklaters.com/regulation for important=20
> information on the regulatory position of the firm.
>
>