RFC Enabling a Function Module

[Former Member]

Hi Friends

I need to remote enable a Function Module( for RFCs ) which was already developed some years ago.

I need to know what all things I need to take care of when remote enabling such a Function Module.

Thanks

~S

[Rashid_Javed]

Well you can do it through attributes tab. There is a radio button for this but keep in mind a few things about RFC function calls, as you may have to change the function code a little bit

1: Certain abap statements are not allowed in RFC functions such as 'Leave'

2: If the orignal function is throwing Exceptions, it is better to return the exceptions in a 'Return' table for your RFC enabled function.

3: All your import and export parameters must be passed by value.

Cheers.

[Former Member]

Hi Friends

Thanks for your inputs. I was basically concerned about the following.

The current Function module logic includes a "CALL SCREEN" which means screen validations will also be included. Also call to FM "F4IF_FIELD_VALUE_REQUEST" is included.

So, if I enable this Function Module as remote enabled, how will screen validations be handled ? Is this possible in RFCs ?

Is "CALL SCREEN" okay for an RFC call?

What if the Function Module has a "CALL TRANSACTION" statement? Can such a FM also be RFC enabled.

Thanks

Your inputs were defintely useful.

Regards

Prasad

[eddy_declercq]

Hi,

You might to have a look at

/people/gregor.wolf3/blog/2005/02/27/suppressing-unwanted-sap-gui-screens-from-bapirfc-when-calling-them-from-external-system-in-background-150-solution-2

and

/people/ajay.kumar/blog/2005/02/25/suppressing-unwanted-sap-gui-screens-from-bapirfc-when-calling-them-from-external-system-in-background133

Eddy

[Rashid_Javed]

Well it should work. We used to have some RFc functions which were updating some data in other system through call transaction (but those call transactions were in background mode)so this should not be a problem.

Also i would suggest make a copy of that FM, RFC enable it and test it through in your own system. You can use the RFC destination 'NONE' for that.

[Former Member]

this is what u need to do...

1) change attributes of FM to Remote-Enabled

2) create RFC destination in SM59, u can specify the logon information here to access the remote system

3) call the function by specifying the DESTINATION addition in the CALL FUNCTION statement...

that is...

CALL FUNCTION <func_name>

DESTINATION <RFC destination name>

but make sure of the following...

1) if u r going to use asynchronous RFC, there should not be a return parameter in the FM,

2) table header lines cannot be passed in RFC FMs

3) no parameters can be passed by reference

read the documentation on RFC for details...

http://help.sap.com/saphelp_erp2004/helpdata/en/22/042abd488911d189490000e829fbbd/frameset.htm

rgds,

PJ

[Former Member]

NOTHING ONLY THING YOU HAVE TO DO IS IN THE ATTRIBUTES TAB MAKE INSTEAD OF NORMAL FUNCTION MODULE MAKE IT HAS REMOTE ENABLED FUNCTION MODULE

CHERRS

[Former Member]

Hi,

First of all u need to know the data is sharing b/w client to client or system to system. u need to go to sm59 tcode to configure the rfc. after that u need to develop fun. module based on client to client or system to system.