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

Similar Messages

Problem with RFC adapter (JCO Exception RFC logon failure)

Hi ,
I have SOAP to RFC scenario.
Scenario with same configuration (RFC adapter) is working in QA system.but when I have transported to PRODUCTION system
it is showing
com.sap.aii.af.ra.ms.api.DeliveryException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE:
I have gievn max conn=10 ;Refresh the cache also
and checked Roles and authorization also but still I am getting the same error.
Regards

Hi ,
I have created all the objects manually. and it is working.
now it is showing other error when I am sending the messages from SOAP side it is showing
MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID DF2C6D6E40E935CB970DEE3A71049BF9 Software Component C3D5E1D1C75311DDB94DE33C0A1E01B6</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Interface mapping Object ID DF2C6D6E40E935CB970DEE3A71049BF9 Software Component C3D5E1D1C75311DDB94DE33C0A1E01B6 does not exist in runtime cache</SAP:Stack>
for this I checked the Interface determination step and receiver determination ,mapping program all looks correct.
I have refershed cache also both Complete and SLD.
but nothing is wroking
Please advice.
Regards

Problems with RFC Adapter, utf-8 encoding and special characters

Hi,
How can I change my enconding UTF-8 for ISO-8859-1 in my RFC ADAPTER SENDER?
Regards,
Sérgio

Hi,
To change encoding of xml you can either use this piesce of xslt after your mapping as a next step
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" encoding="ISO-8859-1"/>
<xsl:template match="/">
<xsl:copy-of select="*" />
</xsl:template>
</xsl:stylesheet>
or use adapter module but now I can't remember name of it.
Best regards,
Wojciech

FILE-RFC ADAPTER problem

Hi all,
I am trying file->xi->rfc adapter scenario.
My scenario is employee information is written to flat file n will be kept on ftp server.THe file adapter will pickup the file and sends it to rfc adapter through pipeline service.
This is going well. The problem is the data is not being updated into receiving sap system.
in SXMB_MONI transaction the messages are successully processed . But there are no messges in rfc adapter when i gone through idx5 transaction???
Any one have idea??
Thanks in advance.
Rgds,
Ram Sri

sxmb_moni only shows the status of the integration engine's processing, not the result of what happened in the rfc call. First, you can check if the adapter framework successfully passed the message to the destination system (not on moni, thru RWB)
as far as did the rfc succeed - it's as difficult as always with internal processing. We did a lot of testing by debugging modules on the destination side (manually putting in the data as the adapter would've to step thru & see where the message is "lost") - have not yet found a better way, sorry. It's not so much a problem with XI, just in general the difficulty to debug rfc's

Problem in Sender RFC adapter

Hi all,
Our scenarion is like this
RFC -> XI -> File
When we are calling the RFC ( inside a program ) from the client we are getitng a shortdump with the error ...
'JCO.Server could not find server function 'STOCK_ENQUIRY_OUT'
any idea where is the exact problem '?
regards
Goutam

Have these basic checks;
1. Import the RFC and activate the same in XI.
2. Configuring of RFC adapter - /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
3. Troubleshooting - /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

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
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".
- 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 Problem: Adapter Engine Field Blank

Hi,
I want to invoke a BAPI defined on a R/3 system. I am trying to create a RFC Adapter in the Integration Directory by creating a communication channel.
The problem I am facing is that when I define the Adapter Type as RFC, the Adapter Engine dropdown list is blank and it does not contain any entries.
On passing a document through XI, I can see the following error in the monitor:
<SAP:Code area="INTERNAL">ADAPTER_NAME_INVALID</SAP:Code>
<SAP:P1>RFC</SAP:P1>
<SAP:P2>PLSRV_CALL_ADAPTER</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unknown receiver adapter (name = RFC)</SAP:Stack>
what do i need to configure on the XI and R/3 side ?
thanks,
Manish

i followed the steps but i am not getting the populated adapter engine list.
Actually, the Association shows a list of logical systems to be added (Application System, BC Application Server, BC Central Server Instance .....). I experimented with many systems but it is not working.
My basic problem is I need to call a BAPI from XI. The XI monitor shows the error :
Adapter Name Invalid.
Unknown Receiver Adapter (name=RFC).
Now, for the RFC adapter, I have not given it any name. My Communication Channel is called GeneratedChannelRFC. I am not sure where this error is coming from. I would appreciate any help to solve this error.
thanks,
Manish

RFC adapter problem: ICM_HTTP_CONNECTION_FAILED

Hi All,
We have problems with a RFC adapter. The error is not consistent. Most of the time it works, sometimes we get the error below. It looks like the http communication with the XI adapter Engine fails. The problem is described in note 804124, but this note does not give us the correct answer.
We are on SP15, has anyone an idea?
Thanks,
Frank
Error:
Error when receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED
404 Resource not found
Partner not reached
Error:     -20
Version:     6040
Component:     ICM
Date/Time:     Tue Mar 7 09:35:20 2006
Module:     icxxconn_mt.c
Line:     2121
Server:     pxpci_PXP_10
Detail:     Connection request from (89/30444/0) to host: pxpci.fil-eu.sv.philips.com, service: 51000 failed (NIECONN_REFUSED) EX-T89, U30444, 660 XIAFUSER, 130.139.212.156, 09:35:20, M0, W0, , 1/0

Hi Michal,
I don't think the timeout is the problem here, as you can see in the error, it states the the resource can not be found (404) and further in the error you find that the connection is Refused. This error occurs within in second after the message comes into SAP XI.
Hi Holger,
The ICM log gives the same error as in the message monitoring. But I think it is not on level 3. I will try that.
Thanx,
Frank

RFC Adapter Problem: Necessary Roles?

Hi XI Gurus,
Our team is working with a File-to-RFC scenario. We are using a custom RFC, which uses BAPI_GOODSMVT_CREATE within it, to post data for Goods issue, Goods receipt and Transfer Posting. We are using the credemtials of a user, sapxiuser, within the RFC adapter. Can anyone please tell me what are the roles that are to be maintained for this particular user at the R/3 end?
Points will be rewarded!
Thanking in anticipation,
Amitabha

Hi,
Remember to add explicit commit in the communication channel:
"
Commit Control for Individual BAPI Calls
If you want to use this communication channel to call BAPIs as remote-enabled function modules that change data in the database, set the indicator.
If executed successfully, the transaction is written to the database by calling the function module BAPI_TRANSACTION_COMMIT explicitly. If an error occurs, the transaction is rolled back by BAPI_TRANSACTION_ROLLBACK.
The result is determined by the value of the field TYPE in parameter RETURN. If successful, the tables are empty and the values , S, I, and W are displayed. All other values are regarded as errors.
To change this setting, set the indicator BAPI Advanced Mode.
In the Successful RETURN-TYPE Values table, enter the values that should lead to a successful execution.
"
Regards,
Wojciech

Problem with sender RFC adapter

Hi All
I have created one RFC adapter for which i have created wrong business system and all then i have deleted that and i have created on more RFC adapter but when i am testing my scenario its taking the old one which i have deleted from the Integration directory. I have refreshed the cache using sxi_cache and also in RWB. But still i m getting the same error...
Could you please tell me how to resolve this error

Hi
Yes i have configured RFC as sender communication channel. I have deleted the old one including the business system. but still in adapter monitoring i m getting the error "com.sap.aii.af.rfc.afcommunication.RfcAFWException: alternativeServiceIdentifier: party/service from channel configuration are not equal to party/service from lookup of alternativeServiceIdentifier (CPA party/service/channel ''/'Whirlpool_BS1'/'RFC_Source_CC', lookup of alternativeServiceIdentifier for party '', schema 'TechnicalSystem' with 'QN9#800' returned party/service of ''/'QN9')"
but i have deleted the whirlpool_bs1 business system.
Why still i m getting this error.
Thanks & Regards
SUN

Problem with RFC sendder adapter.

Hello All, Any help will be greatly appreciated. I am creating interface from CRM to XI using RFC adapter and XI to Forums using SOAP adapter. I configured in IR and ID and trying to push the RFC in CRM and I am getting the following error.
lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS
I went through the previous forums and I got no luck following those recommendations.
Thank you very much for your help.

Hi ,
Check these-
1) Sender Agreement and Program Id for the RFC is correct or not
Sender RFC Adapter
Refresh the cache of the Adapter Engine.
1) sxi_cache->goto-->AE Cache
2) check for CPA Cache also
Just go thru following link from service.sap.com
https://websmp103.sap-ag.de/~sapdownload/011000358700002757652005E/HowtoMintorAF.pdf
http://help.sap.com/saphelp_nw2004s/helpdata/en/0d/28e1c20a9d374cbb71875c5f89093b/frameset.htm
Did you refresh Adapter Metadata in the SLD ? This is mentioned in the Adapter Monitor document.
Change the RFC adapter once again and activate the same. and then run the scenario. Did you change the RFC after importing..If so again import it.
Hope this helps,
Regards,
Moorthy
Message was edited by: Krishna Moorthy P

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

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

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.

Problems in RFC Adapter

Similar Messages

Maybe you are looking for