RFC SAPOSS for EWA Error

Dear Gurus,
I'll tested the connection using SM59 and this below error occured.
I think,the connection is Ok before ,but don't know what happen.Where i need to check and fix it.
For OSS connection to SAP or PUBLIC its OK.No errors.Only for EWA group.
Enclosed are the details:-
Logon     Connection Error
Error Details     Error when opening an RFC connection
Error Details     ERROR: Group EWA not found
Error Details     LOCATION: SAP-Server akne-sapdev_ECD_00 on host akne-sapdev (wp 1)
Error Details     DETAIL: LgIGroupX
Error Details     COMPONENT: LG
Error Details     COUNTER: 29
Error Details     MODULE: lgxx.c
Error Details     LINE: 4299
Error Details     RETURN CODE: -6
Error Details     SUBRC: 0
Error Details     RELEASE: 700
Error Details     TIME: Tue Sep 01 10:34:42 2009
Error Details     VERSION: 5
Please lemme know the solution.
Thanks & Regards
Shah

Hi,
Can you elaborate the problem/
Are you facing the error while connecting to the RFC for SAP OSS in SM59?
Are you facing the issue while generating the EWA report?
Pls clarify.
Regards,
Raja. G

Similar Messages

Production Environment RFC's for EWA.... Please help!!

We have some of the production environment setup EWA. I will need to add else which are left. I have setup EWA in sandbox for testing. worked fine. but i have question about RFC's.
My all DEV systems has the following RFC's in solman;
SM_XXXCLNT100_LOGIN
SM_XXXCLNT100_READ
SM_XXXCLNT100_TMW
SM_XXXCLNT100_TRUSTED
But my all QAS and PRODUCTION system has the following RFC'c in solman.
SM_XXXCLNT100_LOGIN
SM_XXXCLNT100_READ
SM_XXXCLNT100_TMW
I thought when I generate auto RFC's from SMSY, it creates the following;
SM_XXXCLNT100_READ
SM_XXXCLNT100_TMW
SM_XXXCLNT100_TRUSTED
What should I do? if it creates _TRUSTED ONE in PRD, should I delete it? Please help!!
Question: If I am generating auto RFC's for PRD, it created _LOGIN one too? I am totaly confused??
Thanks,
I will definitely post points

The only reason I want to do that because I have to talk to security folks for that, they will go and look at the other production environments which dont have _TRUSTED rfc...
Like as I have mentioned, all production has the following rfc's
SM_XXXCLNT100_LOGIN
SM_XXXCLNT100_READ
SM_XXXCLNT100_TMW.
I dont understand only one thing. how can I get _LOGIN rfc?
The only reason I am asking, when I did EWA in sandbox, It did not generate _LOGIN rfc...
Do you have any idea?
Thanks,

How to setup RFC Connection for SAPOSS?

Dear Experts,
I tried to setup the RFC connection for SAPOSS based on the following settings, but when I test connection, it failed.
Target system : OSS
Msg. Server : ... ( this where I stuck which I'm not sure what to fill in)
Group : EWA
Client : 001
User : OSS_RFC
Password : CPIC
Does anyone know the right settings?
Regards,
Abraham

Hi all,
Do I really need to setup our own SAProuter if our firewall doesn't block any outbound IP address?
I've tried the following settings in OSS1 but still failed to connect.
SAProuter at SAP :-
Name : sapserv3 ( or sapserv7 or sapserv2)
IP address : 147.204.2.5 (or 194.39.134.35 or 194.39.131.34)
Instance no : 99
SAPNet Message Server
Name : oss001
DB Name : 001
Instance No : 01
I left the SAProuter1 and SAProuter2 (at customer site) blank.
Did I miss out anything?

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

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: <b>User XIRWBUSER has no RFC authorization for function group CHECKRFCS</b>.
Self-Test status: <b>JCo request failed</b>.
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

Http RFC destination for ECC to PI Connection Error

Hi,
While doing the proxy runtime configuration http RFC destination for ECC to PI .
I configure the RFC destination as below ---
Target Host -- PI Host
Service No -- 50000
Path Prefix --- /sap/XI/engine/?type=entry
Login Security Details
User Id -- PI user id
Password --- PI password
While doing the Connection Test , I got the error "ICM_HTTP_CONNECTION_FAILED"
I checked T-code in ECC system SMICM and ICM is in green status and I checked the services are activated in SICF transaction.
Please let me know how to resolve this issue.
regards,
Rohit

Hi Rahul,
I checked all service are activated in SMICM and I configured the FQDN also.
Now I cofigured the Service No --- 8000(http port no of PI) instead of 50000(J2EEport no of )
Target Host --- hostname
and did a Connection test...then I am getting a status as "http reponse 500" and status text as "empty http request received".
pls let me know is it correct configured or not.
regards,
Rohit

EWA Error : EWA to SAP is allowed only for test or production syetm

I setup EWA in SDCCN, Choose Task ->Create ->Request session data-> Periodic:-EarlyWatch Alert.
At the last step to confirm, I received error "EWA to SAP is allowed only for test or production syetm".
When can I do?

Hi,
1. Which system for EWA
2. Create Production system for EWA and open the connection for SAP.
Regards,
Srini Nookala

Short dump while executing job SM:EXEC SERVICES for EWA alert generation

Hello All,
I'm getting short dump error while executing job SM:EXEC SERVICES for EWA alert generation.I'm using EHP1@SP22 of Sol Man.
Please find the logs
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RDSVASCABAP_TRANS__________073
" in include "RDSVASIABAP_TRANS__________073 " in
line 1782:
"Field "STATEMENT_SUMMARY001019" is unknown. It is neither in one of th"
"e specified tables nor defined by a "DATA" statement. "DATA" statement"
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
If anyone came across such kind of dump, please reply asap, due to this, i could not generate EWA report for R/3 system 6.04.
Thanks,
Anand.

>
Anand Tigadikar wrote:
> Thx Paul, but i already did checked this note and its not solving my issue
Dear Anand,
Did you perform a complete service definition replacement for SDCC/SDCCN as described in the note?
These are manual steps you need to perform on the system and are not code corrections.
I would suggest you perform it, if you have not, and check the SDCCN logs to review the process ran cleanly.
Note: Please make sure SDCC_OSS is functioning and a connection to SAP can be made before
deleting the service definitions.
If you have already replaced the service defintions on the Solution Manager system, then no point doing it again. However checking a note and applying it are not the same thing. So I am uncertain if you replaced the service definitions or not. The dump you are getting in SM:EXEC SERVICES suggests its due to a problem with the service definitons. The recommendation is to replace them according to the process described in SAP Note 727998. If you have not done so please do so.
If you have successfully replaced the service definitions are you still getting the same dump, or has it possibly changed?
Regards,
Paul

Java call rfc check in original:error while checking in and storing.

hi,experts.
java call rfc check in original:error while checking in and storing. BAPI in the RFC is "BAPI_DOCUMENT_CJANGE2",
the RFC was fine in SE37 and calling by Visual Basic. and in java,when mConnection.setAbapDebug(true), and runing by step and step, was fine too.
if mConnection.setAbapDebug(false) in JAVA, up error in title was displayed.
what cause this error?
Best Regards.

Hi Priya
Please use Su53 after getting the error and find any authorization is missing for the user..
S_GUI Full Authorization is required..
Since by giving BASIS Authorization its rectificed, then it shud be mostly due to Auth issues only
Regards
Aby

RFC destination for synchronous communication (message type SYNCH)

Hi experts,
I am trying to configuare ALE settings.waht i did is
My sending & receiving systems are one server with different clients.By using SALE transaction
1.crated logical systems.(LS_800 &LR_810)
2.Assigned those to clients.
3.Created RFC destination
4. Created modelview assign sending & receiving
systems and message type.saved it.
4.generated Partner profile.Here i am getting below problem
Target system LR_810
RFC destination for synchronous communication (message
type SYNCH)
Partner profile LR_810 SYNCH does not exist
Generate partner profile or
specify outbound partner profiles for message type
SYNCH
Target system LS_800
RFC destination for synchronous communication (message
type SYNCH)
Partner profile LS_810 SYNCH does not exist
Generate partner profile or
specify outbound partner profiles for message type
SYNCH
Regards;
Upender.

Hi Shital;
Thanks for your replay;
Still am getting the Same Error;
Thanks;
Upender.

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

Best practice for handling errors in EOIO processing on AEX?

Hi,
I'm looing for resources and information describing the best practice on how to handle processing errors of asynchronous integrations with Exactly-Once-In-Order QoS on an AEX (7.31) Java only installation. Most information I've found so far are describing a the monitoring and restart jobs on AS ABAP.
Situation to solve:
multiple different SOAP messages are integrated using one queue with an RFC receiver. On error the message status is set to Holding and all following messages are Waiting. Currently I need to manually watch over the processing, delete the message with status holding and restart the waiting ones.
Seems like I can setup component based message alerting to trigger an email or whatever alert. I still need to decide on how to handle the error and resolve it (ie. delete the errornous message, correct the data at sender and trigger another update). I still need to manually find the oldest entry with status waiting and restart it. I've found a restart job in Background jobs in configuration and monitoring home, but it can be only scheduled in intervals of 1 or more hours.
Is there something better?
Thank you.
Best regards,
Nikolaus

Hi Nikolaus -
AFAIK - For EOIO, you have to cancel the failed message and then process the next message in the sequence manually..
Restart job only works the messages which are in error state but not in holding state.. So you have to manually push the message... So there is no other alternative.
But it should not be that difficult to identify the messages in a sequence..
How to deal with stuck EOIO messages in the XI ... | SCN
Though it is for older version, it should be the same.. you should be able to select the additional columns such as sequence ID from the settings..

Rfc to file scenario error in sm58

rfc to file scenario error in sm58
i get the error as com.sap.aii.afccommunication.RfcAfwException
:look up of alternative

hey
>>i have a doubt do we have to use
starting new task or back ground destination
well it depends upon the logic ur gonna implement,both are used for async RFC so u have to see ur requirement and then decide.
have a look at the following
http://help.sap.com/saphelp_nw2004s/helpdata/en/22/042578488911d189490000e829fbbd/frameset.htm
thanx
ahmad

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.

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

RFC SAPOSS for EWA Error

Similar Messages

Maybe you are looking for