‎2008 Feb 06 11:58 AM
Hi ,
I do not have authorization for a particular tcode 'FB09'. When I create a 'Z' tcode though SE93 and assign 'FB09' to it , I can make a workaround and access the transaction .
This works in Development Server .
But the same thing does not work in the Production Server .
What is the reason behind this ?
Thanks and regards ,
‎2008 Feb 06 12:33 PM
hi Prabhu,
I sometimes have the same problem and use the following small program:
REPORT z_test.
PARAMETERS : p_tcode TYPE tcode.
AT SELECTION-SCREEN.
SELECT COUNT( * ) FROM tstc
WHERE tcode EQ p_tcode.
IF sy-subrc NE 0.
MESSAGE e398(00) WITH 'Transaction does not exist!'.
ENDIF.
START-OF-SELECTION.
CALL TRANSACTION p_tcode.
what you have to know is that CALL TRANSACTION does not check the authority to the transaction code (while LEAVE TO TRANSACTION does). If it still fails (because of authority), it means that there are more authority checks (in the program, which you call through CALL TRANSACTION).
hope this helps
ec
‎2008 Feb 06 12:06 PM
The roles what U have in development and Production will be
certainly different ..
‎2008 Feb 06 12:11 PM
‎2008 Feb 06 12:35 PM
Check for User Roles , Profiles and missing authorizations
for the user in both the servers ...
‎2008 Feb 06 12:22 PM
First goto the SE93 and enster FB09 press dispaly to see the how they are defined.same way u have to create Z tcode with entries similar to the FB09. if authorization specified for only transaction code(FB09) then it will work.
some case they restrict at program levet in that case it is not possible to access.
‎2008 Feb 06 12:33 PM
hi Prabhu,
I sometimes have the same problem and use the following small program:
REPORT z_test.
PARAMETERS : p_tcode TYPE tcode.
AT SELECTION-SCREEN.
SELECT COUNT( * ) FROM tstc
WHERE tcode EQ p_tcode.
IF sy-subrc NE 0.
MESSAGE e398(00) WITH 'Transaction does not exist!'.
ENDIF.
START-OF-SELECTION.
CALL TRANSACTION p_tcode.
what you have to know is that CALL TRANSACTION does not check the authority to the transaction code (while LEAVE TO TRANSACTION does). If it still fails (because of authority), it means that there are more authority checks (in the program, which you call through CALL TRANSACTION).
hope this helps
ec
‎2008 Feb 22 11:26 AM