[16] in Management Reporting Authorizations Team
Input to SAP Authorization Strategies
daemon@ATHENA.MIT.EDU (George Petrowsky)
Thu Jul 3 01:21:46 1997
Resent-From: "Rocklyn E. Clarke" <RCLARKE@mitvma.mit.edu>
Resent-To: MRAUTH-L List Archive <mrauth-mtg@menelaus.mit.edu>
Date: Wed, 15 Jan 1997 17:40:53 EST
Reply-To: MIT Management Reporting Authorizations Team
<MRAUTH-L@mitvma.mit.edu>
From: George Petrowsky <GEORGEP@MITVMC.MIT.EDU>
To: Multiple recipients of list MRAUTH-L <MRAUTH-L@mitvma.mit.edu>
----------------------------Original message----------------------------
Thanks for the fax Barry.
Since last week I have:
1. Picked up testing of the MIT transaction/authorization front end
that Steve and I originally did in SF3.
Created ZTSTCT to call ZTST (a copy of ME23). ZTST has the
startup authorization of Z_TCODE = ZTST attached, so a User would
have to have this in their profile to invoke ZTST as a transaction.
However, when called by ZTSTCT via call transaction, the User does
NOT need Z_TCODE = ZTST. This is the same behavior previously noted.
2. Found an SAP note, 35612, which explains that this is the
INTENDED behavior of call transaction, allowing the calling
program to implement any authorization desired prior to
calling the called transaction. This removes Strategy #1,
con #2.
3. Found that the program that is transaction ME23 is also the
program of 20 other transactions, all with different
startup authorizations. I'm not sure what this means to us yet,
but it makes it more complicated.
George
