An RFC adapter question

Hi all,
I have a doubt with the RFC adapter.
Currently I have this interface for an RFC:
R/3 system A -- XI system B -- R/3 system C
In this interface in system A I call an RFC through XI system B to get data of system C. The XI system B is the SLD associated to system A. This interface works fine.
Now the system B have another XI system, the system D. And I need change the XI system in this interface. What I need to do?
It is only needed create the interface in system D with the same RFC adapter configuration, with the same vales of gateway, program ID, etc... Or do I need additional configuration? SLD in system D? config system A?
I need to be sure of what I need because I need prepare documentation before to get access to the new XI system.
Thanks in advance,
RP

But I have a doubt. How the A RFC systems knows where send the RFC? If there is a TCP SM59 connection with program ID, gateway host and service, and there is 2 XI systems, the RFC was sent to both systems? And then the system that have the same program ID in one interface configuration get it?
Do it is possible send it to two XI systems? Because I need sent some RFC's through the first XI and another RFC's through the new connection. I don't have a lot of experience with XI configuration and SLD, please explain it steep by steep.
Can I do it? Or one R/3 system only can send RFC to one XI system?

I am not n abap developer but I was sure that in the RFC it self you need to specify which RFC destination that particular RFC should use.. and hence when you activate that RFC it will only use the correct SM59 destination

Similar Messages

RFC Adaptive Model Questions

Hi all,
I have some questions about RFC Adaptive Model in Web Dynpro:
1)Can I add a new RFC into a Model without recreating that?
2)Theres a way to WebDynpro dont lost de mapped attributes like an input field thats mapped to an import parameter of a RFC? Because all the times that I change the Model and recreate that, my application lost the link between Controller and View and its generate a lot of work to redo this manually.
Thanks,
Manoel

About RFC models, if I have this schema:
RFCModels
-- ZRFC_A
-- ZRFC_B
-- ZRFC_C
If I want to add a new RFC to this model (ZRFC_D), I can't do that. In this case I want to create a new Model with the ZRFC_D right?
When I import a Web Services Model and I have made some changes in Web Services, I don't have a Re-import option enabled like RCC models. What can I do in this case?
Thanks,
Manoel

Question about RFC adapter

Hi,
There is this little concept about RFC adapter
I would like a liitle clarifiaction about..
Here it goes..
Let's just say I have made an RFC in R/3.
The same I have imported In xi.
now when we say RFC ...By definition
it is a remote enabled function module.
We import the "interface" of the Same in Xi
So if I make changes in the BODY of the RFC in
R/3... do i need to reimport it in XI.
Besides when XI's reciver RFC adapter is using the
Rfc's interface to make changes in R/3
is it using a Copy of this RFC created in R/3
I would like to intercep at the point it's doing so...
tried putting a break point in the body of rfc.
Another question is regarding RFC sender adapter
Program ID..tcp Ip protocol.
Conceptually How does this connectivity takes place
I tried and it worked ...
I dunno How to explain this connectivity taking place
just on the basis of PROGRAM ID...
Kindly Help

Hi Deepak,
+
>>We import the "interface" of the Same in Xi.So if I make changes in the BODY of the RFC in R/3... do i need to reimport it in XI.+
Yes you have to.
>>Another question is regarding RFC sender adapter.Program ID..tcp Ip protocol.Conceptually How does this connectivity takes place I tried and it worked ...I dunno How to explain this connectivity taking place just on the basis of PROGRAM ID...
·An RFC server program registers itself under a program ID to an SAP gateway (not for a specific SAP system).
·If an RFC call is passed on from any SAP system to this SAP gateway with the option Connection with a registered program (with the same program ID), the connection takes place with the corresponding JCo server program.
http://help.sap.com/saphelp_nw04/helpdata/en/09/c88442a07b0e53e10000000a155106/content.htm
Hope this will clarify your doubts.
Regards
Suraj

RFC sender adapter question

Hi Experts,
if we take RFC as sender adapter for communication. from PI aspect, the trigger mechanism is pull or push?
in sender RFC configuration, we need to specify Application Server (Gateway), Application Server Service (Gateway), Program ID, Application Server, System Number and logon credentials. it is more like a pull mode, but i do not see any polling interval to be set, how does PI know when the data is ready?
if the data is pushed from RFC sender system to PI, then there is no need to use a sender RFC channel as in SAP server the destination (PI) information of the RFC is already configured.
Does someone can answer my query? Thanks in advance.
Best Regards,

Hi Aditya,
in sender RFC configuration, we need to specify Application Server (Gateway), Application Server Service (Gateway), Program ID, Application Server, System Number and logon credentials. it is more like a pull mode, but i do not see any polling interval to be set, how does PI know when the data is ready?
You would need to create a program that would trigger the Function Module and use the TCP/IP RFC destination you have configured in SM59.
if the data is pushed from RFC sender system to PI, then there is no need to use a sender RFC channel as in SAP server the destination (PI) information of the RFC is already configured.
The RFC adapter lies in the Java stack, that is why you would still need to configure the sender channel RFC in PI. Otherwise the connection will not work.
Hope this helps,
Mark

RFC Adapter - Where to Register Rfc2XmbService (Sender System or XI ?)

Experts,
I have the following scenario:
R3 --> RFC_ADAPTER --> XI --> SOAP --> THIRD_PARTY
My specific question is, In which system do I need to register the Rfc2XmbService program. Is this done in the R3 system or in the XI system.
If it is done in the R3 system then where is it done cause there is no J2EE administration tool in R3.
Could someone explain exactly what this registration concept is.
Thanks and appreciate any help in advance.
- Ravi
--- I have figured this one out already. The program needs to be registered in XI and Not the sender system.
Thanks
Message was edited by: ravi kumar

Hello,
the Rfc2XmbService registers itself when you activate the RFC adapter in the Configuration but you can preallocate it through the Visual Admin.
Further by default are logging for sync calls not enabled, e.g. you don't see anything in SXMB_MONI.
Therefore go to SXMB_ADM and the Integration Configuration option and under the RUNTIME specific option create an entry for
RUNTIME LOGGING_SYNC 1 (0 is default).
Also make sure that the rfc adapter is activate in the AdapterFramework overview. On the target system call transaction SMGW and go to logged on clients to see if you see the Rfc2Xmb Service. Then in SM59 of the R/3 system you should have an entry pointing to the Rfc2Xmb service and a test should give you an idea if it works.
I'm doing R/3 4.6c -> XI 3.0 -> R/3 Enterprise about 20 BAPIs, no issue.
I hope this helps.
Stefan

Sender RFC adapter High volume messaging

Hi,
This question is related to this thread:RFC connection problem
ERP system is sending through 1 RFC dest. (program ID) 20 requests in a minute. And PI starts to hang. ERP is not able tp sent the messages and after a while the request sent from ERP starts to get cancelled. This is a synchonous scenario. How can I handle such a high volume through 1 sender RFC adapter?

Hello
You can monitor the load on RFC adapter queues/threadsin the RWB
-> Component Monitoring
-> Adatper Engine XIP
-> Engine Status
-> Additional Data
See note #791655 Documentation of the XI Messaging System Service Properties, for an explaination of the queues.
To increase the number of threads/queues, see the blog:
1) /people/kenny.scott/blog/2007/08/20/messaging-system-queue-properties-after-xi-30-sp19-xi-70sp11
2) /people/kenny.scott/blog/2008/12/05/xipi-file-and-jdbc-receiver-adapter-performance-and-availability-improvements - this shows how to prevent a problem on one RFC channel blocking other RFC channels that you may be using.
Also, ensure note #937159 XI Adapter Engine is stuck, has been applied to help overall system performance.
Regards
Mark

Sender RFC Adapter only processes first message

Hi there,
we have a R/3 - XI - 3rd party scenario, where the R/3 - XI communication will be established through a RFC.
The RFC destination was properly configured in SM59 in R/3 and also was the XI's sender RFC adapter, with the same program ID.
We called the RFC in R/3 Abap code and the message succesfully arrived at XI (it could be found in SXMB_MONI). However, any other call from R/3 would not result in a message arriving at XI (no new entry in SXMB_MONI nor in Message Monitoring, at RWB). New messages only appear again if we set the status of the adapter to inactive and then active again. Then the message arrives, but again, only the first one.
Can anyone help with this?
Is there any misconfiguration in XI or RFC Destination?
Or is it the abap calling that should be processed in another way?
Thanks in advance,
Henrique.

Hi,
>>>Or is it the abap calling that should be processed in another way?
the important thing is the commit work
which must be done after call function
and you can only have one call function
before the commit work
do you see any other errors in SM58?
>>>Is there any misconfiguration in XI or RFC Destination?
Or is it the abap calling that should be processed in another way?
one or the other - no doubt about that
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Whera can I find RFC adapter file configuration?

I search for Program ID in RFC Adapter configuration but I don't find the file properties.
Where is?
thanks,
mik

Michelle -
What verison of XI are you using? In 2.0 the configuration file ("rfc_adapter.properties") is in the tech_adapter/configuration directory on the IS; in 3.0, the program ID (for client systems) is part of the communication channel configuration in the Integration Directory. HTH; if not, please reply to this post with a more detailed question.
Paul

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.

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

RFC adapter...How it handles multiple calls...

Hi folks
Basic doc'tation on RFC adapter states...qRFC is not supported..Agreed..
I have a scenario where I need to dump lot of transactions from a flat file to an RFC.
I have split the single structure by 1:n mapping(multi) and pushed each message using a Loop(For-each/Par-For-each) to RFC function..
Now question here..Is this a good approach to invoking RFC's(I find response times to be pretty slow on my server upto 20 secs for each RFC call). Cant I parallely execute all the messages by calling the RFC on SRM systems.(PAR for each loop has a limit of 999 loops)..Is there any other option you can suggest for this scene.?

chk this link
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
there is a recommendation on when to use parForEach. From what i understand , parForEach is helpful if u intend to send "One" Message to multiple receiver systems and intend to handle the responses in different context.I beleive it won't help if u send "different" messages to the same receiver system.
One more approach , i can think of is to make a Jco call from your "Message Mapping" itself using User defined functions instead of "configuring an RFC adapter" and "calling it in ccBPM". The below link should help on this.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/how to perform sap data lookups within xi mappings.
Good Luck
cheers
Saravana

RFC Adapter error - http port configuration

Hi everyone,
on XI 3.0 I have some problems to invoke RFC functions located on a SAP SRM system.
No logs are displayed on the XI Monitor: the message is stopped at the "adapter" level.
It seems that RFC adapter tries to connect to a wrong URL (the Production system URL)and obviously it retrieves these messages:
"Received XI System Error. ErrorCode: NO_RECEIVER_CASE_BE ErrorText: ErrorStack: No receiver could be determined "
"Returning synchronous error notification to calling application: XIServer:NO_RECEIVER_CASE_BE:."
"Transmitting the message using connection http://YYY.sap.xxxx:8066/sap/xi/engine?type=entry failed, due to: XIServer:NO_RECEIVER_CASE_BE:."
In the SLD, the right port for Development system is 8064, the adapter is also configured on business landscape YYY and port 8064. I checked both J2EE visual administrator and Business Landscape customizing without success.
But at runtime the adapter framework point to another system on 8066 http port (and the interface call fails).
My question is: where is this wrong URL configured and from where exactly does it take these wrong informations?
Please, help me.
Alessandro Pozzozengaro.

Alessandro,
There is a very good document on SAP that explains, step-by-step what you are trying to do.
The name of the document is: 'Validating a Connection Between SAP R/3 and SAP XI with RFC'.
Give a look on that. I used it to build the scenario here and it works fine.
Regards,
Tadeu

Problems in RFC Adapter

Hi All,
I'm using RFC adapter to send messages to XI. The import parameter of the RFC is a very complex structure. One of the embedded strcuture contains a table. During runtime, if I use "APPEND line TO tale" statement to fill that table in the client of RFC Adapter, the program dumps. The short text is "After a value an end tag must follow. That did not happen in". This short text is obviously incomplete. My questions are:
1. How can I view the complete short text of this dump?
2. Is there any restriction on the RFC adapter parameter? I only use "import" and "export" parameters. I'll not use "table" parameters. Could I use a very complex structure which contains embedded structures and tables as import parameters?

HI Jerome,
>>>1. How can I view the complete short text of this dump?
have you tried TCODE - ST22 ?
>>>2. Is there any restriction on the RFC adapter parameter? I only use "import" and "export" parameters. I'll not use "table" parameters.
please use the table - this is the parameter for storing many values (lines) of a structure
Regards,
michal

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.

Hi.about RFC ADAPTER

can anybody tell me!
it is either xi calls sender system's function or xi's function is called by sender system for a sender RFC adapter?
thanks!

can anyone want to renew answer for the question?
i am ready to cancel this question!
i am gonna reward point.
thanks everyone to answer question!

An RFC adapter question

Similar Messages

Maybe you are looking for