[RFC][Authorization] Prevent Dump on RFC Call

Hi,
I would like to have a tool to check consistencies throughout different SAP systems for a given user.
For this, I call the Bapi called 'BAPI_USER_GET_DETAIL'. The problem is that, depending RFC user defined in SM59, it may end by a DUMP.
Thus, is there a way to test the RFC user rights in order to prevent the Dump ?
The problem is that calling another RFC function module may also result in a Dump, isn't it...
Thanks for your replies!

You may have to try for authorization before hand. You have tried doing authority checks on one of the following authorization objects?
S_RFC        Authorization check for RFC access
S_RFCACL     Authorization Check for RFC User (e.g. Trusted System)
authority-check object 'S_RFC'
         id 'RFC_TYPE' field '__________'
         id 'RFC_NAME' field '__________'
         id 'ACTVT' field '__________'.
if sy-subrc = 0.
* Then do the BAPI
Endif.
authority-check object 'S_RFCACL'
         id 'RFC_SYSID' field '__________'
         id 'RFC_CLIENT' field '__________'
         id 'RFC_USER' field '__________'
         id 'RFC_EQUSER' field '__________'
         id 'RFC_TCODE' field '__________'
         id 'RFC_INFO' field '__________'
         id 'ACTVT' field '__________'.
if sy-subrc = 0.
* Then do the BAPI
Endif.
Regards,
Rich Heilman

Similar Messages

Short Dump in rfc call in background

Hi All,
I am getting an RFC error short dump in a background program the short dump message says "RFC_ERROR_SYSTEM_FAILURE: no system found in another group for import queue", the same RFC works fine in foreground and in another background program. I looked into the target system, there is no dump generated.
I tested it in one system it works fine but in another it generates a short dump. I am trying to understand why this is happening any inputs are welcome.
Thanks in advance,
Barjinder

It has been resolved the called FM was raising an exception and it was not captured in the calling FM.
Thanks to all.

XI to RFC Scenario: Runtime error during RFC Call

Hi,
I am testing a XI-to-RFC scenario involving BPM. The RFC works perfectly from SE37; but I get 'ICM_HTTP_TIMEOUT, Error code 402' when I invoke it from XI. On digging through the problem, it appeared that the calling program produced a short dump at the ABAP end. The code is as follows:
module %_rfcdia_start output.
 "Do not display screen !
 call 'DY_INVISIBLE_SCREEN'.
 perform remote_function_diastart.
endmodule.
module %_rfcdia_call output.
 "Do not display screen !
 call 'DY_INVISIBLE_SCREEN'.
 perform remote_function_diacall.
endmodule.
module %_cpic_start.
if sy-xprog(4) = '%RFC'.
 perform remote_function_call using rfctype_external_cpic.
else.
 call 'APPC_HD' id 'HEADER' field header id 'CONVID' field convid.
 perform cpic_call using convid.
endif.
endmodule.
form cpic_call using convid type c.
communication send id convid buffer header.
if sy-subrc eq 0.
 perform (sy-xform) in program (sy-xprog).
else.
 message a800.
endif.
endform.
form remote_function_call using value(type).
data rc type i value 0.
do.
********This is the line where error occurs************
 call 'RfcImport' id 'Type' field type.
 if sy-xprog = 'JAVA'.
 system-call plugin
 id 'JAVA' value 'FORW_JAVA'
 id 'RC' value rc.
if there is no rollout on the JAVA side which
rolls both, JAVA and ABAP, we return to the
C-Stack and reach this point
in case there was an rollout, the ABAP-C stack is lost
and we jump direkt to this point
here we trigger the rollout on this Abap side with
the following statement
 system-call plugin
 id 'JAVA' value 'ROLL_OUT'
 id 'RC' value rc.
 else.
 perform (sy-xform) in program (sy-xprog).
 rsyn >scont sysc 00011111 0.
 endif.
Anybody has any idea why it is happening? Is it a network issue? The dump in ST22 says that 'The program "SAPMSYS1" was terminated manually'. How it is possible to manually abort an automatic call?
Awaiting reply.
Regards.

Hi,
Probably because of timeout, it is unable to execute the request ..so it is aborted.
btw, is it a synchronous call ? what is the message size ? the given data to RFC is correct and valid structure ? check the mapping .for this use the data from SXMB_MONI and test it
Check this blog for timeout errors-
/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
Regards,
moorthy

CALL_FUNCTION_NOT_FOUND dump on RFC eventhough it exists and is active.

Hi,
From SRM system in a BAdi, I am calling a custom function module (RFC) which exists in remote ECC system to make certain checks.
The problem is that when the system calls the customer function module, it gives dump in ST22 as :
Runtime Errors : CALL_FUNCTION_NOT_FOUND
details as below :
What happened?
    The function module "YLN_TAXCODE_SELECTION_IN" is called,
    but cannot be found in the library.
    Error in the ABAP Application Program
    The current ABAP program "YCL_IM_LEN_TAXCODEDET_IN======CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
I have checked that the above Custom Function module exists and is active in ECC system.
Please give inputs and suggest.
Thanks.

I tried around a little bit:
1) valid function name and valid destination: works fine
2) valid function name and destination 'NONE':
- dumps CALL_FUNCTION_REMOTE_ERROR and CALL_FUNCTION_NOT_FOUND in calling system
3) valid function name and invalid destination:
- dump CALL_FUNCTION_NO_DEST in calling system
4) invalid function name and valid destination:
- dumps CALL_FUNCTION_REMOTE_ERROR in calling system and CALL_FUNCTION_NOT_FOUND in remote system
5) valid function name and empty destination:
- dump CALL_FUNCTION_NOT_FOUND in calling system
Are you sure you don't have a typo in your function name, as in 4), and that you are calling the correct destination (not sure how many you have in your landscape)?
Thomas

RFC Authorization

All,
we are trying to do a HTTP to RFC sccenario and we get the following error while sending the message to the remote R3 system - "User xxx has no RFC authorization for function group nnnn".
First we tried giving access to that function group later it complained about another function group and another. Im able to log into the R3 system and execute the BAPI directly without issues.
What RFC related permission should my user have to make the call work from HTTP to RFC?
Thanks.

Hi,
please see the below threads
RFC: Non-unicode to Unicode - Authorization error
I E ping error: User XIRWBUSER has no RFC authorization for ...
com.sap.mw.jco.JCO$Exception (104) RFC_ERROR_SYSTEM_FAILURE
no RFC authorization for function group RFC2
Regards..
Chilla..

I E ping error: User XIRWBUSER has no RFC authorization for ...

Hi all,
In the RWB->Component Monitoring when I select the
"Integration Engine" it is giving ping error and Self-Test Status errors.
Ping error: User XIRWBUSER has no RFC authorization for function group CHECKRFCS.
Self-Test status: JCo request failed.
Please help me, it is very urgent.
Thanks in advance,
Nagarjuna.

Hi Nagarjuna,
Please look at these..
User abcd has no RFC authorization for function group SYST
Delta Pull Fails with Short dump in R/3 - RFC_NO_AUTHORITY
http://help.sap.com/saphelp_nw04/helpdata/en/4f/b541d812aea34695d54758cec0796f/frameset.htm
cheers,
Prashanth

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

Has no RFC authorization for function group ZRFC_XI

Hi All,
I have a scenario where I am calling RFC inside the BPM. When I execute I got the errror as
User SKXXXXX has no RFC authorization for function group ZRFC_XI
I have gone though the form
no RFC authorization for function group RFC2
User abcd has no RFC authorization for function group SYST
and I understood that we need to set authroization object S_RFC with RFC_TYPE = FUGR, RFC_NAME = SYST and ACTVT = 16. I think we need to set this to XIISUSER and the password and for PI7.0 user PIISUSER and its password
But not able to understand where we need to do this activity. I request you to kindly let me know how to assign this object... do we need to assign in SAP system or in XI system. please help me out on this problem.
Regards,
Dhill

Dhil,
I never worked on these stuffs. But I found some useful stuff ,I think surely it will help u.
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/please-how-to-create-an-authorization-object-386391
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a92195a9-0b01-0010-909c-f330ea4a585c
Best regards,
raj.

User |TMSADM has no RFC authorization for function group SYST

Hi All,
When we release any transports we are getting the above error, this is basically due to the fact that implificaiton of complex password parameters, to supress this we had followed the note 761637.
I had regenerated RFCs and reset TMS user, but still no use any ideas?
This is definely not the issue with Authorization as user TMSADM has right profiles.
Reg,
VV

Patch Downloader wrote:Patch Downloader wrote:>
> ... when I reset my TMSADM user though it says it was reset, but SU01 for TMSAMD user is intact , it did not change the user type to SYSTEM, it kept as it was before Communication data.
Then the reset is not working (which would be consistent with the note). You can administrate the connections (SM59) and user (SU01) manually now. Try to change the user type in SU01.
>
> I did not get the user to test the release , but I am checking in the RFC connection for this RFS desitnatation and it failes with same error.
You stated before that releasing the transport was failing, not the authorization test in SM59.
Note that default system settings for the "Connection Test" only verifies that there are no network gremlins between the servers and the RFC settings, it does not verify that the logon was successfull. The "Authorization Test" on the other hand verifies the authentication was successfull and the authorization to perform the RFC call was checked and successfull.
Most likely, the problem is caused either by the user type AND / OR the password is in fact not correct (or is arriving incorrectly - See SAP Note 1023437).
Some other suggestions:
- Check ST22 to see whether more details are available on the error (check source and target destination).
- Check whether the user doing the release is missing an authorization to use the TMS.
- Check the value of your system profile parameters auth/rfc_authority_check and rfc/reject_expired_password?
Cheers,
Julius

User has no RFC authorization for function group.

Hi expert,
I am calling a new function module from the WebDynpro Java that is causing an issue that User has no RFC authorization for function group. if the user doesnt have proper authorization like SE37 Transactions Code and others.
But there is some more existing function module in the same application that is working fine without having above issues with same access.
I am passing the USERID as input in the function Module and execute simply.
So can you please tell me the Way to handle it?
I will really appreciate your answer.
Thanks
Ali

Hi Rali,
I think,there is problem with ur JCO connection..
Please check the following steps -
1. Go to transaction SM59.
2. Choose Create.
3. Enter the following:
RFC destination: SAPSLDAPI
Connection type: T (Start an external program via TCP/IP).
4. Choose Enter.
5. Choose Technical settings and specify the following data:
a. Select Registered Server Program as the activation type.
b. Enter the program ID of the SAP J2EE Engine that acts as the RFC server. Enter SAPSLD_xyz (xyz is the SID of SAP J2EE Engine Server.)
c. Enter the gateway host and the gateway service of R/3 server
d. If the system is a Unicode system, navigate to Special Options and select the option
Non-Unicode or Unicode in the section Character Width in Target System according to the gateway
server.
6. Save your entries.
Now
1. Go transaction SLDAPICUST.
2. Switch to editing mode and choose Insert Row. Specify the connection parameters of the J2ee server ,
Host name, port Number, user and password - and set this SLD server as Primary.
Only the entry marked as Primary is active.
Please check whether there is entryof r/3 server in the j2ee server /etc/services folder.If no entry is there then add -
R/3server port/TCP
in the service file.
Please check the r/3server service folder and host folder - do they have entry of java server, if no add the entry in the same way as done above for j2ee server.
Also check the Group ,that u have entered for r/3 server in SLD exist in R/3 server or not if not add it....
I hope this will help you ...
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks,
Gunja
Edited by: Armin Reichert on Apr 26, 2008 6:35 PM

RFC Authorization Requirements

Hi,
I hope a simple question here. I am trying to call up an RFC using .Net connector 1.0 (yes I am old school). The server is one where I have limited access. I am trying to just establish an RFC connection at this point but cannot get past it. The message is below. I know I have the correct username and password (have tried 2 different logons. Is it possible that I haven't the proper authorization to establish an RFC connection, and the error thrown is below? I could see if I don't have access, but the error message doesn't seem to fit the bill in that case.
Any input would be appreciated, thanks!
SAP.Connector.RfcLogonException: Name or password is incorrect (repeat logon)
at SAP.Connector.SAPConnection.ThrowRfcException(RFC_ERROR_INFO_EX rfcerrInfo, Encoding encoding, String languangeCode)
at SAP.Connector.SAPConnection.Open()

Hi Jonathan,
Are you getting this error while executing your application or while creating a proxy?
Check other parameters. System number, application server IP number, language. Also I recommend, if you are getting this error while creating proxy, use custom settings not select the SAP server on dropdown.
Best Regards,
Huseyin Akturk
SW Engineer & SAP ABAP Consultant
www.huseyinakturk.net

How to create RFC function module and how to call this function module

Hi,
i want to know step for creating RFC function module and then How to use this function module from some other sap system.
Thnaks,
jigar

Jigar,
To implement a remote function module in ABAP, perform the following steps:
Register the module as remotely callable in the RFC server system.
In the function module Administration screen (transaction code SE37), set the field Can be called via REMOTE CALL. Registering a module as remote causes an RFC stub to be generated for it.
Write the code for the function module.
Create the destinations.....................
Displaying, Maintaining and Testing Destinations
To display, create or modify destinations, choose Tools ® Administration ® Administration ® Network ® RFC destinations or enter transaction code SM59.
Remote Destinations are stored in table RFCDES. The RFCDES table describes logical destinations for remote function calls.
It is not possible to maintain the RFCDES table directly.
You can also access logical destinations via the Implementation Guide (IMG) by choosing Tools ® AcceleratedSAP ® Customizing ® Execute Project ® SAP Reference IMG.
In the Implementation Guide, expand the following hierarchy structure:
Basis
Application Link Enabling (ALE)
Sending and Receiving Systems
Systems in Network
Define Target Systems for RFC Calls
Displaying Destinations
The initial screen for this transaction displays a tree:
Different connection types (i.e. partner systems or programs) are possible. For further information, see Types of Destinations.
To display all information for a given destination, double-click it, or place the cursor on it and press F2 .
To search for a destination, press the Find button and specify your selection. You get a list of all entries matching your selection. Place the cursor on the one you want, and press F2 or simply double-click the destination. All information for the given entry appears.
Creating Destinations
On the destinations overview screen (transaction code SM59), the connection types and all existing destinations are displayed in a tree structure.
All available connection types are explained in Types of Destinations.
To create a new RFC destination, press the Create button. A new screen is displayed with empty fields for you to fill in.
If you want to create a new destination
As you create a remote destination, you can specify a particular application server or a group of servers for a balanced distribution of system load.
For details of the destination parameters, see Entering Destination Parameters.
Changing Existing Destinations
On the destinations overview screen (transaction code SM59), the connection types and all existing destinations are displayed in a tree structure.
You can display all information for a given destination by double-clicking it or pressing F2 on it.
To change an existing destination, double-click it, or place the cursor on it and press the Change button.
For details of the destination parameters, see Entering Destination Parameters.
Testing Destinations
To test a destination, choose the appropriate function from the Test menu.
Connection (also available via the Test connection pushbutton)
Authorization (checks logon data)
Local network (provides a list of application servers)
You can use the CALL FUNCTION statement to call remote functions, just as you would call local function modules. However, you must include an additional DESTINATION clause to define where the function should run:
CALL FUNCTION RemoteFunction
DESTINATION Dest
EXPORTING
f1 =...
f2 =...
IMPORTING
f3 =...
TABLES
t1 =...
EXCEPTIONS......
The field Dest can be either a literal or a variable: its value is a logical destination (for example, "hw1071_53") known to the local SAP System. Logical destinations are defined in the RFCDES table (or the TRFCD table in R/2 Systems) via transaction sm59 or the following menu path: Tools ® Administration, Administration ® Network ® RFC destinations. You can also access logical destinations via the Implementation Guide (IMG) by choosing Tools ® Customizing ® Enterprise IMG. In the Implementation Guide, you can then choose Cross-application components ® ALE ® Communication ® Define RFC destination.
The remote function call concept, for example, allows you to access a function module in an R/2 System from an ABAP program in an R/3 System. If you want to read a customer record from your R/2 Systems database, create a remotely callable function module in the R/2 environment which retrieves customer records. Call this function from your R/3 System using a remote function call and listing the destination for the target R/2 System:
Pls. reward if useful

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

RFC error: timeout during allocate/CPIC-CALL: 'ThSAPCMRCV'#

Hi folks,
We experienced this error while trying to carry out transport into the Production Server- RFC error:timeout during allocate/CPIC-CALL: 'ThSAPCMRCV'#.
I have checked connection tests,RFC, they look fine.
Anyone experienced this before?
Thanks.

hi,
please check :
SM59 > R/3 Connection > TMS Communication Interface generated --> is the connection OK ?
also check in :
STMS --> is the transport configured properly ?
rgds,
alfonsus guritno

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

[RFC][Authorization] Prevent Dump on RFC Call

Similar Messages

Maybe you are looking for