No 'call transaction' security from inbox?

[Dart, Jocelyn]

Hmmm - Are you just using CALL TRANSACTION or are you using CALL TRANSACTION USING ???
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
-----Original Message-----
From: Michael Pokraka [mailto:workflow at quirky.me.uk]
Sent: Friday,27 June 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