how can i debug a rfc being called from .net connector (NCO) v2.0?

[Former Member]

we are having an issue with this process in ecc 6.0. we are not receiving data correclty. is there a way i can view the process / data in sap as it is being called? i want to be able to see the data that is being sent from the c# program thru NCO, sap .net connector.

thanks for any help.

[Former Member · Accepted solution]

you have to be on SAPGUI for debug,put external debug point,and trigger it from external app...

[Former Member · Accepted solution]

thanks,

i am on the sap side, and in the past, i have changed the code in development to have an infinite loop, so that i can step thru the debug screens. here is an example of the code i use;

• for debugging this rfc call. goto sm51 and you will see this * *

*programming looping.

DATA: l_flag TYPE c.

DO.

IF l_flag = 'X'.

EXIT.

ENDIF.

ENDDO.

in sm51, you can see the program spinning, then choose the debug option and change the l_flag to X and proceed.

but, what i am looking for in sap, is a trace or soemthing to show me at the machine code level, what the c# program is sending to the rfc. because, when i debug the program like above, the data is missing in ecc 6.0, using .net sap connector. the internal tables are missing all data. on the c# side, our programmers are telling me that the data was successfully sent.

thanks.

[Former Member · Accepted solution]

well in that case, there must be some mismatch in input and output parameter or table parameter of RFC,

please check it carefully,also check by executing RFC in sapgui by giving same input data.

[Former Member · Accepted solution]

thanks for the response.

i have manually tried the rfc from the sap side with data and it is working correctly, i have had the c# programmers write a new program to send the data to sap thru the .net connector and hard coding the entries on the c# side. this is still not working.

we then tried to use the webservices to connect with the same test c# program, with the hard coding, and it worked successfully.

i would think that after these tests, there is an issue with sap connector for .net NCO v2.0 to ecc 6.0 with unicode. we do not have a system without unicode to test with, so it might be the unicode or it might be ecc 6.0 be itself.

since we are going live with ecc 6.0 at the end of may, we need this to work asap so that the testing can begin. i hope there is a sap person reading this someday and can respond to this issue.

i have check oss and there is nothing on this issue.

thanks.

[Former Member]

thanks all.