Call transaction Tcod..... mode 'N'/'P' where option N not terminating

[Former Member]

Hi,

Call transaction Tcode using mode ['A','E','N','P'] ...

If breakpoints are set in a tcod called using the CALL TRANSACTION tcod USING itab variant,

these are not actually reached in 'N' mode. The system tries to insert data in the Debugger screen; the call ends with SY-SUBRC = 1001

and the message "Batch input data is not available for screen SAPMSSY3 0131" (S 00 344).

I tried this in release ECC 6.0 but its not termintaing as soon as it reaches the breakpoint in tcod.

I tried before this in the previous release and it was working fine.

[former_member202957]

hai Gauri,

you are getting the following messege 'Batch input data is not available for screen SAPMSSY3 0131" (S 00 344).' may be check the data in your flat file. Check the file path correctly and the data in flat file . May be there no data exit for that screen.

<b>reward if useful</b>.

Regards,

sunil kairam.

[Former Member]

Hello,

When trying to debug a BDC Session it encounters a new screen(the one which conatins the code) for which there would be no recording and hence could be the reason for the error message . Please also check if the screen for which the error is thrown is a part of the recording of the tcode .

Regards,

Sowmya.

[Former Member]

Hi,

Welcome to SDN..

Well this kind of behavior is defined in help of call transaction also. I am copy pasting it from SAP help for 'Call Transaction'.

mode Effect

"A" Processing with display of screens

"E" Display of screens only if an error occurs

"N" Processing without display of screens. If a breakpoint is reached in one of the called transactions, processing is terminated with sy-subrc same as 1001. The field sy-msgty contains "S", sy-msgid contains "00", sy-msgno contains "344", sy-msgv1 contains "SAPMSSY3", and sy-msgv2 contains "0131".

"P" Processing without display of the screens. If a breakpoint is reached in one of the called transactions, the system branches to the ABAP Debugger.

So if you want to debug your bdc, you should set breakpoint in code for transaction MB1B and than change the mode from 'N' to 'P'.

CALL TRANSACTION 'MB1B' USING bdcdata MODE 'P' UPDATE 'S' MESSAGES bdcmsgcoll

Regards

[Former Member]

Hi,

I really dont think i explained the problem well by looking at the answers i recvd.

My query is that if i place a breakpoint in tcode and when we use in mode N , then as per the sap help it says that once it reaches this breakpoint it should not debug further steps and should terminate with the message mentioned "No batch input....." but when i tried this in release ECC 6.0 it is debuggin further (not getting terminated with the above mentioned message" and its acting like mode P.

Plz guide me about this situation.