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

RFC exporting parameter becoming blank in dot net interface

Former Member
0 Likes
930

Hello experts,

We have a SAP 4.7 system. We are facing an issue while exporting parameters to an RFC. As can be seen in below (highlighted in blue) function call we are passing a structure in exporting parameter 'IV_EQUO_HEADER'. But when this structure goes in .NET interface the values of recently added 6 fields in this structure are becoming 'BLANK'. Surprisingly when we debug the process we see values in this structure but when this structure is received in .NET interface few fields are losing their values/or they are facing some conversion problem that's why becoming blank. The main point which has to be analyzed is - why the values which are there in SAP system(char - 3) are not getting recognized at .Net's system whereas other values in the same structure are? I have also heard that RFC should be re-generated in the .NET system since there are recent additions in the receiving structure. Not sure about the root cause.

Please give your expert suggestions on this issue. Thanks!

* == Call RFC FM at the web application == *

  CALL FUNCTION 'Z_SD_EQUO_SEND_PROC'

    DESTINATION 'ZSD_EQUOTATION'

    EXPORTING

      iv_equo_header        = wa_equo_send_hd

      iv_so_doc_flag        = wf_rfc_so_flag

    IMPORTING

      ev_result             = ev_result

      ev_message            = ev_message

    TABLES

      it_equo_item          = tb_equo_send_it

      it_equo_item_price    = tb_equo_send_it_price

      it_equo_item_stdtxt   = tb_equo_send_stdtxt

      it_equo_cust_addr     = tb_equo_send_custadr

    EXCEPTIONS

      communication_failure = 1  " MESSAGE wa_equo_send_hd_new-err_message

      system_failure        = 2. " MESSAGE wa_equo_send_hd_new-err_message.

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
563

Hello all..I have got the solution..Actually the structure that we were passing from sap was having 100 fields whereas the receiving structure at .Net's end was having 90 fields...so they have not used all the fields of SAP..but in SAP we added our new z-fields at end of the structure that's why they were not getting identified at .Net's end. Once we displaced our new fields to few up positions in Sap structure. The problem was resolved.

Thanks,

V

1 REPLY 1
Read only

Former Member
0 Likes
564

Hello all..I have got the solution..Actually the structure that we were passing from sap was having 100 fields whereas the receiving structure at .Net's end was having 90 fields...so they have not used all the fields of SAP..but in SAP we added our new z-fields at end of the structure that's why they were not getting identified at .Net's end. Once we displaced our new fields to few up positions in Sap structure. The problem was resolved.

Thanks,

V