RFC Lookup error :No RFC authorization for function module

Hi All,
I have created RFC in the PI system and enabled it as remote. I am working on PI7.1
I have imported RFC into Repository.But when i am trying to execute RFC lookup function in the graphical mapping I am getting No RFC authorization for function module error.
Unhandled RFC exception: <rfc:Z_MAIL_LOOKUP.Exception xmlns:rfc="urn:sap-com:document:sap:rfc:functions"><Name>RFC_ERROR_SYSTEM_FAILURE</Name><Text>No RFC authorization for function module Z_MAIL_LOOKUP.</Text><Message><ID>RFC_ERROR_SYSTEM_FAILURE</ID><Number>341</Number></Message><Attributes><V1>RFC_NO_AUTHORITY</V1></Attributes></rfc:Z_MAIL_LOOKUP.Exception> com.sap.aii.mapping.api.StreamTransformationException: Unhandled RFC exception: <rfc:Z_MAIL_LOOKUP.Exception xmlns:rfc="urn:sap-com:document:sap:rfc:functions"><Name>RFC_ERROR_SYSTEM_FAILURE</Name><Text>No RFC authorization for function module Z_MAIL_LOOKUP.</Text><Message><ID>RFC_ERROR_SYSTEM_FAILURE</ID><Number>341</Number></Message><Attributes><V1>RFC_NO_AUTHORITY</V1></Attributes></rfc:Z_MAIL_LOOKUP.Exception> at com.sap.aii.mappingtool.flib7.RfcLookup.cacheMore(RfcLookup.java:95) at com.sap.aii.mappingtool.tf7.rt.AMultiResIterator$MultiOutIterator.gotoNextContext(AMultiResIterator.java:95) at com.sap.aii.mappingtool.tf7.AMappingProgram.processNode(AMappingProgram.java:315) at com.sap.aii.mappingtool.tf7.AMappingProgram.processNode(AMappingProgram.java:406) at com.sap.aii.mappingtool.tf7.AMappingProgram.start(AMappingProgram.java:496) at com.sap.aii.mappingtool.tf7.Transformer.start(Transformer.java:133) at com.sap.aii.mappingtool.tf7.AMappingProgram.transform(AMappingProgram.java:626) at com.sap.aii.ibrep.server.mapping.exec.ExecuteXiMappingCommand.transformInternal(ExecuteXiMappingCommand.java:197) at com.sap.aii.ibrep.server.mapping.exec.ExecuteXiMappingCommand.execute(ExecuteXiMappingCommand.java:94) at com.sap.aii.ib.server.mapping.exec.CommandManager.execute(CommandManager.java:43) at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:40) at com.sap.aii.ibrep.server.mapping.MapServiceBean.execute(MapServiceBean.java:40) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy1005_10002.execute(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) Runtime exception when processing target-field mapping /ns0:MT_FileDummy/File; root message: Unhandled RFC exception: <rfc:Z_MAIL_LOOKUP.Exception xmlns:rfc="urn:sap-com:document:sap:rfc:functions"><Name>RFC_ERROR_SYSTEM_FAILURE</Name><Text>No RFC authorization for function module Z_MAIL_LOOKUP.</Text><Message><ID>RFC_ERROR_SYSTEM_FAILURE</ID><Number>341</Number></Message><Attributes><V1>RFC_NO_AUTHORITY</V1></Attributes></rfc:Z_MAIL_LOOKUP.Exception>
13:42:37 End of test
Edited by: Rams on Apr 17, 2009 1:43 PM

Hi! Rams,
I think the issue is related to Authentification Issue..Even though u did correctly please check once the below
1) Check any Typo Erros are there while configuring or giving names in Lookups.
2) please check Authorizations like ID and PWD and Sufficient Roles
3) Also please check did u given paramters correctly while doing RFC look up I mean paramers , Binding parameters and RFC channel name and adapter type or Simple type it must be an adapter
4) In ID part while configuring Interface determinaition you need to give your RFC look Up name there also..Hence check whether u given or not if yes correctly or not
5) Also remember one thing if your scenario is correct mostly you can know the result in mapping itself it seems while testing Message mapping and Interface mappings give your RFC look up paramters in the parameters tab present in TEST tab and later in Document tab give Input...and execute it works if it doesn;t works and if there is an issue with RFC you can get there only..ok
Also go through the below document::
[https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20befc9a-aa72-2b10-ae9b-b0988791d457]
I hope this will give u brief idea...
Also check with basis while taking SAP_ALL authorization so that first u ill came to know whether issue is related to authentification or RFC module itself remote enabled and also do SXI_CACHE also ocne to refresh ESR and ID objects..
Regards::
Amar Srinivas Eli

Similar Messages

No RFC authorization for function module

Hi Experts,
I am working on PI 7.3, doing a idoc to jdbc scenario by using the AEX(Advance Adapter Engine Extended).
I created Integrated Configuration, in tab "Inbound Processing" pointed IDoc_AAE sender channel etc...
While doing the configuration testing i am getting the below error "No RFC authorization for function module IDOCTYPE_READ_COMPLETE."
Messages fails in tRFC.
What can i do, to solve this problem?
Thanks & Regards
Stanislav

I ordered the right to RFC-connect.
The problem was this: in RFC-connect, in Destination(in NWA), you must specify a username, who have permission to read idoc-metadata (from ERP).
More about settings AAE, you may read here http://scn.sap.com/community/pi-and-soa-middleware/blog/2010/10/21/pixi-pi-73-new-java-based-idoc-adapters-configuration-sender-receiver--teaser
Sorry for my bad English.
Thanks all.

Formal error: Invalid calling sequence for function modules

Hi All,
I have developed a function module for FQEVENT 620 Payment: Transfer Line Items for Clearing.
The clearing works fine.
After clearing the open items i need to post an FI-CA Document(BAPI : BAPI_CTRACDOCUMENT_CREATE) for each open item(cleared item)
I have used the bapi : BAPI_CTRACDOCUMENT_CREATE in the same function module that i have developed for FQEVENT 620 Payment: Transfer Line Items for Clearing.Here i am getting an error "Formal error: Invalid calling sequence for function modules".
So please let me know where i can use this bapi to post fi-ca document.Is there a BAdi or Enhancement Spot where i can use this BAPI or tell me what should i do to overcome this error.
Regards
Venkat

Venkat:
While I am confused about your business process - creating an open item when clearing one seems strange. Look into event 0020 which is called after documents are posted - it may present the opportunity to post process additional documents.
regards,
bill.

Authorization for function module : RV_SALES_DOCUMENT_VIEW_3

hi,
the user does not have the auth for the fm RV_SALES_DOCUMENT_VIEW_3 and so he can not display the list that this fm is used in.
How can i provide this auth for this user?
Thanks.
Moderator message: not directly related to ABAP development, please have a look in Netweaver Security forum, but do not ask basic questions like this one.
Edited by: Thomas Zloch on Nov 8, 2010 12:41 PM

Hi ,
I guess the function module 'RV_SALES_DOCUMENT_VIEW_3' should get called from the transaction to
display the list.
So for providing the access to this function module, you can create the single role (assigning the transaction of function module to this role) and then create the multple role and assign this multiple role to the user.
Please let me know for any issues.
Regards,
Darshana

No RFC authorization for function module RSA1_OLTPSOURCE_GET_ALL.

When I try to replicate datasource on BW I get this error.
I replicate others but suddenly, there was a problem with the RFC user, and tehn I wans't unable to extract data and replicate DS.
The RFC user was blocked because password failed too many times, and was unblocked.
But now I get that error.

Hi,
check following things
1. Source system connection is correct
2. check SM59 for connection and authorisation test
3. Check your own authorisation see trace in RSTT or su53 dump ..get the correct role
4. check authorsation for BWREMOTE and ALEREMOTE user..
Thanks and regards
Kiran

IDOC Scenario - User has no RFC authorization for function group EDIN

Hi all,
I'm trying to configure an IDOC scenario from ECC to XI.
RFC's, ports and destinations already configured. On WE19 I'm creating an IDOC for testing the scenario. The IDOC is sent successfully, and it stops on TRFC Monitor with error "User PIRFCUSER has no RFC authorization for function group EDIN." .
Some of you knows what authorization is needed? Basis team said the roles are the same at DEV environment, and there this scenario works fine.
Thanks for your help.
regards.
Roberti

Hi,
Check with PIRFCUSER user , that is having the right authorization or not ..
And make sure that this user is present in the system & it should not locked.
to check that user is present or not-----goto su01 of the system & check
Regards
Seshagiri

No RFC authorization for function group AGS_TAO_REQUEST_MGMT_FGR

Hi,
I'm trying to build a connection between SAP TAO 2.0 and SolMan. I recevied following error message: for one of my user:
2010-12-21 16:28:24:577 : ERROR : SAPTAO.exe : Thread04 (SelfCheckWorker) : SAP.TAO.Common.Rfc.RequestListener.TaoCommonReqListProxy : SearchSoftwareComponents(): an error occured: SAP.TAO.Common.Rfc.SapAgentAgentException: CallBackend(RfcRequest): a call to the backend system failed: SAPAGENT_RFC_CALL_DETAILS(RFC_SYS_EXCEPTION) ---> SAP.TAO.Common.Rfc.SapAgentAgentException: SAPAGENT_RFC_CALL_DETAILS(RFC_SYS_EXCEPTION) ---> System.Exception: User GCRIBB has no RFC authorization for function group AGS_TAO_REQUEST_MGMT_FGR
Please help. Thanks in advance.
Subodh

Hello ,
You have mentioned you have received one of your user? rest of the users is it working?
Looks like i also received this error message when i did not instlal my ST-400 ..TAO Agent..i saw the same error message in the log.
Did you follow the this note to install SAP TAO - agent properly (OSS note - 1368112) ?
When you did self check are you getting any warning messages?
1440074 - Check this note also for RFC authorizations
Good luck.
Ram

No RFC authorization for function group HRXSS_SER

Hi,
after implementing portal (EP 7.0), when the end user tries to access the ESS functionalities, the following error occurs,
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
in default trace, i found the following error,
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: User AG1780 has no RFC authorization for function group HRXSS_SER
when i give SAP_ALL access to this user, then everything is working fine, but i cant give so.
help me regarding this...

Hi Ajay,
simply do what the exception tells you: provide RFC authorization in the backend for function group HRXSS_SER to user AG1780.
Cheers, Anja

No RFC authorization for function group RFC2

When I am trying to import RFCs/IDOCs from ECC to XI in the integration repository, I am getting this error:
User has no RFC authorization for function group RFC2.
Any input is appreciated.
Thanks,
tnv

Hi tnv,
I guess you have to use an authorization object S_RFC with parameters.. In your case, you would need to set
RFC_TYPE=FUGR
RFC_NAME=RFC2
See this link
http://help.sap.com/saphelp_nw04/helpdata/en/6b/af429b12e9214d9a2d6cba921b162f/frameset.htm
Hope this solves ur problem!
cheers
Prashanth
P.S Please mark helpful answers

SMD_RFC has no RFC authorization for function group SPF.

Hi,
http://pw200-3.fcc.XXXXXXX.com:50000/smd ->Diagnostics Setup ->Setup Wizard - Step 1 receives an error message like . .
The value of profile parameter login/accept_sso2_ticket could not be checked
Attached the below error message
<< >>
Sat Nov 08 12:19:07 2008 SSO The value of profile parameter login/accept_sso2_ticket could not be checked
Step SSO Details
Found SID for SSO ACL entry : PW3
Found login.ticket_client for SSO ACL entry : 000
The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
SSO ticket certificate of PW3 was imported in ABAP PSE of localhost (client 001) : remove_certificate_failed
The ticket certificate is already in ABAP PSE, but could not be updated. You might need to check whether the certificate is up to date in STRUSTSSO2
The value of profile parameter login/accept_sso2_ticket could not be checked
!! Exception : An exception occured during the execution of this function 'PFL_GET_PROFILE_LIST'.(cause=com.sap.mw.jco.JCO$Exception User SMD_RFC has no RFC authorization for function group SPFL.)
Thanks
Thirumal
Edited by: Thiru Thirumal on Nov 8, 2008 4:33 AM
Edited by: Thiru Thirumal on Nov 10, 2008 5:49 AM

Hi All,
Check the authorizations of user SMD_RFC as described in[ this guide|https://websmp106.sap-ag.de/~sapdownload/011000358700000178012009E/RCA_User_Adminguide_SP18.pdf], refer to section 2.3.3 [SOLMAN.ABAP.RFCCOM]: Internal RFC System User.
Also check notes 1170859 and 1371222.
1170859 - SMD_RFC: running RCA without SAP_ALL profile
1371222 - Additonal authorizations for E2E RCA EhP1 SP20
I hope this help.
BR,
Allam

UWL : User J2EE_ADMIN has no RFC authorization for function group SYST

Dear All,
When I am trying to register the system in universal Worklist Administration, It gives the following error,
System <>: Fri Jul 11 18:58:11 IST 2008
(Connector) :com.sap.netweaver.bc.uwl.connect.ConnectorExc eption:Fri Jul 11 18:58:11 IST 2008
(Connector) :com.sap.mw.jco.JCO$Exception:User J2EE_ADMIN has no RFC authorization for function group SYST.
I have tried by giving the role SAP_ALL to J2EE_ADMIN , then also i am getting the same error. Can anybody through some light on this....
Helpful tips will be rewarded...
Sanoj

Sanoj,
check these threads
https://forums.sdn.sap.com/click.jspa?searchID=13972376&messageID=5489621
https://forums.sdn.sap.com/click.jspa?searchID=13972376&messageID=5267551
https://forums.sdn.sap.com/click.jspa?searchID=13972376&messageID=5636365
reward points if helpful

QM-IDI : User QMIDI has no RFC authorization for function group QIRF

Hi,
I am in the process of trying to connect from Labware LIMS to SAP ECC 6, specifically the quality module. The aim is to use Labware to connect to SAP via the QM-IDI interface to
1) Download inspection lots from SAP
2) Upload usage decisions and inspection lot results to SAP.
Initially I specified an account on SAP of the type 'Communications Data', however any time I tried to connect to SAP from LIMS via the interface with this account it gives an <i>'Incorrect Username/Password'</i> error in the trace logs. I then changed the account to a dialog user, which seems to be partially more successful, however the trace logs captures the following error 'User QMIDI has no RFC authorization for function group QIRF' when I try to connect from LIMS to SAP via the QM-IDI interface after changing the user to type dialog.
I would appreciate any guidance on how to resolve this issue.
Regards.

i got stuck on configuring idi. plz guide me. bond_chaitu at yahoo dot com

UWL: User MSSNO1 has No rfc authorization for function group SWK1

Dear all,
We have just recently upgrade our support pack and the UWL in the portal is not working anymore. It throw an error message when we click on the work item.
(connector): com.sap.mw.jco.JCOSE Exception:User MSSNO1 has No rfc authorization for function group SWK1
Anyone know how to fix this?
I am not too sure about the authorization part. Can someone guide me please?
Thanks.
Regards,
Bryan.

Hi Brain,
Pls check this thread for solution
Re: UWL and function group swk1
Regards,
Harini S

User PI_JCO_RFC has no RFC authorization for function group ERFC

I am doing IDOC-File scenario between newly installed PI and ECC 6.0 systems.
I have done all the configurations on XI and R/3 end.
When I TEST to send an IDOC from WE19, I could do it successfully and the status is 03 in we02.
But when I go and check SM58, I get the said error: User PI_JCO_RFC has no RFC authorization for function group ERFC.
From that I understand RFC in R/3 end require some authorizations. Am I right? If so, what objects need to be added my user role?
Please advise.
Thanks
Shiva

Hi,
Try to add the following authorization object to the role(s) of the RFC user:
S_RFC
Set the following authorizations:
RFC_TYPE = FUGR (function group)
RFC_NAME = <name of the function group containing the BAPI>
ACTVT = 16 (execute)
Regards
Seshagiri

User SIMPCDIA has no RFC authorization for function group BBPC

Hello all, I am working with SRM 7.0 and when I try to list all account values in the corresponding matchcode, I have this error message:
User SIMPCDIA has no RFC authorization for function group BBPC
User SIMPCDIA is a dialog user created in backend system with authorization objetc S_RFC. I don´t know what is the problem...
Can you help me please?
Thanks in advance
Rosa Rodríguez

Try testing with a user that has the 'SAP_ALL' profile
OR
see if below link is helpful to you.
[Probable Solution|http://www.sapkb.com/question.php?ID=10]
Edited by: Saurabh Agarwal on Sep 1, 2010 11:59 AM

RFC Lookup error :No RFC authorization for function module

Similar Messages

Maybe you are looking for