Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

BDC - No batch input data for screen SAPMSSY3 121????

Former Member
0 Kudos

Hi Experts,

I am enhancing the Goods Movement BDC program of MB1B.

When I am executing this BDC prog. directly by inputting the required data, its working well.

But, When I am running it in the <u><b>Debug mode</b></u> (to know the control flow), at the

<i><b>CALL TRANSACTION 'MB1B' USING bdcdata MODE 'N' UPDATE 'S' MESSAGES bdcmsgcoll</b></i>

statemrnt I am getting the SY-SUBRC 1,001 and the error message(in bdcmsgcoll) is,

<i><b>No batch input data for screen SAPMSSY3 121</b></i>

(When I hv checked this - SAPMSSY3 121 screen in SE80, Its a Debug screen!)

and the document is not creating and the stock is not updating!

So,

1 - Why this is happening like this (coz of Synchronous mode?, actually, earlier with other prog. also happened like the same, but that time its test prog. I mean to say that, i guess this is a commmon problem with BDC! I am sorry if am wrong! )?

2- How to fix it?

ThaNQ.

Message was edited by:

Sridhar

1 ACCEPTED SOLUTION

Rashid_Javed
Contributor
0 Kudos

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

Hopefully it will solve your problem.

RJv
2 REPLIES 2

Rashid_Javed
Contributor
0 Kudos

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

Hopefully it will solve your problem.

RJv

0 Kudos

ThaNQ Rashid.