Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Error in some systems when adding a file to favorites


I am trying to open a file that I have added to the Favorites list (Add Other Objects --> Web address or file) in system K5Z. When I double click on the link, though, I get the error message  No authorization to call transaction "SESS_START_OBJECT". I get this error in some systems (B0Y, B5Z, V7T) but in other systems (C2K, HCA, for example) it works fine. I copied the detailed error report below - does anyone know how I can solve this problem? The problem can be reproduced in the systems I listed, also with using the generic user ANZEIGER.

P.S. I am not a developer, so if the answer is obvious from the error message details, please go easy on me :-)

***************************************************************************************************

Category             
ABAP programming error

Runtime Errors       
CALL_TRANSACTION_NO_AUTH


  1. CX_SY_AUTHORIZATION_ERROR

ABAP Program         
SAPLSMTR_NAVIGATION_MODULES

Application Component
BC-DWB-SEM

Date and Time        
15.07.2015 15:49:18

Short Text

     No authorization
to call transaction "SESS_START_OBJECT".

What happened?

     Error in the ABAP
application program.

     The current ABAP
program "SAPLSMTR_NAVIGATION_MODULES" had to be terminated

      because it found
a

     statement that
could not be executed.

     Transaction
"SESS_START_OBJECT" is not listed in the table of transaction

      codes.

Error analysis

     An exception has
occurred which is explained in more detail below. The

     exception, which
is assigned to class 'CX_SY_AUTHORIZATION_ERROR' was not

      caught and

     therefore caused
a runtime error. The reason for the exception is:

     The current ABAP
program uses CALL TRANSACTION to call transaction

   
"SESS_START_OBJECT".

     The current user is not authorized to start transaction "SESS_START_OBJECT".

Missing handling of
system exception

     Program                               
SAPLSMTR_NAVIGATION

Trigger Location of
Exception

     Program                               
SAPLSMTR_NAVIGATION_MODULES

     Include                                 LSMTR_NAVIGATION_MODULESU27

     Row                                     44

     Module Type                             (FUNCTION)

     Module Name                           
MENU_START_OBJECT_VIA_INDX

Source Code Extract

Line
SourceCde

    14 * URLs im Browser, Word Dokumente (über
den Browser gestartet) und

    15 * Reports würden die
Navigationstransaktion in Falle eines Fehlers

    16 * (A-Message oder Dump) mit
herunterreißen, wenn sie unter dem gleichen

    17 * TCODE laufen würden. Daher starte ich
konventionell ( NICHT über

    18 * "CALL Transaktion using ..."
) einen Tcode und übergebe die Anstart-

    19 * Info über die INDX. Die gestartete
Transaktion (sie heißt

    20 * SESS_START_OBJECT ) liest diese
Info.

    21 * Auf diesem Wege weiß dann der Kernel: Hier
wird die Navigations-

    22 * Transaktion verlassen. In Falle eines
Problems (z.B. weil der Pfad

    23 * zu einem Word Dokument nicht gefunden
werden kann oder weil irgend-

    24 * ein Report dumpt) bleibt die
Navigationstransaktion dennoch stabil.

    25 *** Bemerkung:

26 * Reports und
andere Reportingtypen werden nur dann noch in der

27 * Navigationshierarchie als Reports (und
nicht eh über Tcode) gestartet,

28 * wenn sie aus Aktivitätsgruppen stammen,
die vor Release 4.6A erzeugt

29 * wurden. Diese Aktivitätsgruppen enthalten
ja immer noch die alten

30 * Reportingtypen, da erst ab 4.6A für alle
Reports Tcodes verwendet

31 * werden.

32   data: g_data like smen_buffi occurs 0 with
header line.

33   data: id like smen_buffi-url.

34   concatenate 'TCD_START' sy-uname into id.

35   condense id no-gaps.

36   refresh g_data.

37   g_data-url = OBJECT_NAME.   append g_data.

38   g_data-url = REPORTTYPE.    append g_data.

39   g_data-url = SAP_GUID.      append g_data.

40   g_data-url = URL.           append g_data.

41   g_data-url = target_system. append g_data.

42   EXPORT G_DATA TO DATABASE INDX(VM) ID id.

43   commit work.

>>>   call
transaction 'SESS_START_OBJECT' WITH AUTHORITY-CHECK.

45 ENDFUNCTION.

tive Calls/Events

.   Ty.          Program                             Include                             Line

    Name

11 FUNCTION     SAPLSMTR_NAVIGATION_MODULES         LSMTR_NAVIGATION_MODULESU27            44

  
MENU_START_OBJECT_VIA_INDX

10 FUNCTION     SAPLSMTR_NAVIGATION_MODULES         LSMTR_NAVIGATION_MODULESU02            56

  
NAVIGATION_EXECUTE_OBJECT

  9 FORM         SAPLSMTR_NAVIGATION                 LSMTR_NAVIGATIONF0V                    18

  
UCOMM_EXECUTE_OBJECT

  8 FORM         SAPLSMTR_NAVIGATION                 LSMTR_NAVIGATIONF04                    83

  
CONTROL_TREE_NODE_DBL_CLK

  7 METHOD       SAPLSMTR_NAVIGATION                 LSMTR_NAVIGATIONF0I                    86

  
LCL_TREE_EVENT_HANDLER=>ON_DOUBLE_CLICK

  6 METHOD       CL_TREE_CONTROL_BASE==========CP    CL_TREE_CONTROL_BASE==========CM01L    37

  
CL_TREE_CONTROL_BASE=>HANDLE_NODE_KEY_EVENT

  5 METHOD       CL_TREE_CONTROL_BASE==========CP    CL_TREE_CONTROL_BASE==========CM015    61

  
CL_TREE_CONTROL_BASE=>HANDLE_BASE_EVENT

  4 METHOD       CL_TREE_CONTROL_BASE==========CP    CL_TREE_CONTROL_BASE==========CM017    26

  
CL_TREE_CONTROL_BASE=>DISPATCH

  3 METHOD       CL_GUI_CFW====================CP    CL_GUI_CFW====================CM001   138

  
CL_GUI_CFW=>DISPATCH

  2 FORM         SAPLSMTR_NAVIGATION                 LSMTR_NAVIGATIONF10                    14

    UCOMM_USER_COMMAND

  1 MODULE (PAI)
SAPLSMTR_NAVIGATION               
LSMTR_NAVIGATIONI01                   
8

    USER_COMMAND_0100

Tags:
replied

The answer is obvious - you don't have authorization for transaction SESS_START_OBJECT. So what is not clear exactly? Authorization concept is explained in SAP Help (searchable in Google as well).

In all honesty, I have no clue what all those systems are, but judging by the "SAP trapezoid" next to your name I'm guessing it's some kind of SAP internal stuff. So I'm confused why this question needs to be posted on SCN, which is a global community, vs. internal SAP help desk...

Also IMHO authorization check should not cause a dump, but again your colleagues would be in the best position to explain why this happens.

4 View this answer in context
Not what you were looking for? View more on this topic or Ask a question