Application Development and Automation 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: 
Read only

Error handling in BDC

Former Member
0 Likes
1,415

Hi all,

when i use call transaction sy-subrc = 1,001 when i use mode 'N' otherwise sy-subrc = 0.

call transaction 'PA30' USING ITAB MODE 'N'

UPDATE 'S'

MESSAGES INTO MESSTAB.

Error message is

' No batch input data for screen SAPMSSY3 0131'

the data is not updated.can any one say how to overcome this prb.

Please let me know which is the best way to handle Error in BDC.

Thanks

Senthil Bala

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,335

Hi all,

Thanks to all for their answers. I found the answer. When keep break point in call transaction statement sy-subrc = 1,001. but if u run through completely its working fine and sy-subrc = 0 ,

Thanks

Senthil Bala

Hi all,

when i use call transaction sy-subrc = 1,001 when i use mode 'N' otherwise sy-subrc = 0.

call transaction 'PA30' USING ITAB MODE 'N'

UPDATE 'S'

MESSAGES INTO MESSTAB.

Error message is

' No batch input data for screen SAPMSSY3 0131'

the data is not updated.can any one say how to overcome this prb.

Please let me know which is the best way to handle Error in BDC.

Thanks

Senthil Bala

11 REPLIES 11
Read only

Former Member
0 Likes
1,335

check the screen <b>0131</b>, any data passed to that or not.

use all screen mode and try ...

vijay

Read only

RichHeilman
Developer Advocate
Developer Advocate
0 Likes
1,335

A screen is getting thrown(or not thrown) which has not been handled by your recording. Change to MODE E and see if you can tell what is disrupting your transaction.

Regards,

Rich Heilman

Read only

Former Member
0 Likes
1,335

This problem means that transaction is throwing a screen which you BDC is <b>NOT</b> expecting. Follow your steps carefully to find out which part of the transaction is not being handled by BDC.

In debugging you can also assign sy-batch = 'X' and sy-binpt = 'X' to mimic what goes on with MODE 'N'.

Read only

Former Member
0 Likes
1,335

Data will not be updated(I mean not populated) in PA30 transactions you got a error. The error is coming because you are not populating the screen 0131 in program SAPMSSY3.

Do the recording again for the transaction and write the missing part of the BDC population.

Read only

Former Member
0 Likes
1,335

Generally in debugging mode we get the sy-subrc as 1001. Please check whether any fields in the screen are not given value which may be mandatory

Read only

Former Member
0 Likes
1,335

i think there is no data passed to the screen .

try to use all screen mode or error screen mode

and check it

vijay

Read only

Former Member
0 Likes
1,335

Hi Senthil,

Your screen flow does not contain the screen SAPMSSY3 0131.

Run the call transaction in A or E mode to see the flow.

Read only

Former Member
0 Likes
1,335

Its working whrn i provide mode 'E' or 'A'. and not workin for 'E'.

Read only

Former Member
0 Likes
1,336

Hi all,

Thanks to all for their answers. I found the answer. When keep break point in call transaction statement sy-subrc = 1,001. but if u run through completely its working fine and sy-subrc = 0 ,

Thanks

Senthil Bala

Read only

0 Likes
1,335

Cool. Please close the post. Thanks.

Regards,

Rich Heilman

Read only

0 Likes
1,335

Hi Snethil,

Actually Srinivasa Bhagavatam did mention about the 1001 return code in debug mode.. Doesn't he deserve points for that?

Regards,

Suresh Datti