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

Similar Messages

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.

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

RFC Adapter and BAPI Commit

Hi everybody!
In my scenario I post an RFC call to a BAPI (BAPI_GOODSMVT_CREATE). The call succeeds (empty RETURN parameter, material document numer is returned). However, the resulting material document is not available in MB03 - I assume this is due to a missing COMMIT after the RFC call.
However, our system has SP 18 - and I have read that the RFC adapter is able to add a COMMIT after a successful call automatically starting from SP 14. What confuses me is the fact that the descriptions in the online sources state that I should check the "Extended Mode" checkbox in the RFC adapter config screen and then I should check the "Commit..." option. However, when I set the checkbox for extended parameters, I only get a simple table where I can enter property/value pairs.
Has something gone wrong with the upgrade and my RFC adapter doesn't have SP 18 yet? Or am I doing something wrong?
Regards, Joerg

Hi Joerg,
Check in your Repository if you imported the newest adapter metadata.
Check Software Component SAP BASIS - > SAP BASIS 6.40 -> http://sap.com/xi/XI/System
There Adapterobjects -> Adaptermetadata -> RFC
search after the attribute ..singelBapiCommit
Because you dont see a SP version there.
Maybe its better to search afer the label:
Commit handling for singel BAPI-calls
When you dont find the attribute .. try to reimport your BASIS 6.40 Software Componenent.
Regards,
Robin

RFC to XML-RFC Parsing issue in RFC Adapter as Sender

Hi all,
I tried to use RFC adapter as a sender. The scenario I am trying to achieve is R3 -> RFC Adapter Sender --> BPM --> RFC Adapter Receiver --> SAP Auto-ID system.
The reason to use two RFC adapter and BPM is to log the request message if the RFC call fails. Everything works as expected, except the RFC Adapter Sender.
The RFC I am calling has an input table. The input data I use works fine if I call it via SE37 or remotely from another SAP system. However, if I call it via RFC adapter, when XI parses the data into RFC-XML format, the input data is all messed up.
DATA: BEGIN OF ID_STR,
 ID_VERSION(8) TYPE C,
 ID(96) TYPE C,
 ELEMENT_NAME(50) TYPE C,
 ELEMENT_VALUE(128) TYPE C,
 END OF ID_STR.
DATA: it_id LIKE TABLE OF ID_STR,
 ls_id LIKE ID_STR.
ls_id-ID_VERSION = 'EPC_1.30'.
ls_id-ID = '30340242206DC3C00000000A'.
ls_id-element_name = 'BATCH_ID'.
ls_id-element_value = 'BATCH001'.
APPEND ls_id TO it_id.
CALL FUNCTION '/AIN/UI_MOBILE_MSG_SEND'
IN BACKGROUND TASK
DESTINATION 'RFC_UPDATEAII'
EXPORTING
 IV_BUSINESS_PROCESS = '09'
 IV_COMMAND = 'DO'
 IV_ACTION_TYPE = 'APL2'
 IV_PRT_ID = '31140242200000000F000000'
 IV_DEVGRP_EXTID = 'MOBILE'
TABLES
 IT_ID = it_id
commit work.
And the parsed RFC-XML message is:
<?xml version="1.0" encoding="UTF-8" ?>
<rfc:_-AIN_-UI_MOBILE_MSG_SEND
xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
<IV_ACTION_TYPE>APL2</IV_ACTION_TYPE>
<IV_BTD_EXTID />
<IV_BTD_TYPE />
<IV_BUSINESS_PROCESS>09</IV_BUSINESS_PROCESS>
<IV_COMMAND>DO</IV_COMMAND>
<IV_DEVGRP_EXTID>MOBILE</IV_DEVGRP_EXTID>
<IV_LOC_EXTID />
<IV_LOC_TYPE />
<IV_PRT_ID>31140242200000000F000000</IV_PRT_ID>
<IV_PRT_ID_VERSION />
<IV_REASON_CODE />
<IV_UNAME/>
<ET_RETURN />
<IT_ID>
<item>
<ID_VERSION>EPC_1.30</ID_VERSION>
<ID>206DC3C00000000A BATCH_ID</ID>
<ELEMENT_NAME />
<ELEMENT_VALUE />
</item>
</IT_ID>
</rfc:_-AIN_-UI_MOBILE_MSG_SEND>
You can see the data in the table is all wrong, it should be:
<IT_ID>
<item>
<ID_VERSION>EPC_1.30</ID_VERSION>
<ID>30340242206DC3C00000000A</ID>
<ELEMENT_NAME>BATCH_ID</ELEMENT_NAME>
<ELEMENT_VALUE>BATCH001</ELEMENT_VALUE>
</item>
</IT_ID>
The calling system is a 4.6C non-unicode system, and the destination system is a unicode system (this does not matter since the first part of the integration is between R3 and XI). There is no config found on R3 side to specify non-unicode because it is a rather old system. In XI RFC Adapter config, I checked non-unicode checkbox (I also tested it with this unchecked, but still the same issue).
Have any of you seen this problem and how you resolve it?
Thanks a lot for your help!
Regards,
Hart

Hi Hart
long time no seen - hope you remember me
>The reason to use two RFC adapter and BPM is to log the request message if the RFC call fails
there is an easy way (guess max 3-4 hours) to solve all of your issues
and get rid of a BPM
use IDOC - XI - ABAP Proxy
then you will have IDOC and ABAP Proxy that always log the message on both ends (and you can restart ABAP proxies easily in AII - and every AII supports ABAP proxies) + you get rid of a BPM as it's not necessary as far as I understand (as it's asyn communication right?)
maybe you can go this way and IDOCs always work...
good luck,
Regards,
Michal Krawczyk
http://mypigenie.com XI/PI FAQ

Difference between RFC adapter and a proxy

Can any one tell me the technical difference between RFC adapter and a proxy?
reg

There are advantages / disadvantages for RFC / Proxies / Idocs. So if I am in your position depending upon the requirement I will choose one. Some of the differences are:
RFC and Proxy:
RFC/BAPI has its own overhead of function call.
Proxies communicate with the XI server by means of native SOAP calls over HTTP .RFC does not, so you have to convert from SOAP to RFC calls and vice versa. So XML conversion is required.
ABAP Proxies uses Webservice and Http Protocols.
If you use ABAP Proxy , you can reduce the overhead calling the function again and again.
Proxy and Idoc:
IDOC : After recieving the strucutred data It processes it using a Function Module associated with it.
Proxy : Proxy is a structure where there is no processing function module associated. You need to explicitly write the Business Logic/Call the subroutines here
This is my absolutely my view. Another guy has his own response. So first go through your requirements and then you can decide for what to go.
Also go through this urls which may help you:
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
RFC VS PROXY
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
Re: IDOC and RFC
Re: Proxy Vs IDOC
Thanks
Rodrigo

Attachments with RFC adapter ?

Dear Experts,
I have a SOAP 2 RFC Synchronous Interface in my project, from sender side i.e from SOAP i am receiving data of 20 fields and also the attachment(the format of the file can be JPEG, EXCEL, WORD DOC or VIDEO Files) and these needs to be transferred to SAP R/3 System using RFC Adapter.
1. can RFC adapter able receive and send these format of attachments to r/3 server ? can you please suggest me on this...

Hi Raj,
Thanks..
The attachment will not go to the file system in ECC, as i stated that sender is sending the Data & attachments, at the ECC system a INCIDENT(SAP HSE) will be created by using the RFC, when you open the Incident in ECC system you should able to see the data in the Incident along with the attachment attached.
Regards,
Ravi

How to use IDOC and RFC adapter in 1 scenario?

We have AAA field and BBB field and we want to send AAA field to receiver sap system using IDOC adapter and BBB field to receiver sap system using RFC adapter. But how to use IDOC and RFC adapter in 1 scenario and how to map and what are the design and configuration objects we require to create?

To achieve this you have to use
Two Interface Determinations
Two Communication Channels (IDOC & RFC)
& Two Receiver Aggrements.
Use the Enhanced Interface determination and give your conditions there. Based on you condition your interface mapping will be triggered and data will be sent to IDOC & RFC respectively.

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.

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 - 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

Creating Technical System while using SOAP adapter as sender

hello friends
When I create a business system and technical system in SLD for a sender using SOAP adapter, can i create it as Third-Party. Or do I need to create it as anything else in the list.
Also, when do we create Web AS Java technical systems. I need to know when this option becomes MUST.
Thanks in advance
Ram

Yes u can use third party business system and technical system for SOAP system. Business service can also b used for the same purpose.
U should use webAS Java system in case of Java Proxies
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7d4db211-0d01-0010-1e8e-9b07fc2113ab
Regards,
Prateek

Sender RFC Adapter - Data to be sent from R/3

I am working on a scenario where I have to send data from an RFC-enabled function module from R/3 to a file server via XI. The entire scenario is asynchronous.
Sender: RFC Adapter
Receiver: File Adapter
I have done all design and the configuration. Both communication channels are working. I have the RFC destination also set up correctly in R/3.
However, when I run my ABAP program where the RFC-enabled function module is called, I get a shortdump with the message "senderAgreement not found: lookup of binding via CPA-cache failed for".
Plus: " The error occurred during an RFC call to another system."
Could someone kidly help?

Hi,
Follow these steps :
1. import the ECC_ Server into ID if not done
2. Refresh Cache : Tcode SXI_CACHE
3. Please check for Sender agreement config
4. Check out the parameters when R/3 calls back XI, it passes the SYS-ID and client number and checks the same in the Integration Configuration Under Business System Service-> Adapter Specific Identifiers. The R/3 System ID and the client Number
Also check out these blogs..
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
regards
Aashish Sinha
PS : Reward points if helpful

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.

Logical system and rfc destination

hello all,
what is the difference between logical system and RFC destination?
thanks for ur help in advance.
regards,
vikas

Hi,
In any ALE scenario u need one sender and one receiver system.
Logical systems are just logical representation of these systems but in case of RFC destination u specify technical parameters for those systems like IP address and username and password to connect to that system.
Thus when u create port i.e.we21 u specify actual RFC destination for the system to which u want to connect and when u create partner profile for that logical system u specify this port so when u want to send data to this logical system i.e receiver system port will be used which in turn has RFC destination which will be used to connect to that system.
In simple terms logical systems are logical representation of any system and RFC destinations are physical/techinical systems.
Regards

Technical System vs RFC adapter config parameters

Similar Messages

Maybe you are looking for