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: 

issue with the BDC call transaction sy-subrc returning 1001

Former Member
0 Kudos

Hi,

I have a strange issue with BDC for me32k when I run the BDC with mode 'A' its working perfectly and when I ran the same BDC with mode N its catching SY-SUBRC as 1001. i had searched in the forum for the same and its becoz of some pop up like that they are saying . but when I do the same manually from ME32K there is no pop up. how to over come this scenario . please suggest.

thanks,

rg

5 REPLIES 5

raymond_giuseppi
Active Contributor
0 Kudos

First, in recent versions only, remove any break-point in called transaction (or use mode 'P')

Then when you recorded the transaction (SHDB) did you check/uncheck some options like 'Not a Batch Input Session' or 'Simulate Background Mode' as this will change expected values for fields like sy-binpt and many programs will adapt their behavior) So you must use a CALL TRANSACTION mode consistent with SHDB recording mode (Perform some tests).

You should also search and read the many OSS notes available for BDC in MM and consider usage of a BAPI like BAPI_CONTRACT_CHANGE.

0 Kudos

Hi Raymond,

there are no break points in call transaction and I tried with nobipt = X and NOBINPT not equal to X and nothing is working.

former_member282823
Active Participant

Hi Ramya,

What is the error message that is getting captured from BDCMSGCOLL. Recently I had done the BDC for the same transaction and it is working fine for me.

Regards,

Ramesh.

0 Kudos

Correct. SY-SUBRC = 1001 is simply an error in the BDC, and there's more information in the internal table "messages" (lines of type BDCMSGCOLL) CALL TRANSACTION ... MESSAGES INTO messages. Those messages are of type 'S' and message class '00', but one should consider them as true errors. In "A" mode (display all screens), those 'S' messages appear as 'S' messages at the bottom.

Former Member
0 Kudos

Hi,

I solved it my self the issue is we are trying to pass value to a field in display mode hence its catching an error where as in A ( all screen display mode) its showing an simple warning at the bottom.

correcting this would solve my issue.

thanks,

rg