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.

Similar Messages

Error "Choose a change request with target system..."

Hi experts,
I am trying to change an infosource and keep getting this error "Choose a change request with target system BWQ"
How do I correct this?
Thanks!

Hi,
Check out source system Id's are properly assigned or not.
go to tools ( CtrlShiftF11)
assign point if it helps
Regards,
sandeep

Can a report in ERP called from CRM system using RFCs??

Hi All,
Please let me know if this is possible, if so , how?
Can a report in ERP called from CRM system using RFCs??
Thanks
Siva

Yes, you should make an RFC function in ERP and inside the
function you can call the report with a SUBMIT. Then in CRM you can call the RFC function...
Best regards,
Iván
P.D.: Give points if answer helps!!

Mapping XML into 3rd party system using XIF adapter

Hi Gurus,
First of all let me thank all of you for a tremondous contribution you are making for these kind of topics(CRM XIF) in SDN. I could solve half my problems by looking into your replies.
But I have a new & similar problem now. I am able to create and send XML file of order data into 3rd party middleware system using XIF & SOAP framework. But the 3rd party system(business connector) is unable to parse this XML file in their system. They keep getting the error message invalid XML file. I tried testing that myself and it gives me the error 'SOAP-ENV' error. They even tried some workarounds using some SOAP wrappers but it still didn't work. They are asking me to provide a DTD (data type definition) to this XML file generated out of SAP. Not sure if anyone has seen a similar problem like this but our interface is stuck at this point.
Any suggestions would be helpful.
Thanks,
Sunil

Hi,
We have figured out this problem for ourselves. The 3rd party system gets this error because SAP generated 2 XML tags in the beginning of the XML file which cannot be interpreted by XML spy or many XML parsing softwares. When we deleted the first 2 tags we stopped getting that error. But it wasn't a feasible solution for us to delete the first 2 lines in the XML file and then save it and then parse it. We preferred an alternative approach via IDOC's instead of processing XML files directly. Its also better because the size of XML file is much bigger (15 mega) than Idoc ( max of 4 mega bytes). But if you have to process XML files only then you cannot do that for real time or near real time processing as the parsing of XML file nearly takes more than 10 min. And it is definitely not preferred way especially if your middleware system has the capability to process Idocs from a middleware architectural stand point.

Call remote function on a satellite system using RFC target sys option

Hi all,
I am on the Java stack and I would like to call the ABAP stack of a statellite system. I can create a JCo connection on this system directly but for security reason I am not allowed to do that. I would like to call this system through the ABAP stack of my machine (I am in dual stack environment).
- How can I use RFC target sys (available in SE37 for Remote-Enabled functions) with my JCo connection?
- Or, is there a generic function which can call all other functions on a remote system (still using RFC target sys)?
Many thanks,
Stephan

Siddhesh - thank you for the link; the blogs by Thomas are required reading as far as I am concerned.
Hi Raja;
 do you mean another ABAP system (was6.40)?
and from here using another FM you call the 4.6c
system RFC ?
Yes, that is what we are doing. We are calling a web service from an Intranet form to the 6.40 system that, in turn will call the 4.6C system and pass the data back to the Intranet form (through 6.40)
 may be you could pass the RFC destination as import
parameter to the 6.40 RFC and use the same will the
call to 4.6C RFC from the 6.40 RFC
That would work, but it would be more beneficial to just use the function module on the 6.40 system as a proxy to the function on 4.6c and not have to enter code in it each time.
I had thought of writing just one function module in the 6.40 system that could dynamically call any different function module in 4.6c (based on the input parameters), but since were are trying to accomplish SOA, we need visiblity to each web service (ergo function module).
If it's not possible, that is OK I am just hoping someone had found a way to pull this off.
Thanks!
John

Technical System vs RFC adapter config parameters

Hi All
I am working on a scenario with Receiver RFC adapter.While configuring the adaptor ,I had to provide Application Server name and other log in details.
Also the revceiver determination had a business System associated.And in SLD we map the business system with a technical system.
Does the technical system(host name ) has anything to do at runtime?I had to use it to import the RFC though at design time.
Thanks,
Premjit

>
Premjit Mishra wrote:
> Thank you all for the responses.So just to understand a bit more,at run time ,which properties are used ito connect to backend SAP system ie frm Technical System config or from the RFC receiver config property.
AFAIK, RFC receiver adapter config proeperties are used at runtime for connection ..
Technical system details provided are useful in case in case if you are going to use IDOC as the details like
system no and client will be referred from there in your business system associated...
HTH
Rajesh

Error when posting to WebService on XI system using Soap

Hi,
We have a scenario where we have a 3rd party system posting to the XI webservice. The sender Soap adapter is configured for HTTPS without client authentication.
I am using soapui software to test the connection. Before changes were made to the configuration for SSL, we were able to post to XI using the http url. After the changes were made, when posting using the http url no response is received and no message is produced in XI. Also, when we change the url to https and using the port 50001 to post the SOAP message we get the following error:
The following error occurred while parsing the HTTP request: com.sap.engine.services.httpserver.exceptions.ParseException: Incorrect request line: [CONNECT eagnmnsu39e:50001 HTTP/1.1]..
Can anyone provide some insight to the issue?
We are using a user ID with the correct security profile
Thanks.

http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r0m0/index.jsp?topic=/com.ibm.etools.mft.doc/ac04595_.htm
Hope this link will help you.
BR,
Alok

Calling Transaction from other system using RFC

Hi ,
I have one button on screen(say Screen-A), in ECC. when its pressed the transaction '/SAPAPO/BOPIN' gets called from APO.
For calling transaction from APO I am using FM - 'ABAP4_CALL_TRANSACTION'.
I want the initial screen of that transaction to retain some values which I fill on the Screen-A(the screen which has that button).
When I call the transaction from ECC itself (ex. C006), the initial screen of C006 retains the value on Screen-A.
I want the same to happen in case of calling transaction from APO.
How to achieve this? Would it need the changes in IMG (SPRO)?
Please note that, Screen-A is initial screen of transaction 'md05' and I want to retain vaules of Material, MRP Area, Plant.
Thanks,
Sujeet

Builld a RFC enabled FM () that wrap the call of Smartforms (*) in the other system.
Regards,
Raymond
(*) [Writing Remote Function Modules in ABAP|http://help.sap.com/saphelp_nw04/helpdata/en/22/0425f2488911d189490000e829fbbd/content.htm]
(**) [Integrating the Smart Form into the Application|http://help.sap.com/saphelp_nw70/helpdata/en/1c/f40c5bddf311d3b574006094192fe3/frameset.htm]

We are trying to send the ACK's to the legacy system using JMS adapter, MQ

MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: CC_R_JMS_MATRICSToECC114_ACKon node: 203681450 having object id: ac4f4f5b61793872a403ec3ad546e979 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///TQ1E.KFCAT.DEV.ASAPTOMATMM.REMOTE?targetClient=1, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 1188331798094 JMSCorrelationID:46d4af9f-6f63-1ef4-e100-00000a3597fc JMSDestin.
Any thoughts would be greatly appreciated.
Regards,
Srujanks

You cannot send ack messages to a JMS queue as ACK messages have no payload.
You have to tranform the ack message to a real message, this can be done with BPM.
Regards
Stefan

RFC Adapter to connect to Non SAP System

Hi,
I have a scenario to connect to a non SAP system using RFC adapter. I am not used to the same. I need to know whether this is possible and what are the steps to be done.
Thanks and regards
Siji

Hi,
These links should help.
Non-SAP application connecting to PI via Sender RFC Adapter
Error by setup RFC Interface with non SAP system
SAP PI to Third Party system through RFC Connectivity ??
Regards,
Jannus Botha

Error when sending data request

Hi All,
   i have scheduled info package for different type data sources in bi 7.0, for this i am getting the data from ecc 6.0 . all of this schedule's showing the status "error when sending data request" with the following details.
status
diagnosis
the request idoc could not be sent to the source system using rfc
system response
there is an idoc in the warehouse outbox that did not arrive in the ale inbox of the source system
in step by step analysis it is showing
   rfc to source system successful showing with ash status
   data selection successfully stated and finished ? show with red status
in that details tab
request : showing with green status
everything ok
extraction :showing with red status
missing messages
transfer(idocs and trfc) : missing messeges
processing(data packet) : no data
    it is showing technical status with red as processing overdue
                       processing step call to source system
   so it is showing error with 0 from 0 records.
please any body could help me for solving this error.
regards,
naveen.

Hi
Seems you have connectivity issues between the Source system and Bi system.
You need to check whether you have data on R/3 side via RSA3 with Full / Delta Update Modes with Target System as your BI system.
RSA13--Source System -- Right click Connection parameters/check/Restore/Activate again Say Replicate All Data Sources (If Possible , provided if you have time because it consumes lot of time )
You need to check the tRFC Queue SM58/59 for any Stucks and WE19/20 for IDocs.
Much of BASIS Issue .
Hope it helps and clear

How do I send a raw (push) notification from the server side using an Azure mobile service?

Hi there!
Currently I'm able to send toast notifications to my user from my Azure mobile service using the following line of code in one of my server side scripts:
push.wns.send(opponent_id, payload, 'wns/toast', {
success: function(pushResponse) {
console.log("Sent push:", pushResponse);
request.respond(statusCodes.OK, {});
error: function(pushResponse) {
console.log("Error Sending push:", pushResponse);
request.respond(500, { error: pushResponse });
But I would like to send a raw notification to my user now, not a toast notification. I've set up a background tasks which runs as soon as a raw notification arrives(I've tested this through the diagnose option of my mobileservicehub and it works).
I want to send a raw notification now from the server side and I'm kind off lost on how to do that. I've looked for it but can't seem to find an answer to that question, I might be looking for the wrong stuff though.
I'm looking for a solution that looks the same as the one for a toast notification(as demonstrated in the code above).
Your help would be greatly appreciated!
Thanks in advance!
Jan

I found the solution to this it was in fact really really easy, I should have read the documentation more properly since it clearly said that the payload for raw notifications could be literally anything but the client has to take care of it.
So I figured that out!

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.

How to upload a file in R/3 system through RFC using WebDynpro Java

Hi There,
we need to pass a file(mostly xml) using file upload feature in Webdynpro and then need to pass the file in R/3 system using RFC. What should be importing parameters for RFC and how should i implement the fileUploadUi in this case.
I have already seen example of how to add this in a table input form.
Any pointers will be great help.
Regards,
Sudhir

Use this code to convert the file content to bytes in WDJ:
Apart from the resource context attribute create a context attribute of type binary.
get the data from resource & convert it to binary & pass that to RFC. U can use this code for conversion
byte fileData[] = null;
try{
InputStream fileIs = wdContext.currentAttachCVElement().getFileData().read(false);
ByteArrayOutputStream bOut = new ByteArrayOutputStream();
int length;
byte[] part = new byte10 * 1024;
while ((length = fileIs.read(part)) != -1) {
bOut.write(part, 0, length);
fileIs.close();
fileData = bOut.toByteArray();
bOut.close();
} catch (Exception e) {
wdComponentAPI.getMessageManager().reportSuccess(e.toString());
Here getFileData reffers to the attribute of type resource. rest of the code u can use directly.
Use this code in your R/3 function module to convert the data.
*" VALUE(XCONTENT) TYPE XSTRING OPTIONAL
OUTSTRING TYPE STRING,
CONV TYPE REF TO CL_ABAP_CONV_IN_CE.
Convert data passed from WD Application.
CONV = CL_ABAP_CONV_IN_CE=>CREATE( INPUT = XCONTENT ).
CONV->READ( IMPORTING DATA = OUTSTRING ).
SPLIT OUTSTRING AT CL_ABAP_CHAR_UTILITIES=>CR_LF INTO TABLE IT_DATA.
DELETE ADJACENT DUPLICATES FROM IT_DATA.
Let me know if you run into issues, please award points accordingly.

Logical System for RFC-Business system?

Hi,
I want use RFC adapter for my scenario like File to RFC.
The query is like, is there any importance to use Logical system for my Business System which is using for my RFC Adapter in my communication channel.
Regards
Gopi

logical system name is relevant only for Idocs, but it is always a good idea to maintain the technical and business systems with all the information you can provide.
you can check the logical system names of ABAP application servers at bd54 tx code.
Regards,
Henrique.

Error in pushing a request to R3 System using RFC Adapter

Similar Messages

Maybe you are looking for