Dump while calling RFC with Destination

[#1]

Hi All,

We are getting a short dump while executing an RFC with Destination. Please find the below pic for dump details and if anyone came across the same error, kindly give me some solution to resolve this issue.

below is our RFC code,

CALL FUNCTION 'ZCOXT_BAPI_ORDER_CHANGE' DESTINATION 'XMIIRFC02'
     EXPORTING
       i_order_number           = number
       is_header                = orderdata
       is_headerx               = orderdatax
       i_order_category         = auftragstyp-fert
     IMPORTING
       es_return                = return
       e_order_type             = order_type
       e_order_status           = order_status
       e_new_explosion          = master_data_read
     EXCEPTIONS
       error_message.

CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
  EXPORTING
    WAIT          = 'X'
* IMPORTING
*   RETURN        =
           .

Kindly give me some solution.

Regards,

Aravinth

[RaymondGiuseppi · Accepted solution]

- First read Note 97522 - RFC short dump CALL_FUNCTION_REMOTE_ERROR

- Also in the dump look for "In the target system, a short dump has been written as well", so execute ST22 in target system, the FM has raised an error which was not monitored (wrong parameter, unknown FM, not RFC enabled FM, not RFC authorized FM..., look for the dump, many causes are possible)

Regard,

Raymond

[aravinth_anandhan · Accepted solution]

Hi Raymond,

I have gone through the notes and add exceptions in RFC. Now I didn't get dump, but my BAPI is not updating anything.

If is mention like,

CALL FUNCTION 'ZCOXT_BAPI_ORDER_CHANGE' DESTINATION 'XMIIRFC02'

I am getting a following message

synchronous call ZCOXT_BAPI_ORDER_CHANGE to dest. XMIIRFC02 on system wipro_CE1_02 can't be processed by AsynchronousMessageLis

If I give like,

CALL FUNCTION 'ZCOXT_BAPI_ORDER_CHANGE' IN BACKGROUND TASK DESTINATION 'XMIIRFC02'

I am not getting any output or message.

And my BAPI is working fine without the addition DESTINATION. If I add this addition, my BAPI is not updating anything. Please help to solve this issue.

Regards,

Aravinth

[kesavadas_thekkillath]

Have you checked the rfc destinations, parameter types matching in both source/target,authorizations etc ?

[aravinth_anandhan]

I am new to this RFC destination topic, can u please tell me what are all the things I need to check in RFC destination ? And what is that program ID ? can I give any name in that field?

[sandeep_katoch]

Hi Aravinth,

Go to transaction sm59 and there search for your RFC destination XMIIRFC02.

When you will open that rfc you will get a button of test connection. If it is sucessful then your RFC is working fine.

Else you need to make changes to this RFC in same transaction.

Check for the parameters of this RFC. May be you can ask some basis guy for help

Rgds,

Sandeep Katoch

[aravinth_anandhan]

Hi Sandeep,

Test connection for my RFC destination is successful. In that what I need to give in the program id field? Because program ID and RFC destination name both are same in our case.

can we give any name in program id?

Regards,

Aravinth

[sandeep_katoch]

HI Aravinth,

The program ID is the registered program at OS level which is meant for execution of this RFC.

If I am not wrong you are using a TCP/IP type RFC??

Could you pls tell me whether you have called BAPI in update task??

One more thing quiet basic...

Whether the BAPI you have developed is remote enabled or not?

Rgds,

Sandeep Katoch

[aravinth_anandhan]

Hi Sandeep,

• Yes, I am using TCP/IP connection type only
• I didn't call my bapi in update task
• My RFC is remote enabled only

Regards,

Aravinth

[sandeep_katoch]

Hi Aravinth,

Then probably you need to check in destination system for the dump.

One more thing is you can share the complete dump information here so that we get a clear picture.

Till now it seems that the problem with FM remote call only.

Check this for more details

http://help.sap.com/saphelp_45b/helpdata/en/34/8e73b36df74873e10000009b38f9b8/content.htm

Also check in target system for the remote enabling of BAPI you are calling.

Rgds,

Sandeep Katoch

[Former Member]

Hi Aravinth,

Check your RFC Connection in t. code SM59 and check the user id of destination system is maintained in RFC having propper authorization and user id not locked .

If is it possible attach complete dump detail in txt format

regards

Ganesh Datt Tiwari

[aravinth_anandhan]

Hi,

We are not mentioning user name any where in RFC. Is it necessary?

Now Dump is cleared, but my BAPI is not updating anything. Give me some inputs to resolve this issue.

Regards,

Aravinth

[Former Member]

Hi Aravinth,

Great to see that dump issue has been resolved.

RFC is ok means both system can connect but if you want to update the data from this system then an user needs to login in that system to update the same.

You mentain an COMMUNICATION Type user in RFC

This may help you.

Regards

Ganesh Datt Tiwari