Error in RFC adapter

Hello All,
I am working on File to RFC Asynchronous Scenario. I am getting Error in M receiver RFC adapter. It is displaying in Adapter Monitoring as
- Error: 2007-10-03 05:28:38 EDT: Message processed for interface BAPI_CUSTOMER_CREATEFROMDATA1: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was
Can any help how to resolve this.
Regards

Hi,
The RfcAdapter trys to find a Sender Agreement for this RFC call but the lookup failes. The values used for this lookup are:
     Sender Party/Sender Service: The values from Party and Service belonging to the sender channel.
     Sender Interface: The name of the RFC function module.
     Sender Namespace: The fix RFC namespace urn:sap-com:document:sap:rfc:functions
     Receiver Party/Receiver Service: These fields are empty. This will match the wildcard '*'.
Chilla

Similar Messages

Error in RFC Adapter PI 7.10 maximum size of requests for one LUW

Hello all,
I have a big issue on our Development - SAP PI 7.10 System. If I try to push a RFC from a Client System
I get follow error messagei in the Runtime Workbench (RWB) back:
processing error to be caused by: com.sap.aii.adapter.rfc.core.server.RfcServerException: maximum size of requests for one LUW has been reached (1). handling of request for tRFC (TID: 0AA001B8712C49D35D4D06C2) not possible (server: RfcServer[PKG_R3_D07_600_RFC_SND]1)
But I don't know why. I checked follow OSS Notes:
730870 and 774705 w/o success. It will be nice somebody can help me.
Thanks
S. Kohler
P.S. We have the same scenario in our Quality SAP XI System and there works. I couldn't find any
differences between the Adapters. Is there a problem with the parameters ????

Hello Tarang Shah,
okay. Here again ( I thought I mentioned above):
in Q50 (SAP PI 7.10 System) we create a RFC Server with the program ID RFC_Q50.
in D64 (SAP PI 7.10 System) we vreate a RFC Server with the program ID RFC_D64
in D07 (SAP R/3 4.7 x110) we create a RFC Connection to D64 with the program ID RFC_D64.
The testconnection works well. I see in our Dev. SAP PI System (D64) that the connection works.
The problem is here, if you start in the application (System D07) the push, you get the error :
maximum size of requests for one LUW has been reac hed (1). handling of re
in Q50 (SAP R/3 4.7 x110) we create a RFC Connection to Q50 with the program ID RFC_Q50.
The testconnection in Q17 works well. Also the push from the application (System Q17.)
This means, the functionallity is okay on both sides (Q17 and D07) only the application sending
process from D07 makes trouble ( you see in Transaction SM 58 on Client Site, the error as I mentiond above and in SAP PI side.) It seems that SAP PI could't accept more as one LUWs
in the same time. Q50 (Q- System) accepted.
So, this is the reason in my point of view, that the problem isn't the connection, seems more
an paramter problem in D64 side. But I don't know which parameters. I checked the OSS Note 730870 and 774705 w/o success.
Thanks
S. Kohler

Error when RFC adapter calling the BAPI

Hi freinds
Today when I was executing my scenario ( File -- XI -- RFC ), I got following error ::
Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling Z_BAPI_POS_AUTOMATION in remote system (RfcClient[RFC_Connection_SAPR3_DEV]):com.sap.mw.jco.JCO$Exception:(104) RFC_ERROR_SYST
Before this error I executed my scenario 2-3 times without any errors.
I found that in RWB the message status was "Waiting". SO I checked the Component monitoring & found this error in Self Test Status ( the symbol was RED )-->
java.lang.ArrayIndexOutOfBoundException: -1 ( Not copied from the original error message )
I clicked the "Repeat Self Test" button & the status become green so I checked my message again. Now it was successfull but in 2 retries it was giving the JCO error & after the Self test ( 3rd retry) it went fine.
I didn't change anything else other than Self test.
This happened two times with me today. Can anyone tell me the reason behind this & what will be the permanent solution of
this. Is this related to some memory dumping ? Is their anything like clearing memory for adpaters in XI.
Best Regards
Lalit

Could you pls check whether a short dump occured in the target system.
Go to ST22 in the target system and check.
Thanks,
Renjith

Error from RFC adapter

Hi,
I encountered an error while sending RFC from ECC5.0 to XI using RFC sender communication channel and TRFC. The error in the TRFC monitor is
com.sap.aii.af.rfc.afcommunication.RfcAFWEx
: lookup of alternative
Does anyone have an idea what might be causing this?
thanks.
James Chang

Hi,
Is it solved?
If not just check with RFC Destinations(SM59- Tcode). Also check with Cache Refresh.
RFC Sender Error
https://websmp103.sap-ag.de/~sapdownload/011000358700002757652005E/HowtoMintorAF.pdf
Hope it helps,
Regards,
Moorthy

RFC adapter not started (Error starting AS Java Service XPI Adapter)

Dear Experts,
We have recently Upgraded our sustem from XI3.0 to PI 7.1, and have encountered a peculiar error in RFC adapter which could not be started
error says: Error starting AS Java Service XPI Adapter: RFC
corresponding instance when started says
Error starting AS Java Service XPI Adapter: RFC on DVEBMGS00
Hence our RFC channels are not functioning
Please help
Regards,
Rana De

can you try to restart XPI Adapter:RFC in NWA. if still it throws error then try to restart java stack.

Error while calling RFC adapter(FILE-XI-RFC scenario)

Hi,
I am trying for FILE-XI-RFC scenario. I am getting the following error. I have checked in message monitoring. The error is coming while calling the RFC adapter. Can any body tell what problem is this?
Regards,
Dhana
<?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="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.f23.sofd00001530a</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>2: Unable to find URL for Adapter Engine af.u7a.us4296</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine af.f23.sofd00001530a</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Hi,
I did SLD check.
The status says 'Summary: Connection to SLD works correctly'.
But it fails while checking the access to XI profile.
Here is the status
Summary: Connection to SLD works correctly
Now checking access to the XI Profile
Properties of RFC destination LCRSAPRFC
RFC host:
%%RFCSERVER%%
program id: LCRSAPRFC_DZ1
gateway host:
gateway service:
Testing the RFC connection to the SLD java client...
RFC ping returned exception with message:
/ CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679#Transaction program not registere

Error while doing commint from RFC Adapter

Hi,
We have a SOAP-PI-RFC synchronous scenario. Through this Soap request comes to PI and passed on to BAPI via RFC adapter. This BAPI saves the transaction & return the document number. We are using " PI PI parameter u201CCommit Handling for single BAPI' in RFC receiver Channel.
While this setup works for 1 posting, when we do the mass load ( Say 20 Documents) half of the documents are not able to Save. Although BAPI, returns the document number but on checking the document does not exists in SAP. To do further test, we created a program in ECC and try calling BAPI in loop and calling BAPI Commit.
This way program works fine and there is no error
So in nutshell, when we PI do the commit, half of the documents are not saving where as when the ABAP program commits no error. Is there any special way that PI calls this commit work.
PS: We created a wrapper BAPI which calls the orgirnal BAPI and Commit BAPI & called this from PI but still the same problem is coming.
Appreciate help on this.
Regards,
Harish

Are there any error messages in the RFC Reciever channel in Runtime Workbench?
RWB -> Component monitoing -> Adapter Engine -> Comm Channel -> filter for type RFC
Please try to give some more details on why the system says the messages are failing.

Error in Reciever RFC Adapter

Hi All,
While working with JDBCXIRFC, the only error with Reciever RFC Adapter is as
follows.
ZBAPICUSTOMER_DETAILS: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not get functionname from XML requst: com.sap.aii.af.rfc.RfcAdapterException: failed to read funtionname from XML document: missing namespace declaration(2)
In SXMB_MONI, the messages are queued up.
How to debug this error?
Regards
Pavan

1. Map all the mandatory fields..
I have mapped all the mandatory fields. If i enter same kind of values in the same fields of BAPI manually (in se37), the table gets updated.
how you can say that data is getting into the right tables...when you are sending the same data.....may be the data is old only..
Perform the Message Mapping and Interface Mapping test in IR only...
3. Kindly check the Sender_MM Mapping once more...If it is fine...reactivate and Update the cache..
Its fine and reactivated and even updated cache.
Now one doubt....
In Message mapping, the sender mesage type is as follows.
sender_mt 1:1
->Row element 1:unbounded
> zkunnr element xsd:string 1: unbounded
> zname1 element xsd:string 1: unbounded
> zstras element xsd:string 1: unbounded
> zadrnr element xsd:string 1: unbounded
> ztelf1 element xsd:string 1: unbounded
I have mapped ROW with ZBAPI_DETAILS.
the root of sender message type SENDER_MT is left as it is....
Is there anything need to be done (mapped) with this root of sender message type?
No i don't think so, what i can get from your approach is that you want to receive n similar type of records in a Message and want 2 create n different messages for each record from source structure.. 
With this status, i have tested the Test Configuration in Integration Directory. Still getting same error message as follows...
Kindly let me know the name of BAPI.
Perform the Message Mapping and Interface Mapping test in IR only...
java.lang.NullPointerException thrown during application mapping com/sap/xi/tf/_sender_mm_:
Regards,

Error in RFC Receiver adapter

Hi,
I am trying to send data into sap R/3 system from SAP XI 3.0 and I am using RFC adapter for this purpose. When I configured the receiver RFC adapter I am getting the following error in SXMB_MONI:
No receiver agreement found for sender ,FILESYS to receiver ,IDS47800,urn:sap-com:document:sap:rfc:functions,BAPI_MATERIAL_SAVEDATA
Please help us as we are stuck at this Juncture in a very important assignment.
Thanks and Regards,
Anil Kumar Damodara

Hi Anil,
1.Check whether the receiver agreement is properly configured with the "RFC_Receiver" communication channel.
2.Check whether the same Receiver agreement("RFC_Receiver" communication channel) is set in the receiver determination configuration.
check out my article "Validating a Connection Between SAP R/3 and SAP XI with RFC"
Regards,
Sridhar Rajan N

Sender RFC adapter Error- request was null while trying to extract it.

Hi All,
I have a scenario running in Production(PI 7.0 system) where SAP ECC sends RFC request through sender RFC adapter. The scenario was working fine but now I am getting the below error in default trace and I couldn't see any error in communication channel monitoring.
java.lang.Exception: RfcServer[BAS_ECC_RFC_Snd]1[AFSenderD] request was <null> while trying to extract it.
I have gone through the below thread and performed a full cache refresh but it didn't help :
[NULL]
I have gone through SAP note:730870 and I couldn't get any help on this error. Can you please suggest your ideas to solve this issue.
Thanks & Regards,
Laawanya

Hi Lawanya,
Check you RFC and input data , whether the RFC call is able to get the data from ECC or not.
you can test the same RFC in ECC with input data and you can check whether the RFC in ECC is return the value or not.
I gues in your case the RFC in ECC is not return any data to PI.

Error in RFC Sender Adapter

Hello Experts,
Right now i m working on the scenario SRM -> XI -> 3rd party system.
Here i want to send data from SRM to XI, and for that i m using Sender RFC Adapter.
I have configured RFC Sender channel in XI and created RFC Destination into the SRM system, and when i m trying to test the RFC Destination at that time it is giving me error saying that "program POACK_GEE not registered".
Can anyone help me out in this issue... its very urgent...
so waiting for your replies...
Thank you very much,
hetal

Hi Michal,
I already had a look into that... but i didnt find the solution
The error coming is like this....
ERROR program POACK_GEE not registered
LOCATION SAP-Gateway on host <host name> / <service name>
DETAIL TP POACK_GEE not registered
COMPONENT SAP-Gateway
COUNTER 1270
MODULE gwr3cpic.c
LINE 1609
RETURN CODE 679
SUBRC 0
RELEASE 640
TIME Mon May 7 16:45:48 2007
VERSION 2
I have followed all the steps then also i dont know y it is not working...

Errors in RFC sender Adapter

Hi Guys,
I am configuring a RFC sender Adapter in a newly installed system.
I configured the adapter as per the parematers given in SAP help in the exact way and started getting the error
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, direction INBOUND, fromParty '*', fromService 'RD1CLNT020', toParty '', toService '', interface 'Z_TEST', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'RD1CLNT020_IN' (channelId 897afca12ee93b86a5bfcd738c037099)
If I go into SXI_CACHE of the PI system I can see the entry.
My gut feeling is that the adapter is not fetching the metadata properely.
Because I switched the metadata loging from the ECC system to PI system and I got the error
JCO.Server could not find server function 'Z_TEST'
I think in the basis setup we have missed something The version on which we are working is the Latest PI 7.1
If somebody has a document at the the config for JCO or a solution for this problem will be much appreciated.
Thanks & Regards
Gagan Kasana

Hi,
there is no magic with this error - it's a common one
1. my blog - RFC sedenr adapter config -
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
then is still does not work:
2.check out OSS note 730870 - FAQ RFC Adapter
"Question 19:
While sending a RFC call to the RFC Adapter I get a error message like "com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of binding via CPA-cache failed..." or "com.sap.aii.af.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed...". What is missing?"
and you have it working
please let me know if this helped
Regards,
Michal Krawczyk

Receiver RFC Adapter Error

Hi All,
I have a file to RFC scenario. I keep getting the below error: Any Ideas?
Danny,
Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.af.rfc.util.bapi.BapiException: Parameter with name RETURN not found.: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.af.rfc.util.bapi.BapiException: Parameter with name RETURN not found..

is this BAPI an SYNC one
check this link
RFC adapter Call BAPI error
Re: Invoice Not getting posted

Calling RFC Adapter fails - convert error

Hi,
I have a problem with calling RFC Adapter. I'm using JDBC->XI->RFC scenario. JDBC does just "select 'W' from dual". In the destination SAP system RFC function is created for test purposes. This function has one parameter - string type. After calling it, it should write a sysdate into the SAP Z_ table. The XI should call the function with the 'W' parameter. But this fails. Everything is ok, but calling the RFC returns following error (copied from the Runtime Workbench -> Message Monitoring :
Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not convert request from XML to RFC:com.sap.mw.jco.JCO$Exception: (130) JCO_ERROR_XML_PARSER: Expecting a tag to begin with '<' instead of 'W', in "u
(Yes, this is thw whole error message. I don't know what u should be...)
Did someone get this error?
Thanx 4 answers, Peter

Hello all,
Let me reopen the topic of my colleague. I'm facing the same error though with bit different symptoms. Here it is.
ERROR msg:
Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not convert request from XML to RFC:com.sap.mw.jco.JCO$Exception: (130) JCO_ERROR_XML_PARSER: Expecting a tag to begin with '<' instead of 'Z', in "T
The XML message (MainDocument):
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:Z_BAPI_ACCESSIBILITY_TEST_XI xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
<BAPI1008 />
<PARAM>Z_XID_500_ACC</PARAM>
<ZTTOTH_BAPI1008 />
- <ZTTOTH_STRUCT>
<PARAM1>Z_XID_500_ACC</PARAM1>
</ZTTOTH_STRUCT>
</ns0:Z_BAPI_ACCESSIBILITY_TEST_XI>
According to the error message the parser expects behind string ...<ZTTOTH_STRUCT><PARAM1> another tag, but the question is why.
To make all this more funny here I paste another XML message of BAPI calling which works fine (without the error described above):
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:Z_BAPI_PARAMETERS_TEST_XI xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
<PARAM>Z_XID_500</PARAM>
- <ZTTOTH_STRUCT>
<PARAM1>Z_XID_500</PARAM1>
</ZTTOTH_STRUCT>
</ns0:Z_BAPI_PARAMETERS_TEST_XI>
The BAPI functions are absolutely the same except those other two import-pramater structures (BAPI1008 and ZTTOTH_BAPI1008). I'm gonna to try to add those import-parameter structures into Z_BAPI_PARAMETERS_TEST_XI, but anyway - this is weird.
Does anybody have an idea, what should be wrong ?
Thx. Tom
Message was edited by: Tomas Toth

Error in pushing a request to R3 System using RFC Adapter

I am trying to send a request to R3 system using an RFC Adapter as my end point and pointing to
the Application server of the R3 box.
In the Transaction SM58 I see and error saying "Exception in handleRequest of server Xmb2RfcService: java.lang.Exception:"
Here are the corresponding details:
Caller: CENTRALADMIN
Function Module: SRFC_ADAPTER_SERVICE
Target System: AI_RFCADAPTER_JCOSERVER
Host: .... (The XI Server)
Program: SAPMSSY1
Clnt: 100
As per the SRFC_ADAPTER_SERVICE function module, the purpose stated so...
"This function is the glue between the JCo RFC Inbound Adapter and the XMS Pipeline."
By the by the RFC adapter is started and I can see no activity in the log after startup.
I would really appreciate for any idea/leads in solving this. Thanks.

Here are the details
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%Config File for RFC Adapter%%%%%%%%%%%%%%%%%%%%
RFC ADAPTER CLASSNAME FOR ADAPTER ENGINE
classname=com.sap.aii.rfcadapter.core.RfcAdapterModule
RFC ADAPTER CONFIGURATION PROPERTIES
Tue Jan 21 13:27:43 CET 2003
1. GENERAL SECTION
1.1 trace settings
RfcAdapter.trace=2
-> adapter trace level 0 = none
 1 = error
 2 = standard
 3 = request
 4 = payload
 5 = binary payload outbound
#RfcAdapter.traceStack=0
#RfcAdapter.listenException=0
#RfcAdapter.listenState=0
-> additional trace switches (in general not needed)
RfcAdapter.traceFile=./LogFiles/Adapter_rfc.log
-> name of trace file (traces to stdout if not specified)
 NOTE: in a productive environment, the trace file should be written to the
 log-file directory of the Adapter Engine
1.2 connectivity settings
RfcAdapter.registerInbound=sourceBackendXD1
-> space-delimited list of logical names for inbound R/3 systems subsections.
 The adapter will register with all R/3 systems defined in this list and
 those systems can send RFC requests into the XI via an RFC destination
 that has to be setup in SM59 to point to the RFC Adapter
RfcAdapter.accessInbound=toXmb
-> logical name for inbound access to XMB subsection
RfcAdapter.registerOutbound=fromXmb
-> logical name for outbound access from XMB subsection
RfcAdapter.accessOutbound=targetBackend
-> space-delimited list of logical names for pre-allocated outbound R/3 systems subsections.
 This is an option to speed up connection setup during request processing. The RFC Adapter
 preallocates sessions to all listed R/3 systems.
RfcAdapter.clientCloseConn=1
-> close calling connections after call (1) or just reset session (0)
 NOTE: the reset mechanism is slightly faster for request processing. However, it does
 not re-connect after a target system shutdown and hence requires a restart of the
 RFC Adapter in such a situation.
#RfcAdapter.maxDynPools=128
-> maximum number of dynamically allocated client pools to access outbound R/3 systems
#RfcAdapter.minDynPoolSize=4
-> initial number of clients in dynamically allocated client pools
#RfcAdapter.incDynPoolSize=4
-> increment number of clients in dynamically allocated client pools
#RfcAdapter.maxDynPoolSize=64
-> maximum number of clients in dynamically allocated client pools
2. SUBSECTION FOR REGISTRATION TO CLIENT APPLICATION SYSTEMS
(one subsection per incoming R/3 system; requires callback service user for repository access)
RfcAdapter.sourceBackendXD1.host=db03
RfcAdapter.sourceBackendXD1.sysnr=00
RfcAdapter.sourceBackendXD1.progid=Rfc2XmbService
-> recommended is: RfcAdapter.sourceBackend.progid=Rfc2XmbService
RfcAdapter.sourceBackendXD1.poolsize=5
RfcAdapter.sourceBackendXD1.unicode=1
-> source system is Unicode installation (1) or not (0)
RfcAdapter.sourceBackendXD1.client=500
RfcAdapter.sourceBackendXD1.user=XIAPPLUSER
RfcAdapter.sourceBackendXD1.passwd=********
RfcAdapter.sourceBackendXD1.lang=EN
RfcAdapter.sourceBackendXD1.trace=2
-> enable RFC trace for this connection (1) or not (0)
#RfcAdapter.sourceBackendXD1.sncName=<SNC_name_of_adapter>
-> e.g. RfcAdapter.sourceBackendXD1.sncName=p:CN=USERNAME, O=ORGNAME, C=DE
#RfcAdapter.sourceBackendXD1.sncLib=<SNC_library_path>
-> e.g. on Win2K: RfcAdapter.sourceBackendXD1.sncLib=C:
Program Files
SECUDE
SECUDE for R3
secude.dll
#RfcAdapter.sourceBackendXD1.sncQop=<SNC_quality_of_protection>
-> 1,2,3,8,9 e.g. RfcAdapter.sourceBackendXD1.sncQop=1
#RfcAdapter.sourceBackendXD1.sncAcl=<SNC_access_control_list>
-> logical names for allowed callers e.g. RfcAdapter.sourceBackend.sncAcl=peerB6A peerB6Q
#RfcAdapter.sourceBackendXD1.sncAcl.peerB6A=p:CN=B6A, O=SAP-AG, C=DE
#RfcAdapter.sourceBackendXD1.sncAcl.peerB6Q=p:CN=B6Q, O=SAP-AG, C=DE
-> details for peer ACL lists
3. SUBSECTION FOR ACCESS TO XMB INBOUND RFC SERVICE
(only one entry possible)
RfcAdapter.toXmb.host=web03
RfcAdapter.toXmb.sysnr=00
RfcAdapter.toXmb.poolsize=5
RfcAdapter.toXmb.client=100
RfcAdapter.toXmb.user=XIAPPLUSER
RfcAdapter.toXmb.passwd=******
RfcAdapter.toXmb.lang=EN
RfcAdapter.toXmb.trace=2
4. SUBSECTION FOR REGISTRATION OF XMB OUTBOUND RFC SERVICE
(only one entry possible)
RfcAdapter.fromXmb.host=web03
RfcAdapter.fromXmb.sysnr=00
RfcAdapter.fromXmb.progid=Xmb2RfcService
this value must be in sync with Program Id setting for AI_RFCADAPTER_JCOSERVER in SM59
RfcAdapter.fromXmb.poolsize=5
RfcAdapter.fromXmb.unicode=1
-> source system is Unicode installation (1) or not (0)
RfcAdapter.fromXmb.trace=2
5. SUBSECTION FOR ACCESS TO SERVER APPLICATION SYSTEMS
(one subsection per outgoing R/3 system; pre-allocated connection pools via service user)
RfcAdapter.targetBackend.host=db03
RfcAdapter.targetBackend.sysnr=00
RfcAdapter.targetBackend.poolsize=5
RfcAdapter.targetBackend.client=500
RfcAdapter.targetBackend.user=XIAPPLUSER
RfcAdapter.targetBackend.passwd=*******
RfcAdapter.targetBackend.lang=EN
RfcAdapter.targetBackend.trace=2
END OF RFC ADAPTER CONFIGURATION PROPERTIES
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%Log data for the adapter%%%%%%%%%%%%%%%%%%%%%%%%%%
Fri Sep 24 09:50:09 EDT 2004 *****
09:50:09 (6011): RFC adapter initialized
09:50:09 (6031): RFC adapter started
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%SM59 entries on the XI box%%%%%%%%%%%%%%%%%%%%%%%%%%
Name: AI_RFCADAPTER_JCOSERVER
Program ID: Xmb2RfcService
Action Type: Registered Server Program
Gateway: web03 (Local XI box)
Gateway Service: sapgw00 (00 is the system number)
Name: XI_SERVER
Program ID: Rfc2XmbService
Action Type: Registered Server Program
Gateway: db03 (R3 box)
Gateway Service: sapgw00 (00 is the system number for R3)
Both the entries are tested fine.

Error in RFC adapter

Similar Messages

Maybe you are looking for