Fail in RFC call to PI

Hi,
I have a problem with communication of RFC call and PI
The situation is:
ECC calls RFC from report and by the background method with destination to PI.
but...the rfc stays fixed in transaction SM58...and the PI don't receive any message...
The message in SM59 call transaction is:
com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup rfc sender sm58
We have used the follows structure:
PI 7 with SP 9 - AIX + Oracle
SAP ECC 6.0 - AIX
Thank''s a lot for any help...
Sandra

Hi Sandra,
Great! I'm glad this worked.
I would only use this as a temporary solution though.
This happened because the SAP R/3 Business System that you've specified in your Integration Builder Configuration doesn't match the system (SID and client) that you're sending from. I would recommend correcting the Configuration and then checking this flag again. It's safer that way, because right now you could make calls from any R/3 system and XI would accept it.
To correct the Configuration, you'll likely need to:
1) Create a Business System for the R/3 system that you're making the RFC call from. If it's DEV client 100, you would create a Business System called DEV_100 for example.
2) Redo your configuration with this Business System.
3) Check the 'Verify Sender System' flag again in your configuration.
Thanks,
J Wolff

Similar Messages

RFC call failed: JCO.Server could not find server function 'SET_SLD_DATA'

Hi, All
the system is PI 7.0 EHP1 oraclei Win2003 server, I configured SLD but I run RZ70, having error "RFC call failed: JCO.Server could not find server function 'SET_SLD_DATA' ". I know there are lot of tread about this error, but none of themsolve my problem. all JCO, RFC connections and SDL DATA supplier(VA) seem OK. error message in SM21 is "Could not send SLD data"
detail from SM21
The system could not send the data that has been collected automatical
for the System Landscape Directory (SLD). Check whether the gateway
configured in transaction RZ70 has been started and whether the SLD
bridge has been registered with this gateway.
You can use transaction SM59 to check this in the sending system for t
implemented RFC destinations. The RFC destinations have the standard
names "SLD_UC" for Unicode sending systems and "SLD_NUC" for non-Unico
sending systems. If a different RFC destination has been entered in
RZ70, check this destination instead.
You can use the Gateway Monitor to check the target gateways. In ABAP
systems, this monitor is started with transaction SMGW, or you can use
the external SAP program "gwmon". Check whether the specified gateway
has an active registration.
OF COURSE I checked RFC of SLD_UC and SMGW
any different ideas
Regards
ABH

Hi
Please check the following notes are implemented
Note 906454
Note 907729
You may be aware but if you are not --->RZ70 creates the required SLD* RFCs during runtime - therefore if you have defined these RFCs manually first using the same namespace you can get RFC conflicts which result in a failed submission
Please also check the user in the RFC is known to both systems and has required authorization to write to SLD
Generally with SLD you have to install or select a suitable gateway to handle incoming data supply traffic
Also the gateway you are using has be known to SLD and reflected in RZ70 - i.e these defintions have to be the same
It is also recommended to delete all references to SLD_* RFCs in data supplier and target SLD
after a failed submission attempt to allow RZ70 to recreate these consistently once the above has been checked
Best wishes
Stuart

RFC call failing due to UNICODE implementation

Hi
We are trying to connect to a SAP system using the JCO (SAP-JAVA Connectivity). We are passing the user name as an input parameter and in turn the SAP system send back the no. of item (ABAP Type integer) pending for the user name to the java and its inserted/updated in Oracle DB (which does accept the unicode characters).
It was all wokring fine untill the SAP system has been migrated to Unicode upgrade. Now the RFC call is getting failed from our system. On analysis we found with debug, that the user name is not getting accepted by the SAP system and throwing the error -says Exception in thread "main" com.sap.aii.proxy.framework.core.BaseProxyException: Conversion error between two character sets., error key: RFC_ERROR_SYSTEM_FAILURE and at the SAP end the error says "Conversion of "UNAME" from code page 4103 to 4102 is failed". The unicode change in SAP system cannot be reverted back due to some constraints.
Can you please help, how can we pass the user name as encoded in character set 4102 or any other solution so that it can be accepted by SAP and run the Function module and return the data.
Many Thanks
Snehil Joshi

Check RFC destination in Tx SM59. You must have one tab for unicode settings.
Regards.

UPGRADE : RFC call to subst_save_upgeval_db failed with key UPDATE_ERROR

Hello.
We are upgrading our NW 7.01 to NW 7.3 ABAP.
In Postprocessing phase MAIN_POSTP/CREATE_UPGEVAL we encounter the following error:
ERROR: RFC of "subst_save_upgeval_db" failed
key: ERROR UPDATE
message: EXCEPTION UPDATE_ERROR RAISED
Here is the troubleshooting ticket:
This trouble ticket was created by SAPup on 20111125120155
SAPup broke during phase CREATE_UPGEVAL in module MAIN_POSTP / Post Processing
Error Message: RFC call to subst_save_upgeval_db failed with key UPDATE_ERROR (UPDATE_ERROR): EXCEPTION UPDATE_ERROR RAISED
Summary of SAPup:
SAPehpi Release:        lmt_002
SAPehpi Version:        SAPup release lmt_002 version 41.001
Start Release:          701
Target Release:         730
Summary of host system details:
SID:                    TA1
Host:                   sapta1
MS Host:                sapta1
GW Host:                sapta1
Start Path:             /usr/sap/TA1/DVEBMGS02/exe
Kernel Path:            /usr/sap/TA1/DVEBMGS02/exe
Summary of operating system details:
OS Type:                Linux X86_64
OS Version:             2.5
Summary of database details:
Database Type:          ora
Database Version:       11.2.0.2.0
Summary of RFC details:
Host:                   sapta1
GW Host:                sapta1
Client:                 000
Destination:            TA1
Language:
System No.:             02
here is the PHASES.LOG:
1 ETQ201 Entering upgrade-phase "CREATE_UPGEVAL" ("20111125120352")
4 ETQ399 Set environment for standard connect:
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '02', GwService = 'sapgw02'
4 ETQ399 Environment variables:
4 ETQ399   dbs_ora_schema=SAPSR3
4 ETQ399   auth_shadow_upgrade=0
1 ETQ200 Executing actual phase 'MAIN_POSTP/CREATE_UPGEVAL'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = 'STORE_DB'
4 ETQ359 RFC Login to: System="TA1", Nr="02", GwHost="sapta1", GwService="sapgw02"
4 ETQ232 RFC Login succeeded
Do you have anu ideas ?

Here is the dev_rd log:
Fri Nov 25 14:07:04 2011
***LOG S23=> GwIDisconnectClient, client disconnected (020) [gwxxrd.c     10423]
***LOG S74=> GwIDisconnectClient, client disconnected ( sapta1) [gwxxrd.c     10434]
***LOG S0R=> GwIDisconnectClient, client disconnected () [gwxxrd.c     10451]
***LOG S0I=> GwIDisconnectClient, client disconnected ( SAPCPIC) [gwxxrd.c     10464]
LOCATION    SAP-Gateway on host sapta1.sap.fr.alten.com / sapgw02
ERROR       connection to partner 'localhost.localdomain:0' broken
TIME        Fri Nov 25 14:07:04 2011
RELEASE     720
COMPONENT   NI (network interface)
VERSION     40
RC          -6
MODULE      nixxi.cpp
LINE        4850
DETAIL      NiIRead: 127.0.0.1:0
SYSTEM CALL recv
COUNTER     58

RFC call to spda_get_stack_info failed.

Hi All,
When carry out the system upgrade from 47x200 to 701 EHP4 SR1,
has a error in get stack info in the preparation step.
From windows 2003 x32 MSsql 2000 upgrade to windows 2008 R2 and MS sql 2008 R2.
Error message set: 'RFC call to spda_get_stack_info failed with key
RFC_ERROR_SYSTEM_FAILURE (SYSTEM_FAILURE): Error ST_MATCH_FAIL occured.
P1=element-start P2=sp-stacks P3= P4=element-start P5=SMSDXML P6='
Thanks.

Hello,
this error is happening because you're using an old version of SAPup and/or an old version of the Upgrade FIX file. Please make sure you're running the very last version of these files and repeat the process from the beggining.
Also the file ../EPS/in/SMSDXML.xml is actually not the XML file you want to use, it is a for R/3 release with
SAP_BASIS 4.x, the EHP stack configuration for start releses 6.20 and higher, these text files do not match anymore.
This can contribute for EHP_INCLUSION phase failing. Have you renamed it? It usually is a long file name, for example: SMSDXML_EP1_20111002154601.221.xml. Please make sure you or someone have not made manual changes in this xml.
I hope this information helps.
Best regards,
Tomas Black

First RFC call failed, config not loaded. Check the System landscape configuration.

Dear Experts,
We are getting below error on portal while using the BEX query in BI system.
Error:
BEx Web Application
Error: First RFC call failed, config not loaded. Check the System landscape configuration.
Exception occurred while processing the current request; this exception cannot be handled by the application or framework
Failed to process request; contact your system administrator
To facilitate analysis of the problem, keep a copy of this error page
We are sorry for the inconvenience.
As the ITS & WEB AS connection tests go successful on object created for BI system in portal.
Kindly suggest me on this issue..
Thanks,
Bharath.

Hi Bharath,
Please go through the below SAP Note and let me know if this helps.
1903392 - Error: First RFC call failed, config not loaded
BR,
Anurag

Itanium: Rfc call for SXMI_XMB_SYSLOG_READ fails Error INVALID_DATE_TIME

I have a distributed NetWeaver 2004S Environment: Main SAP Instance and Database are located in a CST Time Zone on the same machine. A dialog SAP instance, installed on an HP-UX Itanium Host, is located in a PST Time Zone, but, the system clock set for CST time - 2 hours behind the main SAP instance host system clock time.
My application is installed on the HP-UX Itanium Host and connects to the local (dialog) SAP instance, and makes RFC library calls to collect data. For Syslog data, the RfcCallReceive call is made to function SXMI_XMB_SYSLOG_READ with all the required input parameters. This call succeeds for the first time, but, fails all subsequent times if the call is repeated at 1 minute interval. Following error message is returned:
gid:105 key:INVALID_DATE_TIME
The date times on start and stop times are correct - they match very well with the system clock time.
Now, if I increase the repetition interval from 1 minute to 5 minute, the Rfc call to the function SXMI_XMB_SYSLOG_READ succeeds for the repeated calls.
Please note that the Rfc application was compiled on an HP PA-RISC development machine, and, uses ARIES emulator to run on HP Itanium Host.
There is another piece of information I can provide here if that helps: I am able to make 1 minute spaced repeated Rfc call to SXMI_XMB_SYSLOG_READ function with success on a PA-RISC dialog instance of another SAP deployment that has the main SAP instance plus database on one machine in a CST time zone, and, the dialog SAP instance hosting the application on PA-RISC host on a different machine, but, in the same CST time zone.

Hi Manoj,
The Application and the dialog instance are on the same machine - HP-UX IA64. This is what TZ has on this host
TZ=CST6CDT
How do I synchronize the application and the SAP dialog instance - they are located on the same physical machine?
The main instance and the database are on another machine - SunOS5.10 sparc. This is what TZ has on that host
TZ=US/Central
The date on HP-UX IA64 (dialog instance) is
date
Fri Nov 21 13:13:35 CST 2008
The date on SunOS5.10 sparc (Main Instance + Database) is
date
Fri Nov 21 13:13:35 CST 2008
Please note that the dialog instance and the main instance are located geographically in PST and CST time zones - being 2 hours apart.
I appreciate very much your effort. Looking forward to the follow-up.
Thanks

RFC call failed : Error when opening an RFC connection

Hi,
As a result of "Start Data Collection" operation in the t-code RZ70, I have got this error.
"RFC call failed : Error when opening an RFC connection"
Others things are with success message.
Regards,
Bala Raja

hi
check this links
http://help.sap.com/saphelp_nw04s/helpdata/en/9b/da0f41026df223e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/9b/da0f41026df223e10000000a155106/frameset.htm
also check Tcode: SLDAPICUST.
run tcode SLDCHECK? any error?
Thanks
Rodrigo
PS: If useful reward points

RFC call ended with "Communication Failure" exception (Function call failed; could not find the function

Hi All,
I am getting error while executing oDATA service from SAP Netweaver Gateway
Error details:
RFC call ended with "Communication Failure" exception (Function call failed; could not find the function
I am using SAP NG 740
Project is created in Gateway system using SEGW having Map to Datasource option used.
in SPRO manage alias, I had seleted Local App option. Screen attached
I had tried all troubleshooting like delete and add service and alias in "/IWFND_MAINT_SERVICE".
but still getting same error for all service.
Kindly advise.
Regards
Vivek

Hello Vivek,
Service builder would have also generated code for RFC Exception handling to catch exceptions raised when communication fails between your GW and BE for some reasons.
Handling is done for 1. System Failure 2. Communication Failure & 3. Business Failure;
Put a BP in your DPC or DP_EXT class where exception code is written to check what exactly is has caused communication failure.
Check if that RFC is existing in that destination or not.
For your reference : Code would be something like this. Put BP here and check the problem.
* Error and exception handling
IF lv_subrc <> 0.
* Execute the RFC exception handling process
 me->/iwbep/if_sb_dpc_comm_services~rfc_exception_handling(
 EXPORTING
 iv_subrc = lv_subrc
 iv_exp_message_text = lv_exc_msg ).
ENDIF.
Go inside this method and check to get info on what has to be done to resolve issue.
Check carefully what has gone wrong and fix it accordingly.
No need of adding service & deleting as problem is not because of that.
Regards,
Ashwin

XI RFC call failing

Hello,
 I am setting up a very simple scenario where I am making a sychronous RFC call to a BAPI in R/3 (Version 4.6c) from an XI Sandbox (Version 7.0).
 I have the RFC Communication channel properly configured, or so I think, and have verified everything else as well. I initiate the message from the Runtime Workbench and it shows with status "Successful" in the Message Monitoring section. However, when I look in SXMB_MONI transaction I am unable to find a response message from the BAPI coming back in the payload. I notice that even though the scenario is synchronous, the "Type" column in the SXMB_MONI transaction results shows it as "Asynchronous". Also, in the message details there is a Payload (which I am sending when I create and send the message from the RWB), in every step, until the Call Adapter step. After that there is no payload in the Call Adapter or the Response steps, just the SOAP Body with the Manifest.
 In the message details I see that the <SAP:Processing Mode> entry is set to "Asynchronous" rather than "Synchronous".
 Does anyone have any idea why this is so?
Thanks,
Murtaza.
Message was edited by:
 Murtaza Madraswala

Hi Amitabha,
 I looked in the location you suggested and got a list of "Success" messages. These are listed below for you to look at:
Time Stamp Status Description
2007-06-18 15:17:54 Success Message successfully received by messaging system. Profile: XI URL: http://camapox1:50100/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
2007-06-18 15:17:54 Success Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2007-06-18 15:17:54 Success Message successfully put into the queue.
2007-06-18 15:17:54 Success The message was successfully retrieved from the receive queue.
2007-06-18 15:17:54 Success The message status set to DLNG.
2007-06-18 15:17:54 Success Delivering to channel: GeneratedReceiverChannel_RFC
2007-06-18 15:17:54 Success MP: entering
2007-06-18 15:17:54 Success MP: processing local module localejbs/RfcAFBean
2007-06-18 15:17:54 Success RFC adapter received an asynchronous message. Attempting to send tRFC for Z_SD_RFC_ATP_WRAPPER with TID XIlc32S1tf4Togkm0mRWaHRG
2007-06-18 15:17:55 Success MP: leaving
2007-06-18 15:17:55 Success The message was successfully delivered to the application using connection RFC_http://sap.com/xi/XI/System.
2007-06-18 15:17:55 Success The message status set to DLVD.
 The problem that I am seeing is that this is posted under the list of Asychronous Received Messages. Thats something I am just unable to understand. I have a Synchronous Outbound Interface defined and an RFC Communication Channel, which is Synchronous as far as I know. So why is the processing mode for the message being chosen as Asynch? Which config setting have I missed that is causing this problem? I am just unable to find the answer so far.
 I appreciate your help. Please let me know if you have any clues.
Thanks,
Murtaza.

Backgroung job failing becuase RFC function module is running in Dialog

Hi,
I have a program which is calling a RFC function module. I am running this program in background as a job. Now this function module which is in other system is running in Dialog and giving a time out error and the job is failing becuase of that.
I tried call fucntion 'test' in background task
destination 'XVZ'
tables
test = 'test'.
But this is not working, i can still see this function module running in Dialog in SM50. Any suggestion?
Thanks,
Shweta

Hi !
RFC-Called function-modules are running in a dialog workprocess of the
target system (they could not run in a batch proecess !!).
That means the do have the same "Timeout" limitations than any other
Dialog-Process.
What you can do:
- The Dialog "Timeout" could ce increased by your SAP-BASIS
- If they could not - you should "shorten" the LUWs in the target-funktion.
...means - put a COMMIT WORK an any point the work is done.
After a COMMIT WORK the "Timeout" Counter beginns at 0 !
Hope that helped....
Reward points would be nice...

Error in starting SAP GUI as part of an Java RFC call from a PC

Hi,
We are on the 4.6C version of SAP and have the latest basis kernel patches that allow an RFC connection to start the SAP GUI. The program that I am running externally is java using the 3.0.1 JCo. The OS of the PC I am using is Windows XP. The SAPGUI version is 7.10 patch level 11.
The program seems to be working properly as the command prompt window goes grey as if there is another window being opened but then I get back this error message and I do not see the GUI.
The message I am getting back is:
Exception in thread "main" com.sap.conn.jco.JCoException:(136) JCO_ERROR_ILLEGAL_STATE:Launching SAP GUI failed, though it was requested(error message:Communication with SAPGUI timed out)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.startSAPGui(MiddlewareJavaRfc.java:1853)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.connect(MiddlewareJavaRfc.java:1285)
at com.sap.conn.jco.rt.ClientConnection.connect(ClientConnection.java:661)
at com.sap.conn.jco.rt.PoolingFactory.init(PoolingFactory.java:103)
at com.sap.conn.jco.rt.ConnectionManager.createFactory(ConnectionManager.java:171)
at com.sap.conn.jco.rt.DefaultConnectionManager.createFactory(DefaultConnectionManager.java:44)
at com.sap.conn.jco.rt.ConnectionManager.getFactory(ConnectionManager.java:160)
at com.sap.conn.jco.rt.RfcDestination.initializ(RfcDestination.java:766)
at com.sap.conn.jco.rt.RfcDestination.getSystemID(RfcDestination.java:794)
at com.sap.conn.jco.rt.RepositoryManager.getRepository(RepositoryManager.java:32)
at com.sap.conn.jco.rt.RfcDestination.getRepository(RfcDestination.java:865)
at GISToSAPWO_Test.get_wo_call(GISToSAPWo.java:91)
at GISToSAPWO_Test.main(GISToSAPWO_Test.java:206)
I have been all over trying to find the solution to this and have come up empty. Any help will be greatly appreciated. If this is the wrong forum for this please let me know and I will re-post.
Thank you in advance for any information you can pass on about the issue,
Mark

Hi Greetson,
Thank you in advance for your response. It is greatly appreciated.
1) In a way yes. I am using the connection setting USE_SAPGUI = 1. This is suppose to start the GUI prior to starting the RFC's program run. If this is not correct please let me know.
2) The code is part of the JCo and the RFC library from what I have read. If this is not correct please let me know.
3) I am only testing from my PC at this moment. I have re-installed my SAP GUI and am now at patch level 13 on 7.10.
4) The application passes in the connection information which includes username and password along with the parameters for the RFC call. I would like the SAP GUI to open without the user having to re-enter his/her username and password. I thought that once the RFC is called using the dialog users credentials that the GUI would then open using the connection. I have used the java pooled connection method and it still does not open the GUI.
5) The purpose is to pass Equipment objects, Functional Location objects and Leak Id objects to an RFC to open a list screen from IW39, List Maintenance Order transaction, for display of each at one pass, as well as open Excel with data from classification for the Leak Id's.
Hope this sheds some light on the problem I am having. Please let me know if more information is needed.
Best regards,
Mark

Problem passing a table parameter in rfc call using the function control

I try to pass a Table as parameter to a Function Module using the SAP.Functions library (part of SAP frontend controls) from a Visual Basic (VBA) program.
The function module has been verified to work when invoked from SAP FrontEnd Function Builder.
The SAP RFC Control is created with
Set sapFunctions=CreateObject("SAP.Functions")
Following code snippet shows how I attempt to set exports and add a table row before calling the function module:
sapFunctions.Connection = sapConnection
Set sapMaterialUpd = sapFunctions.Add("Z_SD_BAPI_SALES_DATA_UPD")
With sapMaterialUpd
'set exports
 .Exports("PA_GLPUPDLEVEL") = "S"
 .Exports("PA_VKORG") = "FI14"
'append table row
 .Tables("IT_SALES_DATA_UPD").AppendRow
 .Tables("IT_SALES_DATA_UPD")(1, "VKORG") = "FI14"
 .Tables("IT_SALES_DATA_UPD")(1, "MATNR") = "W_3100"
 .Tables("IT_SALES_DATA_UPD")(1, "DATBI") = "99991231"
 .Tables("IT_SALES_DATA_UPD")(1, "DATAB") = "20041231"
 .Tables("IT_SALES_DATA_UPD")(1, "KBETR") = "2222"
 .Tables("IT_SALES_DATA_UPD")(1, "KONWA") = "EUR"
End With
'call the function module
If sapMaterialUpd.Call() = True Then
 'do something with the return tables here...Else
 Debug.Print sapMaterialUpd.Exception
End If
The Call() returns FALSE and the exception is "SYSTEM_FAILURE". The connection also resets.
The local logfile that the control generates shows that an exception occurs at the point of the call:
10.02.2005 17:54:20.766 Packing Parameters for Z_SD_BAPI_SALES_DATA_UPD
Packing Parameter PA_GLPUPDLEVEL.
Packing Parameter PA_VKORG.
Packing Table 0.
Packing Table 1.
10.02.2005 17:54:20.766 *** Calling RFC Function 'Z_SD_BAPI_SALES_DATA_UPD'
10.02.2005 17:54:20.986 RFC CALL status = RFC_SYS_EXCEPTION
10.02.2005 17:54:20.986 RFC Error: RFC_IO27
-Status:CODE=CM_DEALLOCATED_NORMAL STATUS=CM_NO_STATUS_RECEIVED DATA=CM_COMPLETE_DATA_RECEIVED ID=69415076
-Message:connection closed
-Internal Status:IO HANDLE=23 DRV=EXT LINE=1420 CODE=27 : GET ID=ffff LINE=861 CODE=7
10.02.2005 17:54:20.986 Function call finished.
Seen next code snippet. If the Table object is not touched, the function call goes through without any problems:
sapFunctions.Connection = sapConnection
Set sapMaterialUpd = sapFunctions.Add("Z_SD_BAPI_SALES_DATA_UPD")
With sapMaterialUpd
'set exports
 .Exports("PA_GLPUPDLEVEL") = "S"
 .Exports("PA_VKORG") = "FI14"
 'do not append a table row, for testing only ;-)
End With
'call the function module
If sapMaterialUpd.Call() = True Then
 'do something with the return tables here...
Else
 Debug.Print sapMaterialUpd.Exception
End If
This code works perfectly when calling the function. It returns TRUE and behaves normally. The function module returns descriptive response text in a table telling that the table was empty, according to the BAPI implementation.
So is there something special needed here after appending the table row and before making the Call to properly attach the table as a parameter for the function module?
Can this be a bug in the SAP RFC Control? The version of the wdtfuncs.ocx is 6206.6.45.54.
Any hints are welcome!

hi All partner,
who solved this problem , I meet it too and
can't clear it.
SAPfunc := sapfunctions1.Add('z_get_sfcs_dn_mo');
SAPitab := sapfunc.tables.item ('I_DNMO');
SAPitab.appendrow; SAPitab.value(1,'MANDT') := '220';
SAPitab.Value(1,'VBELN') := '2150000001';
SAPitab.Value(1,'POSNR') := '50';
SAPitab.value(1,'MATNR') := '19-99999-00';
SAPitab.value(1,'AUFNR') := '921241512001';
SAPitab.value(1,'DEDAT') := '2005/09/09';
SAPitab.value(1,'LFIMG') := '100';
IF SAPfunc.call = true then
begin
end
else
 begin
 showmessage('call fail!!') ;
 end;
end;
RFC source code as below
FUNCTION z_get_sfcs_dn_mo.
""Local interface:
*" TABLES
*" I_DNMO STRUCTURE ZDN_MO
data: wa type zdn_mo.
LOOP AT i_dnmo.
 wa-mandt = i_dnmo-mandt.
 wa-vbeln = i_dnmo-vbeln.
 wa-posnr = i_dnmo-posnr.
 wa-matnr = i_dnmo-matnr.
 wa-aufnr = i_dnmo-aufnr.
 wa-dedat = i_dnmo-dedat.
 wa-lfimg = i_dnmo-lfimg.
 modify zdn_mo from wa.
 insert into zdn_mo values wa. --dump at here
 commit work.
ENDLOOP.
T/C: ST22 error message say at
insert into zdn_mo values wa. ---dump at here
the sapfunc.call returns fail.
Message was edited by: jorry wang

Question on service userid - for RFC call

Hi
In XI 3.0 SP18 , we are making a RFC call from XI mapping runtime - to XI's ABAP stack - RFC function module . In the RFC receiver communication channel , I tried using service user XIISUSER , XIAPPLUSER for this RFC call - I got short dumps on XI ABAP stack mentioning that these two service users do not have authorization to make RFC calls -
Does anybody out there know what service user on XI has RFC call authorization that can used to make RFC calls onto XI ABAP stack from its mapping runtime ?
Correct answers will be rewarded rightaway. Thanks for your time in advance.

Hi,
u have to make entry in sld...
Hi,,
2 Introduction
Configuring IDoc adapter in Exchange Infrastructure 3.0 requires some configuration on the SAP
systems, for both XI and the backend system where the IDoc message is to be sent. These steps, although
simple, are many times missed or mis-configured, causing the delivery of messages to fail.
Since IDoc adapter uses the ABAP stack, instead of J2EE, the configuration requirements are mainly in
ABAP.
Setting up IDoc adapters requires the XI integration server to be able to communicate with the backend
SAP system, and also to make sure that the Logical System Name used when posting IDoc exists on the
backend SAP system.
3 The Step By Step Solution
The basic steps for the IDoc configuration are outline below:
1. Configure SM59 on XI to communicate to SAP backend system.
2. Configure port on XI for IDoc communication.
3. Create or verify the Logical System Name on the SAP backend system.
4. Create or verify business system in XIs System Landscape Directory.
5. Verify the Logical System Name of the business system.
6. Verify or add the Logical System Name for the sender business system.
7. Create/configure the Communication Channel for the IDoc receiver adapter
3.1 Configure SM59 on XI to communicate to SAP backend system.
1. Using transaction SM59, create an RFC destination with Connection Type = 3.
In this example, the RFC destination name is NDVCLNT510.
2. Enter the logon information:
3. Test the connection by clicking on Testing connection and Remote logon.
Both must be successful.
3.2 Configure port on XI for IDoc communication.
4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is SAPNDV.
The Port name must be in the form of SAPxxx, where xxx is the system ID of the backend SAP
system.
The Client must be the client number of the backend SAP system.
Select the RFC Destination which was created in the previous step.
3.3 Create or verify the Logical System Name on the SAP backend system.
5. Enter transaction SALE on the SAP backend system.
6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.
3.4 Create or verify business system in XIs System Landscape Directory.
The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.
7. In the System Landscape Directory, select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical System Name.
3.5 Verify the Logical System Name of the business system.
8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).
Navigate the menu:
Service Adapter Specific Identifiers.
If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.
9. (Optional) Synchronization of the business system in Integration Directory to the business system in System
Landscape Directory.
Double-click on the business system in the Integration Directory.
Switch to Edit mode.
Select menu: Service Adapter-Specific Identifiers
10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.
11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.
3.7 Create/configure the Communication Channel for the IDoc receiver adapter.
15. In the Integration Directory, create an IDoc receiver communication channel.
The RFC Destination is from step 3.1.
The Port is from step 3.2.
NOTE:
There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
4 Appendix
Transaction: IDX2
There are a couple of situation where IDX2 can be useful on the XI system.
1. When we want to test connection between the XI and SAP backend system.
2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the
meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.
Go to transaction IDX2 and click on Create.
Enter the IDoc Type and the Source Port as defined in step #2. Click Continue.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.
Reward points if find useful.

RFC call in background error

We are having a unique problem in upgrade BW system. We have several RFC function calls in start routine and abap programs to R/3 and APO systems. After the upgrade these calls are not working in background. When we run the program online/dialog the RFC calls are fine and we get the data back. But when run in background we get CALL_FUNCTION_REMOTE_ERROR with "Name or password is incorrect. Please re-enter" message in the dump.
We have checked the RFC destination password for ALEREMOTE and they are okay. We have even tried all upper case or all lower case password options but still does not work. It seems like RFC call in background from BI 70 to non-70 (APO 3.0), the system is not passing the password in right format or something related to encryption problem.
We came across following links but not sure if it applies. Any input on this topic is appreciated.
Note: 792850
http://help.sap.com/saphelp_nw04s/helpdata/en/52/6717ed439b11d1896f0000e8322d00/frameset.htm
Regards
-Bala

Michael,
It is not the problem with the user. All or any user - works fine when run online and fails in the background.
Regards
-Bala

Fail in RFC call to PI

Similar Messages

Maybe you are looking for