RFC Adapter Debug

I would like to trigger a debug in the backend R/3 system for an RFC coming in through the RFC adapter in XI 2.0. Does anyone know how this is done. I suspect that it should be an option in the RFC Adapter configuration similar to RfcAdapter.trace, but I cannot seem to find one.

Hi,
I also wanted to debug the RFC coming from BW system to XI. We raised an oss note to SAP , and they said that its not a background job , but it is a module pool . So I am also stuck over here.
The only debug option is RFC trace Log file , where in the end it gives a message , what went wrong .
Thanks,
Pushpendra

Similar Messages

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

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,

RFC Adapter - JCO Exception - Please Urgent

I am developing a scenario from File--RFC integration. I am using File and RFC adapter to perform this transaction.
The File Adapter is picking the file properly and the trnaformation (Mapping Program) is also happening properly. But the RFC is throwing the following error. I got this error info from the Runtime Workbench.
Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling ZPS_XI_ACTIVITY_CREATE in remote system (RfcClient[BAPI_CreateActivity_Receiver]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR
Error Delivery of the message to the application using connection AFW failed, due to: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling ZPS_XI_ACTIVITY_CREATE in remote system (RfcClient[BAPI_CreateActivity_Receiver]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR.
The RFC is executing without any problem when I execute this from the transaction SE37.
I have created communication channel in Integration Directory in appropriate manner.
I also created RFC destination in the XI system (TCODE SM59) and the same is using in the "Receiver Determiiation - Service".
I have not done any configuration at SAP R/3 side. Is any config required at R/3 end for this scenario - please let me know.
Please throw some light on this. I will greatly appreciate your help.

Friends,
Please suggest on this vague problem that I am facing. Your help would be greatly appreciated.
1. I am using SAP-PS (Projects & Systems) BAPI 'BAPI_BUS2002_ACT_CREATE_MULTI' to create the activities for a project. According to this BAPI documentation,
- First call 'BAPI_PS_INITIALIZATION' before make this BAPI call
- After BAPI call, we should use 'BAPI_PS_PRECOMMIT' and 'BAPI_TRANSACTION_COMMIT'.
2. Hence, I have developed Z-Func Module with Initialize, BAPI call - then Pre Commit and Commit.
3. This is executing from SE37 without any issues. Other parameters to make a remote call is also set properly.
4. To make sure that, I made a JCO call from Java Program using PDK for Java. This is also working fine.
5. But when I used this in the XI scenario (File-XI-RFC) this is showing ABAP dump and this is invoking from Pre-Commit module.
I couldn't figure it out why it's happening like this.
I did lot of troubleshooting and the details are as follows for your reference.
1. The mapping program is working fine without any issues. I confirmed this by writing these input values to the file (ofcourse lot of pain) inside the function module. All the values have been parsed by XI and coming to Func Module as expected.
2. No issues with logical destinations (SM59).
3. I have tried other options such as clearing the Cache...etc.
Hence, please throw up some light. If any body tried with these kind of BAPI (needs initialize, pre-commit and commit) I really appreciate your effort.
Can we enable the debugging of func module when the XI makes a call...? - I tried with Standard options that seems doesn't work.

RFC adapter - AE_DETAILS_GET_ERROR - no adapter engine

Hello,
have a strange error.
Our scenario connects two R/3 systems via RFC adapter (outbound / inbound) for an RFC in a standard R/3 function module SUSR_ZBV_GET_REMOTE_PROFILES.
The RFC is synchronous.
When starting the RFC call from the sender system the error message in the trace is "exception while reading from SLD:Property sap_xiadapterservice.adapterType does not exist".
Message in RWB:
"Transmitting the message using connection http://abc038.ceu.test.com:8077/sap/xi/engine?type=entry failed, due to: XIServer:AE_DETAILS_GET_ERROR:Property sap_xiadapterservice.adapterType does not: Unable to find any Adapter Engines."
- SLD connection is working
- Vis.Admin.: no problems found
(SAP RFC adapter active)
- Component monitoring: no errors
- all rfc connections checked: ok
Does anybody have an idea, how to fix that?
Best regards
Dirk

Hello Dirk and all posters,
We get the same problem just as you described.
We also see no entries in the sxi_cache part for the adapter engine which indicates a problem in getting AE metadata from the SLD.
I see we are all not alone so i believe SP12 is the cause for the problem.
We have another SP11 system that works well.
We tried all those things to understand the problem:
1. look at the structure of the calsses maintained in the SLD to make sure the property "adapterType" exists.
2. Checked the log of the SLD with level "Finest" to make sure the data for the property is sent - all OK.
3. Try to completely delete SLD and reimport CIM 1.4 and CR content 2.0 - all the latest from the web - problem still exists.
4. Put a huge trace on the RFC gateway in the ABAP engine to make sure all XML data is received from SLD server including specific proprty. all ok.
5. Of course we made sure all caches are refreshed, access to SLD is performed all right (logs, traces).
6. Try to disable SM59 entry: SAPSLDAPI and look at the trace in SXMB_MONI. It shows error of connection of course instead of the error of the non exsitene property. But it still shows the error for not getting the access data - so this is only a side affect of the real problem.
Now, as you can see we turned the system from inside out.
I beleive the problem is SAP's problem regarding the parsing of the COM model in the CIM client. I believe that if i could debug the actual abap that parses the XML in the ABAP WAS i would find the problem - i could'nt find a way of debugging the actual processing of a message in QRFC so i'm stuck here.
- Does all of you who have the problem has SP12 ?
- Does any one have an idea of anything else we can all check ?
Good luck for us all :->
Yoad Snapir.

RFC Adapter Trace!

Hi Everybody,
I'm currently trying to debug a problem with the RFC adapter. Is there a flag that can be set that would allow me to see the actual JCO code being executed by the RFC adapter? I'm in a situation where the RFC is being executed and it's generating an error message but it seems to be data related...however, the data in the XML looks correct so I need to see how the RFC adapter is interpreting the XML message. Of course, I'm definitely open to any other ideas that you may have.
Thanks alot,
...Scottd
p.s.I'm using XI 3.0!

Hi, Soctt,
Go to the J2ee Visual Admin tool. Check the service Log configurator. Go to the RFC adapter file and set the trace level to debig mode. Save it. Noe try to test your sceanrio and check the file system for the traces...You have more info from the trace now.
Looks like you have a problem with the data you trying to send thorouch XI.
Regards
Prasad

Queries on RFC adapter

Hi,
Reading up on RFC adapter at the moment
Read that RFC has limitations such as No Call-Back, no RFC-GUI-Debug, no qRFC and no SNC.
Is there any link that will give a more detailed explaination on the above items?
Thanks.

Hi,
These links provide more information
http://help.sap.com/saphelp_nw04/helpdata/en/11/028417f9f8b24cbe1b0b398e1cb76a/frameset.htm
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
/people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii (search for RFC adapter)
SAP note : 730870
Regards
Vishnu

RFC adapter limitations

Current limitations of RFC adapter are: No SNC, No Call-Back, no RFC-GUI-Debug, no qRFC.
Could you please tell me what they mean ?? especially SNC ??
thanks
kumar

Kumar,
No SNC: SNC is secure network communications. Check this sap help for further information on this palnati:
http://help.sap.com/saphelp_nw04/helpdata/en/ff/7932e4e9c51c4fa596c69e21151c7d/frameset.htm
No Call-Back:
http://help.sap.com/saphelp_nw04/helpdata/en/22/0425ac488911d189490000e829fbbd/content.htm
No qRFC:
Check this help:
http://help.sap.com/saphelp_nw04/helpdata/en/0b/40693c1b331c6ae10000000a11405a/content.htm
---Satish

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.

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

Restrict messages in RFC adapter or in source/sending (SAP R/3) system

Hi All,
I have SAP R/3 to web service scenario via XI (RFC to SOAP). In that scenario RFC caries the attachments, some time the attachments size is more than 5mb. Due to that java stack of XI becomes unresponsive. Due to that SMQ2 gets filled up with the entries and other scenarios are also severely effecting.
Is there any way to restrict the message, if itu2019s size is more than 5mb in RFC adapter of XI or can we stop the processing/sending of such a messages in source system itself (SAP R/3).
I welcome all your suggestions.
Thanks & Regards,
Venu V

Hi Praveen,
The attachments to the tickets in source system. The RFC caries that data, once that data size is more than 5mb then it affecting the server.
I am getting following errors
u201Ccom.sap.aii.af.ra.ms.api.DeliveryException: Could not create Message from TransportMessage. Reason: com.sap.aii.af.ra.ms.api.MessagingException: com.sap.aii.af.ra.ms.api.MessagingException: Could not parse XMBMessage due to Read timeout. The client has disconnected or a synchronization error has occurred. Read [45434] bytes. Expected [101981].u201D
u201CJCO_COMMUNICATION_FAILURE
Error opening an RFC connection
"COMMUNICATION FAILURE" during JCo call. Error opening an RFC connectionu201D
Thanks & Regards,
Venu V

RFC adapter in XI 3.0 not working properly with BAPI in R/3 4.6C

Here is the scenario.
An XML file is received from our customer. This file contains purchase order information that is used to create a sales order in our SAP 4.6C system. Once the sales order is created an acknowledgement is generated and this is returned back to our customer in an XML format. This scenario is working perfectly fine in our XI 2.0 system but is not working properly in our XI 3.0 test environment. Our custom function module in R/3 is a wrapper function that uses a standard SAP BAPI to create the sales order. Part of the function module does use the statement
call function 'BAPI_TRANSACTION_COMMIT'
The last thing the BAPI does is call another function module that using an RFC destination that will return and order acknowledgement.
Here is what happens within XI and our SAP system.
The XML file is received and mapped to our imported RFC. The RFC adapter is called and the information is passed onto SAP where our customer function module executed. The sales order is created within SAP without any problems and the second function module is called which references an RFC destination assigned to our XI 3.0 system. The information is sent back to XI and an appropriate file is created for our customer. All seems to be working properly except that when the original RFC is sent from XI to SAP, SAP creates a short dump stating
"call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:" Then it is put back into the que where 5 minutes later it executes again and trys to recreate the sales order in SAP. (again, this same function module executing from XI 2.0 works fine)
I believe I have everything configured properly because the SAP side is being executed and I am successfully passing information back from SAP to XI. However the original function module in SAP is failing with the above error message. It appears that the original function module cannot communicate back with XI. I have had SAP looking at this issue and they have not been successful yet in solving this problem.
Any ideas.
Thanks,
Jim d'Hulst

Hi,
I think the problem is with the send back of acknowledgement to XI. Does the DeliveryException state something about the sender agreement? I guess you are using a statement like below:
CALL FUNCTION 'ZABCD'
destination <tcp/ip destination>
exporting
input = ack.
In that case, check whether the TCP/IP destination is working fine. Also, to be able to exchange message, the structure of the Function Module ZABCD needs to be identified as the sender in XI Configuration (Integration Directory).
Also, check your config with the blog mentioned below:
<a href="/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit">/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit</a>
Regards,
Amitabha

Dynamic user in RFC Adapter

I configure a RFC Receiver adapter to communicate with R/3. In my client application (via Webdynpro) I send the message that use this communication, but I need to call the RFC using a dynamic user/password, that is, the user credentials that is logged. Is it possible? How I do it?
thanks.

Hi Elton,
I don't think so, it is possible to have dynamic user ID and password for the RFC adapter. As of now...
Because you need to enter the user id and password while configuring adapter itself.
But if you want , you can call different RFCs based on the Condition etc.
Hope this helps,
Regards,
Moorthy

RFC Adapter Debug

Similar Messages

Maybe you are looking for