Dump CALL_TRANSACTION_NOT_FOUND

[Former Member]

Hi All,

I have a dump while excuting program ZSMMENU.

Dump Analysis -

The current ABAP/4 program uses CALL TRANSACTION to call the Transaction

" ".

Table TSTC (Transactions) contains no entry for the

Transaction " ". This could be due to a program error

(incorrect transaction code specified).

Ensure that upper/lower case is correct.

Can anybody please give mevaluable inputs on this?

Thanks & Regards

Reshma K

[Former Member]

hi..

Is this the program created by you? If yes,

Did you assign a transaction code to this pgm?

If you have not assigned a tcode, then assign it first and

run that tcode.

thanks,

Padma

[Former Member]

Hi,

It's not a program developed by me. However while executing, it is giving a dump.

DATA: OK_CODE LIKE SY-UCOMM,

SAVE_OK LIKE SY-UCOMM.

SAVE_OK = OK_CODE.

CASE SAVE_OK.

CALL TRANSACTION save_ok.

Is it the thing that blank space is causing a dump?

Please see the below code -

CASE SAVE_OK.

WHEN 'BACK'.

SET SCREEN 0. LEAVE SCREEN.

WHEN 'END '.

SET SCREEN 0. LEAVE SCREEN.

WHEN 'BREA'.

SET SCREEN 0. LEAVE SCREEN.

WHEN 'IW58'.

CONCATENATE 'U_' SY-UNAME INTO VAR.

CALL FUNCTION 'RS_VARIANT_EXISTS'

EXPORTING

REPORT = 'ZIQMEL20_2'

VARIANT = VAR

IMPORTING

R_C = SUBRC

EXCEPTIONS

OTHERS = 99.

IF SUBRC <> 0.

CASE SY-TCODE.

WHEN 'ZZBSC'.

CNT_QMART = 'ZB'.

WHEN 'ZZCSC'.

CNT_QMART = 'ZC'.

WHEN 'ZZPSC'.

CNT_QMART = 'ZP'.

WHEN 'ZZHSC'.

CNT_QMART = 'Z4'.

WHEN 'ZZRSC'.

CNT_QMART = 'Z7'.

WHEN 'ZZSSC'.

CNT_QMART = 'ZS'.

WHEN OTHERS.

CNT_QMART = ' '.

ENDCASE.

SUBMIT ZIQMEL20_2

VIA SELECTION-SCREEN

WITH QMART EQ CNT_QMART

AND RETURN.

ELSE.

SUBMIT ZIQMEL20_2

VIA SELECTION-SCREEN

USING SELECTION-SET VAR

AND RETURN.

ENDIF.

WHEN OTHERS.

*{ INSERT DEVK908920 1

IF sy-tcode = 'ZZRSC'.

gw_tcode = 'ZZRSC'.

w_memkey = 'ZZRSC'.

export gw_tcode from gw_tcode to MEMORY ID w_memkey.

clear : gw_tcode, w_memkey.

ENDIF.

*} INSERT

CALL TRANSACTION save_ok.

• save_tran = sy-tcode.

• leave to transaction save_ok.

ENDCASE.

Please give me your suggession....

Thanks

Reshma K

[Former Member]

erm call transaction works with transaction codes and not with user_command_codes ...

[SimoneMilesi]

Hi!

First of all before

CHECK save_ok IS NOT INITIAL. "<-avoid to call a blank transaction.
IF sy-tcode = 'ZZRSC'.

then

TRANSLATE save_ok TO UPPER CASE. "<-avoid to call something that doesn't exist.
CALL TRANSACTION save_ok.

[SimoneMilesi]

Florian, if it's a custom report, he can assign at user command the value of some transaction to call.

In some cases i do this myself, to avoid if..else... or case...

[Former Member]

oh ok, from that logical side, that is wicked, from the docuemnting side, it is ... misleading but well thanks for clarifying this to me.

[Former Member]

Hi,

Instead of "others" you could specify the code which is a transaction. I guess "others" may be really others.

Sujay

[nirajgadre]

Hi,

Check the statement CALL Transaction in your code . it seems that you are calling the transaction witch is does not exist in system itself or you are not passing any transaction to CALL transaction statement.