No 'call transaction' security from inbox?

[Soady, Phil]

Hi Mike,
If you need this feature from a method.... (why are they a valid agent ?)
then
either
 
CALL FUNCTION 'AUTHORITY_CHECK_TCODE'     to your method,
 
or
 
Place explicit rules in Se97.
 
hth
 
Phil.
 
 
Phil Soady
Senior Consultant
Business Technologies
SAP Australia
* : 0412 213 079
* : phil.soady at sap.com
 
 
 
 
 
-----Original Message-----
From: Michael Pokraka [mailto:workflow at quirky.me.uk]
Sent: Friday, June 27, 2003 1:31 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: No 'call transaction' security from inbox?
 
 
Hi all,
Scenario: transaction security based on S_TCODE, 4.6c system. This works well, except when a task does a CALL TRANSACTION as part of a dialog item. If an item is executed from the inbox for a transaction which is NOT authorized, it happily ignores the auth check. I've put in a BREAK-POINT just to make sure: it stays in the same user context, the break point is reached, SY-UNAME is whgat is expected, and debugging reveals exactly nothing. (get to CALL TRANSACTION, hit F5, and it immediately jumps to the transaction's ABAP). The same thing executed via SE38 does fail an authorization check.
 
Any thoughts?
Cheers
Mike