RFC adapter receive queue performance

We currently using XI 3.0 on NetWeaver 6.40 with a lot of asynchronous interfaces from JDBC <-> RFC.
After some load we experience that message received in RFC adapter queue are processed after a long time. The messages has status "To Be Delivered" and XI is processing other messages the same time.
2010-01-07 15:25:28 Success Message successfully received by messaging system. Profile: XI URL: http://mlrxiprod:50000/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
2010-01-07 15:25:28 Success Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2010-01-07 15:25:28 Success Message successfully put into the queue.
after 1 1/2 hour ...
2010-01-07 17:01:10 Success The message was successfully retrieved from the receive queue.
2010-01-07 17:01:10 Success The message status set to DLNG.
2010-01-07 17:01:10 Success Delivering to channel: NAV_FICANCEL_RFC_RECEIVER
2010-01-07 17:01:10 Success RFC adapter received an asynchronous message. Attempting to send tRFC for ZXI_FI_CANCEL_WRAP with TID XIps}UGFk94TwD}G0O}ZGR2m
2010-01-07 17:02:32 Success The message was successfully delivered to the application using connection RFC_http://sap.com/xi/XI/System.
2010-01-07 17:02:32 Success The message status set to DLVD.
Can you explain why it takes so long the message to picked up and processed from the queue. All messages will be processed but the performance is unacceptable. No errors are found in SMQ2.

Hi,
It looks like msgs take very long time to be picked up from the queue(s) ! Is there enough threads allocated (according to SAP recommendations, which I can't remember) ?
How many system & application threads have been allocated ?
Rgds
Chris

Similar Messages

Soap Sender and RFC Adapter receiver getting APPLICATION_ERROR

Hi, all,
I have a webservice soap sender and RFC Adapter receiver scenario, it works fine with RFC "RFC_SYSTEM_INFO", When i tried the RFC "RFC_READ_TABLE", getting the following error message, <SAP:Code area="RFC_ADAPTER">APPLICATION_ERROR</SAP:Code> in
SXI_MONITOR, in webservice client, i am getting error message like this:
<faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <rfc:ZZTEST_RFC_READ_TABLE.Exception xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
 <Name>TABLE_NOT_AVAILABLE</Name>
 <Text>QUERY_TABLE not active in Dictionary</Text>
 </rfc:ZZTEST_RFC_READ_TABLE.Exception>
Thanks a lot!

Hi
Its not compulsory but its good to wrap it as Z object.
Well if you are facing problem with SOAP data. Then try to do one thing. Check with the data you received from SOAP message. If this works
Then try to check in mapping is it passing the data correctly or not. With this check with the user authorization PIAPPLUSER. if its having less authorizations to execute this BAPI in ECC
Thanks
Gaurav

RFC Adapter Receiver - change SAP User for each call

Hi guys,
I need to create one connection between PI and SAP, all right, i can use RFC Adapter Receiver, no problem.
But, for each call i need to use User and Password different, then, I would pass SAP User and Password in my XML Payload.
Can anybody help me, please?

hi,
>>But, for each call i need to use User and Password different, then, I would pass SAP User and Password in my XML Payload.
sure we can help you but no in this way:)
it is possible to change the user for RFC adapter but using
principal propagation:
/people/alexander.bundschuh/blog/2007/01/16/principal-propagation-in-sap-xi
this is the way you need to go and not send password in XML payload
(this is certainly not the way and no client will approve it)
why use a password is anyone can see it ?
Regards,
Michal Krawczyk

RFC Adapter Receiver Error

Hi Guys,
I am getting below error in RFC Receiver Adapter Level Error. is showing as Adapter Level Status as "WAITING" , with below error.
Can any one pls help me on this. if i resend the message from RWB will it works...?
Warning Adding message to blacklist. Reason: message, which is in delivering state, is reassigned.
Warning Message added to blacklist
*MP: exception caught with cause
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: Out of memory error occurred while processing message at RFC receiver*
Error Adapter Framework caught exception: Out of memory error occurred while processing message at RFC receiver
Error Delivering the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: Out of memory error occurred while processing message at RFC receiver.
Thanks,
Siva.

Hi Naveen,
How i will increae heap memory ? can u pls expalin me step by step..
Earlier the above message error shwing as "WAITING" sattus with above error..its posted duplicate message ( multiple messages 2 times) in target system..
actually this meesge "WAITING" ststus in Runtime workbench - Adapter Engine on 1st march 2012, but its posted on same day and next day 2nd march 2012 on 4PM PST ( That means 5-30 AM IST ).
This is File 2 Rfc Interface..
Can any one pls expalin me why it posted double times..? any clue..? pls help me on this...
Regards,
Siva.
Edited by: siva38 on Mar 7, 2012 2:27 PM
Edited by: siva38 on Mar 7, 2012 2:49 PM

HTTP Response code 404 - RFC Adapter des not connect to Integration engine

Hi,
I seem to have problem with XI Integration engine. My integration process does not go beyond adapter engine and it fails with the following error,
Begining of the erorr report -
2006-01-23 13:35:53 Success RFC adapter received sRFC for ZSCEN2_XI from <sysno>/<client>. Attempting to send message synchronously
2006-01-23 13:35:54 Success Application attempting to send an XI message synchronously using connection AFW.
2006-01-23 13:35:55 Success Trying to put the message into the call queue.
2006-01-23 13:35:55 Success Message successfully put into the queue.
2006-01-23 13:35:55 Success The message was successfully retrieved from the call queue.
2006-01-23 13:35:55 Success The message status set to DLNG.
2006-01-23 13:35:55 Error Returning synchronous error notification to calling application: Received HTTP response code 404 : Not Found.
2006-01-23 13:35:55 Error Transmitting the message using connection http://<host>:55300/sap/xi/engine?type=entry failed, due to: Received HTTP response code 404 : Not Found.
2006-01-23 13:35:55 Error The message status set to FAIL.
2006-01-23 13:35:55 Error Returning to application. Exception: Received HTTP response code 404 : Not Found
end of error report -
and the runtime workbench does not connect to Integration engine and fails with the following error,
begin error report -
javax.ejb.CreateException: Unable to log on to system XID in language en with user XIRWBUSER
 at com.sap.aii.mdt.server.integrationengine.IntegrationEngineMonitoringBean.ejbCreate(IntegrationEngineMonitoringBean.java:374)
 at com.sap.aii.mdt.server.IntegrationEngineHomeImpl10.create(IntegrationEngineHomeImpl10.java:185)
 at com.sap.aii.mdt.server.IntegrationEngineHome_Stub.create(IntegrationEngineHome_Stub.java:56)
end of report -
Have anyone experienced the same issue?. Are we missing some post installation configuration?.
Thanks in advance
Regards,
Arul

HI Anulraja,
Your Adapter Engine searches the pipeline url of the integration engine from the SLD.
Check the Bussiness System in Sld , which you'll have defined for XI Server.
It should have ROLE : Integration Server And
pipeline url: http://ux0800:55300/sap/xi/engine?type=entry
should be this if your http port is 55300.
Check if this url is right in SLD-Bussiness System.
You can check the exact http port in transaction sxmb_adm.
Go to Integration engine configuration and then click on check icon(F7).
It should match with that provided in the BS in SLD.
By default it should be 8000.
Check all these things and then try.
Regards,
Yomesh

RFC to XML-RFC Parsing issue in RFC Adapter as Sender

Hi all,
I tried to use RFC adapter as a sender. The scenario I am trying to achieve is R3 -> RFC Adapter Sender --> BPM --> RFC Adapter Receiver --> SAP Auto-ID system.
The reason to use two RFC adapter and BPM is to log the request message if the RFC call fails. Everything works as expected, except the RFC Adapter Sender.
The RFC I am calling has an input table. The input data I use works fine if I call it via SE37 or remotely from another SAP system. However, if I call it via RFC adapter, when XI parses the data into RFC-XML format, the input data is all messed up.
DATA: BEGIN OF ID_STR,
 ID_VERSION(8) TYPE C,
 ID(96) TYPE C,
 ELEMENT_NAME(50) TYPE C,
 ELEMENT_VALUE(128) TYPE C,
 END OF ID_STR.
DATA: it_id LIKE TABLE OF ID_STR,
 ls_id LIKE ID_STR.
ls_id-ID_VERSION = 'EPC_1.30'.
ls_id-ID = '30340242206DC3C00000000A'.
ls_id-element_name = 'BATCH_ID'.
ls_id-element_value = 'BATCH001'.
APPEND ls_id TO it_id.
CALL FUNCTION '/AIN/UI_MOBILE_MSG_SEND'
IN BACKGROUND TASK
DESTINATION 'RFC_UPDATEAII'
EXPORTING
 IV_BUSINESS_PROCESS = '09'
 IV_COMMAND = 'DO'
 IV_ACTION_TYPE = 'APL2'
 IV_PRT_ID = '31140242200000000F000000'
 IV_DEVGRP_EXTID = 'MOBILE'
TABLES
 IT_ID = it_id
commit work.
And the parsed RFC-XML message is:
<?xml version="1.0" encoding="UTF-8" ?>
<rfc:_-AIN_-UI_MOBILE_MSG_SEND
xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
<IV_ACTION_TYPE>APL2</IV_ACTION_TYPE>
<IV_BTD_EXTID />
<IV_BTD_TYPE />
<IV_BUSINESS_PROCESS>09</IV_BUSINESS_PROCESS>
<IV_COMMAND>DO</IV_COMMAND>
<IV_DEVGRP_EXTID>MOBILE</IV_DEVGRP_EXTID>
<IV_LOC_EXTID />
<IV_LOC_TYPE />
<IV_PRT_ID>31140242200000000F000000</IV_PRT_ID>
<IV_PRT_ID_VERSION />
<IV_REASON_CODE />
<IV_UNAME/>
<ET_RETURN />
<IT_ID>
<item>
<ID_VERSION>EPC_1.30</ID_VERSION>
<ID>206DC3C00000000A BATCH_ID</ID>
<ELEMENT_NAME />
<ELEMENT_VALUE />
</item>
</IT_ID>
</rfc:_-AIN_-UI_MOBILE_MSG_SEND>
You can see the data in the table is all wrong, it should be:
<IT_ID>
<item>
<ID_VERSION>EPC_1.30</ID_VERSION>
<ID>30340242206DC3C00000000A</ID>
<ELEMENT_NAME>BATCH_ID</ELEMENT_NAME>
<ELEMENT_VALUE>BATCH001</ELEMENT_VALUE>
</item>
</IT_ID>
The calling system is a 4.6C non-unicode system, and the destination system is a unicode system (this does not matter since the first part of the integration is between R3 and XI). There is no config found on R3 side to specify non-unicode because it is a rather old system. In XI RFC Adapter config, I checked non-unicode checkbox (I also tested it with this unchecked, but still the same issue).
Have any of you seen this problem and how you resolve it?
Thanks a lot for your help!
Regards,
Hart

Hi Hart
long time no seen - hope you remember me
>The reason to use two RFC adapter and BPM is to log the request message if the RFC call fails
there is an easy way (guess max 3-4 hours) to solve all of your issues
and get rid of a BPM
use IDOC - XI - ABAP Proxy
then you will have IDOC and ABAP Proxy that always log the message on both ends (and you can restart ABAP proxies easily in AII - and every AII supports ABAP proxies) + you get rid of a BPM as it's not necessary as far as I understand (as it's asyn communication right?)
maybe you can go this way and IDOCs always work...
good luck,
Regards,
Michal Krawczyk
http://mypigenie.com XI/PI FAQ

Sender RFC Adapter - Data to be sent from R/3

I am working on a scenario where I have to send data from an RFC-enabled function module from R/3 to a file server via XI. The entire scenario is asynchronous.
Sender: RFC Adapter
Receiver: File Adapter
I have done all design and the configuration. Both communication channels are working. I have the RFC destination also set up correctly in R/3.
However, when I run my ABAP program where the RFC-enabled function module is called, I get a shortdump with the message "senderAgreement not found: lookup of binding via CPA-cache failed for".
Plus: " The error occurred during an RFC call to another system."
Could someone kidly help?

Hi,
Follow these steps :
1. import the ECC_ Server into ID if not done
2. Refresh Cache : Tcode SXI_CACHE
3. Please check for Sender agreement config
4. Check out the parameters when R/3 calls back XI, it passes the SYS-ID and client number and checks the same in the Integration Configuration Under Business System Service-> Adapter Specific Identifiers. The R/3 System ID and the client Number
Also check out these blogs..
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
regards
Aashish Sinha
PS : Reward points if helpful

RFC-Adapter, order not put in

Hi,
my scenario File -> XI -> R/3-Backend will be precessed successful. The Response Payload have the items and in detail of messages appears succes status
"RFC adapter received an asynchronous message. Attempting to send tRFC for BAPI_PO_CREATE with TID XIfr1OyAQS4Td..."
But in R/3 the order ísn't put on.
Does one of you have an idea why???????
Thanks
Hüsniye

Try this code. This works perfectly for us:
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
EXPORTING
 SALESDOCUMENTIN = SALESDOCUMENTIN
 ORDER_HEADER_IN = ORDER_HEADER_IN
 ORDER_HEADER_INX = ORDER_HEADER_INX
 SENDER = SENDER
 BINARY_RELATIONSHIPTYPE = BINARY_RELATIONSHIPTYPE
 INT_NUMBER_ASSIGNMENT = INT_NUMBER_ASSIGNMENT
 BEHAVE_WHEN_ERROR = BEHAVE_WHEN_ERROR
 LOGIC_SWITCH = LOGIC_SWITCH
 TESTRUN = TESTRUN
 CONVERT = CONVERT
IMPORTING
 SALESDOCUMENT = SALESDOCUMENT
TABLES
 RETURN = RETURN
 ORDER_ITEMS_IN = ORDER_ITEMS_IN
 ORDER_ITEMS_INX = ORDER_ITEMS_INX
 ORDER_PARTNERS = ORDER_PARTNERS
 ORDER_SCHEDULES_IN = ORDER_SCHEDULES_IN
 ORDER_SCHEDULES_INX = ORDER_SCHEDULES_INX
 ORDER_CONDITIONS_IN = ORDER_CONDITIONS_IN
 ORDER_CONDITIONS_INX = ORDER_CONDITIONS_INX
 ORDER_CFGS_REF = ORDER_CFGS_REF
 ORDER_CFGS_INST = ORDER_CFGS_INST
 ORDER_CFGS_PART_OF = ORDER_CFGS_PART_OF
 ORDER_CFGS_VALUE = ORDER_CFGS_VALUE
 ORDER_CFGS_BLOB = ORDER_CFGS_BLOB
 ORDER_CFGS_VK = ORDER_CFGS_VK
 ORDER_CFGS_REFINST = ORDER_CFGS_REFINST
 ORDER_CCARD = ORDER_CCARD
 ORDER_TEXT = ORDER_TEXT
 ORDER_KEYS = ORDER_KEYS
 EXTENSIONIN = EXTENSIONIN
 PARTNERADDRESSES = PARTNERADDRESSES
**checking if the BAPI returned some errors*****
LOOP AT return ASSIGNING <bapiret>.
 IF <bapiret>-type = 'E' OR <bapiret>-type = 'A'.
 success = space.
 EXIT.
 ENDIF.
ENDLOOP.
IF success = 'X'.
****in case of success commit the BAPI*********
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 wait = 'X'
 IMPORTING
 return = wa_bapiret.
ELSE.
 ROLLBACK WORK.
 ENDIF.
Also you need to pass on the information for "inx" structures. What I mean is , if you are sending data to field REF_1 in header_in, then ref_1 in header_inx needs to be passed witha value of 'X'.
The update flag in inx structure needs to be 'C' for create.
If have items in your sales order, then you have to pass the values for item_in and item_inx. Additionally you need to pass values for schedule lines also.
Hope this helps.
Thanks,
Bhaskar

Receiver RFC adapter issue! Please help!

Hi Experts,
I have 4 XI interfaces. All of these are Webservice to RFC scenarios. Moreover all of them are synchronous.
Request message: Webservice (SOAP Adapter) ---> XI -
> RFc Adapter ---> ECC Function modules
Response message: Webservice (SOAP Adapter) <- XI < RFc Adapter <- ECC Function modules
As you can see above, external system calls XI web service via SOAP Adapter. The input data is then sent from SOAP Adapter to RFC adapter to call RFC function module in the receiving side. The receiving system is SAP ECC system.
The receiver ECC system has two instances. For example SP0 ad SP1.
In the receiver determination step we have maintained a rule such that if the Plant value in the input message is XYZ then send data to SP0. But if the plant value in ABC then send data to SP1.
This Conditional rule is working fine.
However we are getting couple of issues with only one instance of ECC (SP0).
1. com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message badfa070-b163-11de-a4c1-001cc495e48a(INBOUND) expired
2. NO_MAPPINGPROGRAM_FOUND. Mapping program is not available in runtime cache: Object ID C2B41FFDFD4635BAB1E41AE53C0D10CE Software Component 5394F420463611DAC1CFFBBC0A01BC16
3. com.sap.engine.interfaces.messaging.api.exception.MessagingException: No response available
The above listed errors are generated occasionally. Sometimes no errors are generated even when the same input data is sent again and message is successfully processed.
I have verified the input data and everything is OK with that.
Mapping object is available in XI and cache was also refreshed. I additionally reactivated the objects in XI as well.
So what could be the real root cause of this? Please help!
Thanks
Gopal

1. com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message badfa070-b163-11de-a4c1-
001cc495e48a(INBOUND) expired
Check the Timeout parameter of your adapter.....for requests which expire with this error confirm from the SAP end that the message processing is done well within the Timeout period of the adapter.
Refer this note for more info on the above occuring error and the possible way to avoid it: https://service.sap.com/sap/support/notes/791379
Update:
Even problem 3 seems to be occuring due to insufficient Timeout specified for the adapter.....if possible try increasing the Timeout in VA
Regards,
Abhishek.
Edited by: abhishek salvi on Oct 6, 2009 1:42 PM

Sender RFC Adapter-- XI-- File Receiver Adapter ?

Dear Expert,
we are on PI 7.0 & R/3 system 4.7E WAS < 6.20. We have a scenario where in there are some huge downloads are required from R/3 to FTP File Location. For such scenarios Normally Poxy is suggested but Due to WAs Version limitation we cannot use Proxy. The other alternative is to use SENDER RFc adapter using RFC destination with XI. we have configured the RFC destination it is working fine.
I am able to receive the message also in XI. But whenever i am running this RFC in R/3 it is giving me the shot dump as follows. :
call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:
The File is also getting written to the destination properly. But in XI also i get the following error.
 <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>http://Test/Zbilldwd ZBILLDWD_FILE_IM</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Interface mapping http://Test/Zbilldwd ZBILLDWD_FILE_IM does not exist in runtime cache</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
What could be the reason of this.? As well i am geting 3 error messages in XI.
I have defined this interface as Inbound / Async Message interface with input message as output file structure. ( Is this configuration is OKAY ?)
pl. help me to solve this error.
Regards,
Umesh

HI,
Check your configuration from the message it states that it can not find out the mapping program.
Check the configuration Receiver and interface determination whether you are using the same which is designed in repository.
Thanks and Regards,
Chirag Gohil

How to enable viewing of payload for receiver RFC adapter in RWB

HI All,
We can see the payload of all adapters in RWB by clicking on the message link under component >> adapter monitoirng. However when i click on message link for receiver RFC adapter, it does not show any payload. How can I enable this payload?
Regards

Hey
Sync messages are Cached rather than persisted in RWB to save memory.
You need to change the following parameter in Visual admin to see sync messages in RWB
Service SAP XI AF Messaging:
messaging.syncMessageRemover.removeBody = false
its set to True by default hence it does not stores the messages.
You may have to restart the Java stack after the changes (but first try without restarting the Java stack).
Thanks
Aamir
Pl:You will see the sync messages in Message Monitoring in RWB (not sure if it will show up in Communication channel monitoring as well)

SOAP - XI - RFC. XI not perform Adapter call after Technical Routing.

Hi, All!
I have a problem with XI.
My configuration (all calls are synchronous):
SOAP adapter -> XI mapping -> RFC adapter call to R/3
Most of the time it's works correctlly!
But some times XI does not call outbound RFC adapter after "Technical Routing". And there is no error in XI Monitor, but this XML message marked like "scheduled". So the SOAP adapter returns "Timeout error".
I have compared messages in XI monitor for a successful call and a unsuccessful one. There is no difference in "Routings" and "Mapings" they are the same, except for in the unsuccessful message no "Adapter call" at all!
Do you know how to solve such a problem?
Thank you!!

try to register all queues in SXMB_ADM -> Manage queues.
I think that should help you solve the issue.

Receiver RFC Adapter

Hi All,
I am getting this error in communication channel monitoring for receiver RFC Adapter.
Delivering the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling Z_CRM_LEAD_CREATEMULTI in remote system (RfcClient[S10440_RFC_CallOutComes_Out]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Illegal move of the field symbol of a LOOP ... ASSIGNING.
Have gone through lots of links on SDN but not able to solve it out.
Any inputs will be greatly appreciated.
Thanks,
Venkat

Hi,
this one seems pretty simple
>>illegal move of the field symbol of a LOOP ... ASSIGNING.
this suggests that your error is inside FM Z_CRM_LEAD_CREATEMULTI
so correct the code (probably the table you try to loop is empty)
and try once more
Regards,
Michal Krawczyk
http://mypigenie.com XI/PI FAQ

Configuring receiver RFC adapter to use RFC destination

Hello,
   I have been doing some digging, but I can't find a solid answer on how to configuring a receiver RFC adapter to use an existing RFC destination to call a 4/6C R/3 backend system... Our scenario is to WS --> SOAP --> RFC which is up and running in production just fine on NW 7.0, SP12.
   I ask this question because we, as a company, do not like to maintain passwords in multiple systems. That is necessary when we use the receiver RFC adapter now since SNC is a distant pipe dream for us and we would like to use an existing RFC destination that is set up to call the backend system using a logon ticket.
   I checked the relevant links I could find below, but I can not resolve the answer from them. Has anyone set this up successfully? This link (RFC Destination type RFC Receiver Adapter?) mentions it briefly, but it does not go into any length on how to set it up.
Thanks!
John
http://help.sap.com/saphelp_srm40/helpdata/fr/33/c6e63b60c25767e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/33/c6e63b60c25767e10000000a11402f/content.htm
Re: Asynchronous RFC call

Hi John !!
I suggest you to create a new user, without dialog access in your ECC system to be used exclusively by the XI system to access ECC. And then, always use this user in all RFC receiver adapter communication channels.
Regards,
Matias.

Error RFC Adapter (as receiver)

Dear All,
My scenario is: File --> XI --> RFC.
I used RFC adapter as a receiver.
I got checkered flag in SXMB_MONI, but i got following error in adapter monitoring:
"com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling /POSDW/CREATE_TRANSACTIONS_EXT in remote system (RfcClient[RFC_Receiver_Adapter]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Error determining transaction category for code 1503"
Please advise on what to do/to check. Thanks.
Best Regards,
Victor.

Hi Sarvesh,
That note is seems apply to my case.
I will ask my basis team to implement it and see whether it will fix my problem.
I will update this thread again once it has been implemented.
Thanks,
Victor.

RFC adapter receive queue performance

Similar Messages

Maybe you are looking for