Why is the RFC Adapter so unstable

Hi all,
I have a scenario where an IDOC is sent from the sender system and an RFC enabled Function Module is called on the target system. Sometimes I get an error in the Adapter for no aparent reason. I check the RFC adapter trace file but none of the exceptions was raised and I am not able to see what was the problem.
But, if I restart the RFC Adapter and send the IDOC again, everything's allright. Why? Is there any other trace avilable somewhere? Is there any way to restart the RFC Adapter periodically and automatically?
Thanks and regards,
Nuno

This sounds like a bizarre scenario. Why would a Idoc (asynchronous) be calling an RFC (synchronous)?
Unless the RFC is doing update? Then you have more problems. You are mixing your QoS from EO to BE. The delivery is no longer guaranteed. The posting to the RFC could work but XI may not get the acknowledgement - RFC adapter does not do commit so you must have a commit in the remote function. If no acknowledgement is received, do you resend and risk duplicate updates? How do you guarantee EO delivery? The sender system is right in expecting EO for it's outbound Idoc.
In all the training material RFC is intended for data retrieval, not data posting. This is consistently done with Idoc (EO, or EOIO).
I would consider changing the scenario to Idoc->xi->Idoc.

Similar Messages

Problems in connecting the RFC adapter

Hi all,
we are using XI 3.0 which has been installed very recently. I am trying to configure the RFC adapter but i am getting an error "program <progname> not registered".
I have set up a TCPIP connection on the ECC system with the parameters :
gateway host: hostname of ECC system
gateway service : sapgwXX where XX is system number of ECC system
activation type : Registered server program ZXXXXX
On the XI system, I am creating a communication channel of type RFC sender with the Integration server as the adapter engine
RFC server parameters:
Application Server : hostname of ECC system
application Service: sapgwXX where XX is system number of ECC system
program ID : ZXXXXX (case-sensitive)
RFC metadata parameters:
application server : hostname of ECC system
system number : system number of ECC system
Logon Details of the ECC system
I am confused about which details to give where, but i have followed Michal's blog .
I am still getting an error . Could you please help in sorting out this matter?
Thanks,
Amit

Hi
RFC metadata parameter login should be U R ECC system login s and correct.
What is u r error.
Steps shown in the blog is all fine it works , no other configuration needed.
I guess u r testing the TCP RFC connection , u configure u r Sender RFC use the Register Program id same what u have used in the RFC (case sensitive) and run the scenario
it will work.
Regards
Srini

Why is the OTN forum so unstable ?????

Why is the OTN forum so unstable ?????
I haven't seen any other Forum on the WORLD WIDE WEB being so slow/unstable?
Maybe you should move over to some MS products (FYI this was a jocke).

Here here!
"I haven't seen any other Forum on the WORLD WIDE WEB being so slow/unstable?" - exactly how I feel too!!!
Error 404 many times each day and loosing posts due to "internal error" or what have you! I have mailed a few times to "webmaster" but nothing...
I think this is really bad PR, but what do I know ;)

Why does the hdmi adapter(purchased from apple for $40) no longer mirror my iPad 2?

Why does the hdmi adapter(purchased form Apple for $40) no longer mirror my ipad 2? If ios6 prevents this, will they return my money?

Does this involve iPhoto in any way? I believe you need to post in a different forum - and since these are strictly uuser to user forums answers about what Apple does or will do are not likely nor reliaible - you need to contact Apple for Apple answers
LN

Using the RFC adapter (sender), how do I know which RFC is being sent?

Hello everyone!
Has anyone used the RFC adapter (sender) in XI to pick up RFC messages? How would I know which RFC is triggered for example when a user creates a PO (purchase order)?
Warm Regards,
Glenn

Glenn,
When u are writinfg RFC program, u will have destination right? There u know u have to give RFC Destination(SM59) while creating RFC destination we will be giving Program ID .
Similarly in XI while creating Sender RFC u have to give the program id. So with these program id these programs are linked together and triggered from R/3 to the exact Sender adapter.
Please see Michal weblog for more details
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
I hope it clears your doubt!!!
Best regards,
raj.

Why is the 30pin adapter £25?! Why not include it free?

This seems like a tax on loyal fans who have a wealth of 30pin accessories (my BOSE sounddock being one of the eye-wateringly expensive ones).
It just feels like a big "screw you" from Apple.
If the adapter was included free with the iPhone 5 - or was even reasonably priced I wouldn't mind. But £25 for somethat that has a unit cost to apple you could measure in pence is the complete opposite of caring about the customer.
Can anyone think of a justifyable reason for the cost; other than "Because they can"?

compared to many others apple have really stuck with the same connector for a long time
11years is a long time using the same electronic connector
but I agree it's pretty pricy

Why Is the Outlook Mail Website Unstable in Internet Explorer 9 and 10?

I had to reset my Internet Explorer 9 browser on Windows Vista and my Internet Explorer 10 browser on Windows 7 the other day and now I can no longer view the Outlook Mail Website or the Outlook Calendar website, etc. They
keep making the browsers close. I've had this problem before, but I can't remember how I fixed things. Can someone please help me out? I can view these web pages in the Google Chrome browser for time being.

Fawad and Robert Aldwinckle,
I'm sorry that I took so long to get back to you; I've really been struggling with this thing. No Fawad, your suggestion didn't help. I wanted to tell you about a partial success that I've had. Perhaps you will be able to short cut my task once
you have read this. By disabling the XML HTTP 3.0 and XML HTTP 6.0 Microsoft Add-Ons, I have been able to make the Outlook.com email, People and SkyDrive pages stable. The Calendar page is the only one that still makes my browsers
crash. Furthermore, if I try to fiddle with the Calendar page by restoring the page, etc. instead of just shutting down the browser, it will cause the Skype program to sign me out! Let me say that I'm signed into Skype with a Skype
account as opposed to my Microsoft account. Does this give you any ideas?
I too was thinking this is a security setting issue. The website address for the Calendar page is different from that of the other 3 Outlook pages in that it doesn't result in the address box of the browser turning green as it does for the
other 3 pages. Near the "lock" icon in the website address box for the Calendar page, it does not show verification by VeriSign and the Microsoft Corporation. It's verified by someone else. People in England have had problems seeing
their Calendar page because of verification errors.
I wonder whether some scripting settings need to be changed in the security settings tab in Internet Options..
Thanks,
Greg

RFC receiver adapter issue - ECC side we are seeing blank data for the RFC

Hi All,
We are using Receiver RFC adapter to call a custom RFC (Synchronous call). It was working fine, but recently RFC was modified (They added new fields). We re-imported the RFC into ESR and also modified the mapping to reflect the new RFC strucuture. Now when we execute the RFC, at the ECC side no data is beeing seen. On the PI side we see data in sxmb_moni. It looks fine. However we don't see anydata in ECC. We did full cache refresh but it did not help.
Please let me know if anyone has any thoughts on this issue.
Thanks
-Pradeep

I enabled the the RFC adapter trace in PI. It appears like adapter is not sending the structure and tabled that are populated. IT is sending only 230 bytes. Any clue why would rfc adapter drop the tables and structures??
FUNCTION Z_FI_AA_BAPI_ASSET_CHANGE
    handle = 2
    parameter   = <null>
    parameter   = <null>
    tables = <null>
>>>> [2] <unknown> EXT <ac: 6> >>> FLUSH (READ) (88578752)
Send RFCHEADER [2]: 01/BIG/IEEE/SPACE-U2/52494850
Send UNICODE-RFCHEADER [2]: cp:4102/ce:IGNORE/et:6/cs:2/rc:0x00000023
UUID: send_rfcuuid B6D708F0-B946-11E0-BC35-EEB4AC138154
UUID: RfcCallNew send the uuid to the partner:B6D708F0-B946-11E0-BC35-EEB4AC138154
>>>> [2] <unknown> EXT <ac: 7> >>> WRITE (88578752)
000000 | 01010008 01020105 04010002 01010103 |................
000010 | 00040000 020B0103 0106000B 04010002 |................
000020 | 01060200 00002301 06000700 1A003100 |......#.......1.
000030 | 37003200 2E003100 39002E00 31003200 |7.2...1.9...1.2.
000040 | 39002E00 38003400 07001100 02004500 |9...8.4.......E.
000050 | 11001200 06003600 34003200 12001300 |......6.4.2.....
000060 | 08003700 30003000 20001300 08001800 |..7.0.0. .......
000070 | 73006100 70007000 69002D00 64006500 |s.a.p.p.i.-.d.e.
000080 | 76002D00 64003100 08000600 28007300 |v.-.d.1.....(.s.
000090 | 61007000 72006400 62002D00 64006500 |a.p.r.d.b.-.d.e.
0000a0 | 76002D00 64003000 5F004400 52003300 |v.-.d.0._.D.R.3.
0000b0 | 5F003000 30000605 140010B6 D708F0B9 |_.0.0...........
0000c0 | 4611E0BC 35EEB4AC 13815405 14050200 |F...5.....T.....
0000d0 | 00050200 0B000600 36003400 32000B01 |........6.4.2...
0000e0 | 02003200 5A005F00 46004900 5F004100 |..2.Z._.F.I._.A.
0000f0 | 41005F00 42004100 50004900 5F004100 |A._.B.A.P.I._.A.
000100 | 53005300 45005400 5F004300 48004100 |S.S.E.T._.C.H.A.
000110 | 4E004700 45010203 37000003 37051400 |N.G.E...7...7...
000120 | 10B6D708 F0B94611 E0BC35EE B4AC1381 |......F...5.....
000130 | 54051401 3100E62A 54482A03 00E60000 |T...1..TH.....
000140 | 00000000 00000000 00000000 00000000 |................
000150 | 00000000 00000000 00000000 00000000 |................
000160 | 00000000 00000000 00000000 00000000 |................
000170 | 00000000 00000000 00000000 00000000 |................
000180 | 00000000 00000000 00000000 00000000 |................
000190 | 00000000 00000000 00000000 00000000 |................
0001a0 | 00000000 00000000 00000000 73617070 |............sapp
0001b0 | 692D6465 762D6431 5F445049 5F313839 |i-dev-d1_DPI_189
0001c0 | 34303530 00000000 00000000 63303432 |4050........c042
0001d0 | 35313733 62393435 31316530 38373562 |5173b94511e0875b
0001e0 | 30303030 30303163 65366132 00000000 |0000001ce6a2....
0001f0 | 02C04251 73B94511 E0875B00 00001CE6 |..BQs.E...[.....
000200 | A2B6D708 F0B94611 E0BC35EE B4AC1381 |......F...5.....
000210 | 54000000 01000000 002A5448 2A0131FF |T........TH.1.
000220 | FF0000FF FF000000 00000000 00000000 |................
   >> CPIC native call CMSEND [2] convid: 88578752 14:23:39,159
   << CPIC native call CMSEND [2] convid: 88578752 rc: 0 14:23:39,159

Problem when calling the RFC and IDoc adapter at the same time

Hi,
I'm having a major slowdown problem with XI3.0 SP11.
When I'm sending a message(IDoc) from R/3 into XI to get translated into an EDI document, I have no problems and it's very fast. RFC calls are very fast too.
Now, if I'm sending the same message and at the same time another call is done trough the RFC adapter, then the full XI environment hangs for several minutes.
I did all recommended settings from the XI-SR1 install guide(Configuring the J2EE Engine) and tuning guide (XI Configuration Parameters)
and I don't know what to do more? At the Unix level, command TOP shows that dw.sap.XDV_DVEBMGS70 is taking all the CPU% available when both messages(IDoc and RFC) are sent to XI at the same time.
Anybody have an idea what to do next?
Rgds,
Yves

Did you check the dev_rfc logs ? Also check SM21 for any errors. Logon to the Target System and check SM50 transaction then you will know whats going on.
regards
Shravan

When RFC-Adapter is down, only the adapter-status shows error flag

Hi all,
How can I reprocess a message that did not reach the endpoint because the rfc-adapter was down, if the overall status of the message is "Message Processed"?
Thaks,
Nuno

Hi,
The question is about receiver RFC adapter and not about the sender RFC adapter. So single / mass re-start from SM58 won't help (Report RSQIWKEX for q-RFC and report RSARFCEX for t-RFC).
If RFC adapter is down, message won't reach to the destination system via adapter engine. IE monitoring will say that message is successfully processed (so report RSXMB_RESTART_MESSAGES will not help) . In this case, if you go to adapter engine monitoring from RWB, you will be able to see the status Waiting or System error.
I'm not sure how to re-start this message, but probably you can do this through MDT.
May be SAP note - 813993 will help you.
Good Luck & Bapu, Jalasa Kar........

RFC Sender problem between 46D and RFC adapter

Hi,
I have this simple integration scenario where I want to send data to a archiving system;
SAP -> (tRFC) -> XI -> (MQ) -> BizTalk -> (MQ) Arch.syst.
SAP side ***
A Z-program using a Z func. like;
    CALL FUNCTION 'ZSD_DCF_SEND_TAG'
      IN BACKGROUND TASK
      DESTINATION 'XISYSTEM_TRFC_DCF'
      EXPORTING
        pt_filing_info = gt_filing.
    COMMIT WORK AND WAIT.
XI side ***
Both IR and ID is configured correctly, in the development environment everything works just great. I have created a test program where I can define how many calls I will do, looping over the func. call with a commit inside the loop - 500 or more msgs are ok.
The integration scenario is transported to quality enviroment using CMS, and the RFC sender comm.ch. is configured accordingly.
The problem in quality ***
When sending just 1 msg, everything is just fine, message received and delivered to MQ.
When sending >= 2 msgs, the 1 msg is always ok, BUT all others fails due to the following from Adapter monitor;
RFC_HISTORY
- Error: 2006-01-19 10:55:18 CET: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'RFCSender_XI0002' (02d4d30de3593874942ed0659add0827, party '', schema 'TechnicalSystem', identifier 'Q93#120')
- OK: 2006-01-19 10:55:17 CET: Message processed for interface ZSD_DCF_SEND_TAG
My sending system is Q93 CLI 505 so I can understand the error, BUT I cannot understand why the RFC adapter is saying the TechnicalSystem is Q93#120 - it should be Q93#505. My Q XI has client 120...
It seems to me that the RFC adapter is kind of confused about the sender..
I have created a OSS message and SAP has looged on and looked into it with both a XI expert and RFC expert without being able to answer - all is configured correctly.
- The SLD config. for bus.system Q93 is ok -
- The bus.system in ID is showing correct vaues for
Adapter Specific Identifiers (SID Q93, client 505)
- Both Dev. and Qual. environment are running on XI 3.0 SP 14 latest patch, RFC component version on the SAP side is identical between dev. and qual. SAP systems
- It doesn't matter which gw I use (Q93 gw or XI gw), the error is persistent
- It doesn't matter if I increase initial conn, max conn.
I have also tried to use qRFC instead, but with the same result.
Anyone using tRFC for asynch. communication from SAP to XI seeing something similar?
Meanwhile, I will do RFC trace on GW and RFC Adapter on AE....
Please, do not say SP15, oss msg for FAQ RFC adapter or links to RFCAdapter config....
best regards
Torstein

Hi,
SAP Note 730870 FAQ: XI 3.0 RfcAdapter Q.no 15
<i>Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?
A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".</i>
- Give correct appserver and gateway service details in XI.
- Open the service holding the RFC adapter you are trying to use. On the top menu, goto Service -> Adapter Specific Identifiers..
Regards,
Prateek

RFC Adapter not getting data

Hi experts!
I am developing a RFC to File scenario on PI 7.1 EHP1 and ECC 6.0 which is synchronous. Following the Help page Setting Up an RFC Destination for the RFC Adapter I created two destinations. The fist one is a TCP/IP, name RFCDE1COMPANY2, program id BAPI_COMPANY_GETLIST and corresponding gateway host and service I found at SMGW (Parameters). The second one is a Logical with name RFCDE1and reference entry RFCDE1COMPANY2.
At my RFC Sender Adapter I configured the same gateway info and the same program id. After that I tested both destinations and it worked. I created the following report to call the bapi on that destinations::
REPORT ZREP_BAPI_COMPANY_GETLIST.
DATA: company_list TYPE STANDARD TABLE OF BAPI0014_1.
CALL FUNCTION 'BAPI_COMPANY_GETLIST'
IN BACKGROUND TASK
DESTINATION 'RFCDE1'
TABLES
COMPANY_LIST = company_list.
COMMIT WORK.
At SXMB_MONI the request message was processed and the output file generated, but it has only the root tag. At moni the inbound message has no data (company data).
I tested the BAPI_COMPANY_GETLIST at SE37 and there are 149 entries. When I executed this same BAPI with RFC target sys configured to my destination, it didn´t show any data and has an exception called SYSTEM_FAILURE. I think probably the error is on RFC destinations but I can´t figure it out what is wrong.
Best Regards,
Gabriela

Hi experts,
Thank you all for your quick response.
At the TCP/IP Destination there is a button "Unicode Test", according to this test my target system is unicode (character size 2). I changed the option at MDPM&Unicode on that TCP/IP Destination like Madhusudana described. I also selected the checkbutton "Unicode" on sender RFC communication channel.
About the sync/async, I will not use sync async bridge because this scenario can be async. One think that I realized is that when I call my report, I am implicitly calling PI asynchronously and when I call the BAPI directly by the test tool, I am implicitly calling PI synchronously. That is why most part of my tests did not work before.
Now I can see on SXMB_MONI that the scenario worked and the file was generated. But the data are still not being showed on inbound payload. I think something is wrong with my destinations but I can´t figure it out what is.
Ps.: I would prefer to use XI proxies, but this scenario will be configured (not now) on a XI 3.0 with ERP 4.6 C. Now I´m just learning how to handle with RFC Adapter.
Any ideia?
(Points granted)
Thank you and best regards,
Gabriela

RFC Adapter - Locking Issue

Hi,
Our SAP production environment was down for two days. While it was down the login used by one of my RFC Receiver Adapters was locked. This meant the adapter could not run. Fair enough.
When the Production environment was brought back up the login used by the RFC Receiver Adapter was unlocked. However, I continued to get an error in Runtime Workbench claiming that the login was locked.
Checked with the security team and they confirmed the user wasn't locked.
Just to try something I went into the RFC adapter in question and simply retyped the login/pwd, saved the adapter and activated it. This seemed to clear the problem and it's now running as expected !!
Question is why did this work ? The adapter was saying the login was locked. It wasn't. All I did was effectively resubmit an updated version of the adapter and it worked again, even though no part of the adapter had actually changed. Is this some sort of caching issue ? Any thoughts ?
Cheers,
PaulC.

User was unlocked yesterday and was still giving locked error this morning. It's now working. Just surprised that a new call of an adapter would continue to say locked when it wasn't. Can only think it's some for of caching but this is a pretty unsatisfactory answer. Makes me worry that it might happen again.

JCO_ERROR_FUNCTION_NOT_FOUND in RFC Adapter

Hi,
In XI 3.0 RWB Component monitoring, if we check the RFC Adapter we are getting forllowing error.
Sender Channel 'RFC_SMSINVOICE_SEND' for Party '', Service 'PRD' (Internal Name 'RfcServer[RFC_SMSINVOICE_SEND]')
Server data: {jco.server.gwhost=192.168.223.128, jco.server.progid=SMSINVOICE, jco.server.gwserv=sapgw00, jco.server.unicode=0}
Repository data: {jco.client.lang=EN, jco.client.snc_mode=0, jco.client.client=200, jco.client.passwd=*****, jco.webas.ignore_jdsr_error=1, jco.client.user=basis-ltitl*, jco.client.sysnr=00, jco.client.ashost=192.168.223.128}
Current pool size: 1, max pool size : 5
RFC_HISTORY
- Error: 2011-06-30 15:13:47 IST: com.sap.mw.jco.JCO$Exception: (123) JCO_ERROR_FUNCTION_NOT_FOUND: Server repository could not create function template for 'ZSD_INVOICE_SMS_FMASYNC1' caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts!
- Error: 2011-06-30 14:58:47 IST: com.sap.mw.jco.JCO$Exception: (123) JCO_ERROR_FUNCTION_NOT_FOUND: Server repository could not create function template for 'ZSD_INVOICE_SMS_FMASYNC1' caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts!
- Error: 2011-06-30 14:43:41 IST: com.sap.mw.jco.JCO$Exception: (123) JCO_ERROR_FUNCTION_NOT_FOUND: Server repository could not create function template for 'ZSD_INVOICE_SMS_FMASYNC1' caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts!
- Error: 2011-06-30 14:28:52 IST: com.sap.mw.jco.JCO$Exception: (123) JCO_ERROR_FUNCTION_NOT_FOUND: Server repository could not create function template for 'ZSD_INVOICE_SMS_FMASYNC1' caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts!
- Error: 2011-06-30 14:13:12 IST: com.sap.mw.jco.JCO$Exception: (123) JCO_ERROR_FUNCTION_NOT_FOUND: Server repository could not create function template for 'ZSD_INVOICE_SMS_FMASYNC1' caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts!
I'm not sure this is becuase of user 'basis-ltitl', becoz we have changed this used in sender communication channel and tried it. Eventhough it giving the same error.
Could you please help me out in resolving this issue.
Regards,
Baskaran K

Hi Mark,
When I click on 'Cache Status Overview' it says Adapter Framework not register in SLD.
In SLD, I could find 2 entries for all XI components, one is with old name (xiprd) and another entry with new name (mipxiprd). But the entry for the new name does not have the domian assigned. I have manaully assigned domain for new entry (Intetegration Directory on prx.mipxiprd) and made dummy change in communication channel. But the cache notification ended with red state in Cache status overview for adapter framework (af.prx.xiprd). But this is the old name of adapter framework.
I'm not sure why it picking the old name instead of new adapter framework name(af.prx.mipxiprd). Kindly not in SLD, both adapter frame work are present.
If I remove the the old one from SLD, none of the notification going to Adapter Framework.
Kindly help me out in solving the issue. From where the adapter framework URL will be picked up in Integration Directory.
Regards,
Baskaran K

Hi in my interface RFC adapter and XI adapter

Hi all,
in my interafce they are using XI adapter for data transfering for a BAPI in SCM sever , but i dont why ther using this adapter instead of RFC adapter , any one can tell me difference for this one
thanking you
sridhar

Hi,
You can configure the XI adapter to exchange messages with an Integration Engine. Both XI 3.0 and XI 2.0 message protocols are supported. You also use the XI adapter to exchange messages between SAP Exchange Infrastructure and the Partner Connectivity Kit (PCK).
You can use security settings to sign messages and check the signature. You can encrypt and decrypt message payloads.
The RFC adapter enables you to use the functions of the Integration Engine or the PCK in existing SAP landscapes. It is used by SAP systems to connect to the Integration Engine or the PCK by using the RFC interface. It supports SAP systems as of version 3.1x
See the below links to ref
http://help.sap.com/saphelp_nw04/helpdata/en/e1/091640a991c742e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/33/c6e63b60c25767e10000000a11402f/content.htm
Regards
Chilla..

Why is the RFC Adapter so unstable

Similar Messages

Maybe you are looking for