RFC adapter : Function template from rtepository was null

[Former Member]

Hello all

I get an error which says RfcClientException: functiontemplate from repository was <null> . This error occurs with Receiver RFC communication channel for only certain BAPIS. I tried to find the solution for it with out much luck. There is an SAP notes 730870 which talks about this problem , But i didn't a solution for this even on the notes. It says that the metadata for that particular RFC hasn't been loaded or updated. How can I get rid of this problem , Please advice

Thank you

Sudheer

[prateek]

Perform the following:

1. Try to reimport the RFC into IR.

2. Check for the RFC destination user authorization which is used to connect to the SAP system.

3. Check ID config whether u have used the business system correctly.

Regards,

Prateek

Regards,

Prateek

[Former Member]

Hi Prateek

I have done all of that , But I still have the error, The interesting bit is that this happens only for a particular BAPI call , all the rest of the scenarios and BAPI calls work fine.

[prateek]

Is it a Z* BAPI? Is this the first time u r using this BAPI? If yes, check in R3 whether the BAPI status is activated and released. Then reimport.

Ur WebAS abap business system must also be configured properly.

Regards,

Prateek

[Former Member]

Hi Prateek ,

this is not a ZBAPI , Its BAPI_MATERIAL_SAVEDATA. Hoe can i check if this BAPI has been activated ? I tested this BAPI in the r/3 system and it workd fine, so i guess it is activated. Reagrding the business system , it is configured and working properly with other scenarios and BAPIS.

Cheers

[kkram]

Hello

With the information provided so far, looks like this is an authorization issue on the RFC user that is being used to fetch the metadata of the function module. Authorizations can be controlled on function groups using object S_RFC. Please check this link regarding the authorization group.

http://help.sap.com/saphelp_nw70/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm

Fact that you are able to load other BAPIs but not just the one stated, leads us to believe that its a metadata issue but since you say all the other touch points have been checked, it is worth a shot to look at the authorizations.

Thanks

KK