Using RFC adapter as TRFC call

Hi Folks,
My requirement is to use the RFC adapter as a TRFC call. Can anyone guide me how to do that ?
Regards,
Santosh

Hi,
Is your RFC at the sender side or at the receiving side?
If it is at sender side, you can call the rfc function module in UPADTE task .
Sample Code:
CALL FUNCTION <FM Name> IN UPDATE TASK EXPORTING ......
If it is at receiver side, you can specify the QoS as EO(Exactly once in the sender adapter)
Re: How to make an asynchronous RFC call using the receiver RFC adapter?
Regards,
Ravi Kanth Talagana

Similar Messages

3rd party to sap using RFC adapter

Hi Folks,
I'm sending some IDOC to sap from the 3rd party. I have to use RFC (TRFC call) adapter as sender and IDOC as receiver adapter.
Can you please suggest me how to configure teh sender side.
Regards....

>
santosh nayak wrote:
> Hi Folks,
> I'm sending some IDOC to sap from the 3rd party. I have to use RFC (TRFC call) adapter as sender and IDOC as receiver adapter.
> Can you please suggest me how to configure teh sender side.
>
> Regards....
In order to use RFC as sender need to configure the below
SAP Side
RFC destination of type T using SM59 tcode
PI side
RFC destination of TYPE t type using same tcode
Note the progid provided should be same in both RFC destionations
Then during execution of RFC in SAP side need to provide the RFC destionation created there
HTH
Rajesh

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.

File to JDBC Using RFC Adapter.

Hi All,
I've been trying to find out a scenario which is like a File-to-Database where RFC is the sender and JDBC is at Receiver end.
Kindly guide me in:
1) What are the steps I need to do when I use a RFC Adapter to pick a file from FTP?
2) Are the steps same for the JDBC Adapter as we do normally in a JDBC Receiver Adapter?
3) Is there any other configuration required for this type of scenario?
4) If I import the RFC only I wanted to know how would the file be picked from FTP Server? Is it likewhile create a RFC we import the File from FTP server.
My Plan of Action to do the scenario is:
1) Import the RFC from R/3.
2) Create the data types for target.
3) Map them both.
4) Use JDBC Adapter on the Receiver end.
These are the steps which I think should be done, if there are any other steps which I need to do, please do tell me.
Please do let me know the steps if all the are wrong as I'm doing this type of scenario for the 1st time.
Regards,
Sreedhar.

Hi,
Though i am not very sure about your interface requirement/design but would suggest you the following links :
Sender RFC :
/people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
Reciever JDBC:
JDBC Stored Procedures:
/people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures
JDBC Receiver Adapter -- Synchronous Select u2013 Step by Step
/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
/people/siva.maranani/blog/2005/09/16/xi-how-to-on-jdbc-receiver-response - XI: How-to
on JDBC receiver response

XI-BW Integration using RFC adapter?/

How to update bw ods using rfc adapter

Hi tariq,
data migration from BI or BW to XI is the most bussiness used application
pls check the link it gives complete details
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/events/webinars-nw-rig/bi%20xi%20integration.pdf
/people/kamaljeet.kharbanda/blog/2005/09/16/xi-bi-integration
Interfacing data into BW using Perl, Ruby, or Python
/people/piers.harding/blog/2005/11/18/interfacing-data-into-bw-using-perl-ruby-or-python
/people/kamaljeet.kharbanda/blog/2005/09/14/sap-netweavercomplete-information-integration-platform
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8c10aa90-0201-0010-98a0-f071394bc9ae
pls do chk this
if it worth pls do the req
Thanx
Sampath

Getting information from SOAP call in R/3 using RFC adapter

I have following scenario:
R/3 (RFC)> XI (SOAP)> WebService
I want to know within the R/3 if the call to the webservice fails (Server not available, etc), that there is a problem.
Is there any exception code or way to fill the exception with a return code? I have tried to map a exception, but it will only be created, if the WS-Application creates the exception not if an error occurs in XI or the AF.
Best regards
Helmut

You can capture exception from R/3 and send it to external WebService. You need to add a Module to your SOAP Communication Channel:
Module Key: SOAP
Parameter Name: XI.SendMode , value = http
Module Key: SOAP
Parameter Name: XI.TargetURL , value = http://XXX(your url to the XI engine)
Module Key: SOAP
Parameter Name: XI.User , value = <username>
Module Key: SOAP
Parameter Name: XI.Password , value = <password>
Once you do this you can get R/3 Exceptions passed to your w/s.
Thanks
Ashish

Error while using DB Adapter in BPEL[Calling a procedure or function]

Hi
I am getting Error while executing the BPEL Process.
1) I created a BPEL Process which uses a DB Adapter. I am using call a procedure or function. My Procedure is shown below. It takes a string a s input parameter and executes that string. I have used an assign activity to assign the input string.
Procedure
create or replace
PROCEDURE SP_QUERY(s_string in varchar2)
AS
l_sql_stmt varchar2(1000);
BEGIN
l_sql_stmt := s_string;
-- dbms_output.put_line( l_sql_stmt );
EXECute immediate l_sql_stmt;
commit;
dbms_output.put_line('Executed' );
-- if SQLCODE = 0 then
--retCodeString := 'OK';
--end if;
END;
I gave input string as "select * from tab", I have also tried a insert statement to a table in which its present in this database. But i am getting the following error.
<3 Jun, 2013 9:42:25 AM IST> <Error> <oracle.webservices.service> <OWS-04115>
Whats the Issue? Is the issue with the procedure or the BPEL process? Please help me out. I am stuck in this

Hi,
According to your message you have selected your procedure, but looks like the procedure is not having any reply or response parameter with it.
Have you executed the procedure separately from SQL editor and see whether you are able to get the response or not ?
If you get response, then how many columns are you getting ?
Check the column names are matching with the schema file generated by adapter and see whether those column names are available as elements in .xsd file.
Example provided below..
In the below link, check the section "9.7 Stored Procedure and Function Support"
http://docs.oracle.com/cd/E23943_01/integration.1111/e10231/adptr_db.htm#CHDFBBCD
Thanks,
Vijay

Using RFC or HTTP adapter

Hi All,
I want to configure a receiver adator as the receiver adaptor in the sap xi system which will receive data from a 3rd party.
In this case among the adaptors RFC, SOAP, & HTTP which one will be the best to use and why ?
Also please let me how to use the RFC adapter as a trfc call.
Regards...

Hi Santosh,
You can receive your data from the 3rd party either with soap or http adapter. You can use rfc adapter for sending data to sap.
RFCs are of 5 types. Please check this thread for detailed information:
standard RFC Vs tRFC
From SAP help:
The RFC adapter maps the following RFC calls to XML messages and the other way around:
● Synchronous RFC calls (sRFCs) in messages with Structure linkquality of service Best Effort (BE)
● Transactional RFC calls (tRFCs) in messages with quality of service Exactly Once (EO)
● The receiver RFC adapter can also process messages with quality of service Exactly Once In Order (EOIO). They are mapped to transactional RFC calls (tRFC).
You have tRFC and qRFC queues. Take a look at this blogs:
/people/sap.india5/blog/2006/01/03/xi-asynchronous-message-processing-understanding-xi-queues-part-i
Regards,
---Satish

RFC Adapter Receiver - change SAP User for each call

Hi guys,
I need to create one connection between PI and SAP, all right, i can use RFC Adapter Receiver, no problem.
But, for each call i need to use User and Password different, then, I would pass SAP User and Password in my XML Payload.
Can anybody help me, please?

hi,
>>But, for each call i need to use User and Password different, then, I would pass SAP User and Password in my XML Payload.
sure we can help you but no in this way:)
it is possible to change the user for RFC adapter but using
principal propagation:
/people/alexander.bundschuh/blog/2007/01/16/principal-propagation-in-sap-xi
this is the way you need to go and not send password in XML payload
(this is certainly not the way and no client will approve it)
why use a password is anyone can see it ?
Regards,
Michal Krawczyk

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.

Difference In RFC Adapter and XI proxy

I am using RFC adapter for master data and XI proxy for transaction data , can anyone tell me what is major difference and what is negative point in using RFC adapter
Thanking you
sridhar

Hi,
Adapters enable the Integration Engine and the Partner Connectivity Kit (PCK) to communicate with different applications.Adapters connect the Integration Engine to SAP legacy systems, as well as to external systems.
In this way, adapters integrate existing SAP components with SAP Exchange Infrastructure, for example. In the process, XML and HTTP-based documents are converted to IDocs (IDoc adapter) and RFCs (RFC adapter) and the other way around. This enables you to integrate your existing SAP infrastructure with the new SAP infrastructure, which is based on system integration and the exchange of XML messages.
The plain HTTP adapter gives application systems the option of communicating with the Integration Engine and exchanging business data in a simple format, using an HTTP connection.
RFC Adapter :
The RFC adapter enables you to use the functions of the Integration Engine or the PCK in existing SAP landscapes. It is used by SAP systems to connect to the Integration Engine or the PCK by using the RFC interface. It supports SAP systems as of version 3.1x.
For FAQs about the RFC adapter, see SAP Note 730870
The RFC adapter is provided by the Adapter Engine and the PCK. It essentially comprises two parts, namely a sender adapter at the Integration Engine inbound channel, and a receiver adapter at the Integration Engine outbound channel.
The adapters are configured in the configuration part of the Integration Builder, or in the configuration part of the PCK. You use the SAP Java Connector (JCo), which enables you to manage metadata. This in turn enables you to map RFC data generically to RFC XML and the other way around.
The receiver RFC adapter can be used for mapping lookups.A communication channel with a receiver RFC adapter can be created automatically for business systems that are defined in the System Landscape Directory.
The RFC adapter maps the following RFC calls to XML messages and the other way around:
Synchronous RFC calls (sRFCs) in messages with quality of service Best Effort (BE)
●     Transactional RFC calls (tRFCs) in messages with quality of service Exactly Once (EO)
●     The receiver RFC adapter can also process messages with quality of service Exactly Once In Order (EOIO). They are mapped to transactional RFC calls (tRFC).
You require the sender adapter if you want to use the Integration Engine or the PCK to process RFCs. The RFC adapter converts the incoming RFC data to XML message format (RFC XML) so that it can be processed by the Integration Engine or the PCK.
You require the receiver adapter if the determined receiver system expects the data from the Integration Engine or the PCK to arrive in RFC format. In this case, the Integration Engine or the PCK must transfer the received XML message (RFC XML) to the RFC adapter. The RFC adapter converts the RFC XML message to a valid RFC call and executes the call.
Proxy :
Generally speaking, interfaces are where functions in a system can be executed. In the context of SAP Exchange Infrastructure, only the following interfaces are relevant:
·        Interfaces designed for message exchange between application systems
·        Interfaces used by a cross-component integration process to receive or send messages, or both
Starting with a cross-system integration process, you can then derive the corresponding interfaces required. SAP Exchange Infrastructure supports this process by using an integration scenario to describe the collaborative process. The integration scenario summarizes the interfaces required for this collaborative process.
You can use SAP interfaces that already exist in systems, non-SAP interfaces that are connected to SAP Exchange Infrastructure using adapters, or define new interfaces called message interfaces in the Integration Repository. Both worlds can also be interconnected in a collaborative process.
Interfaces are an essential component of SAP Exchange Infrastructure:
·        You define the interfaces to be used in an integration scenario.
·        Cross-component integration processes use interfaces to exchange messages.
·        You define the XML transformations for messages that are to be exchanged between two interfaces in a mapping.
·        You assign an interface in a sender system to one or more interfaces in a receiver system in logical routing.
·        You generate proxies to implement your scenario based on message interfaces.
You save interface descriptions (message interfaces, BAPIs, RFCs, and IDocs) in the Integration Repository so that they can be referenced throughout SAP Exchange Infrastructure. However, adapters for external systems do not normally use interfaces; instead they access files or database tables in order to function, for example. For this reason, it is not necessary to import these interfaces into the Integration Repository. If the structure of the message is described using a WSDL, XSD, or DTD schema, you can import the schema as an external definition.
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful

RFC Adapter

Hi
I am using RFC adapter, I am facing java.lang.outOfMemory Exception whenever payload size increases.
Important point: In XI everything is successful.
 But in R-3 I am facing the problem.
Please guide me, how to solve this issue.
Piyush

Hi All
I have set up the connection for Integration builder in R-3.
In sproxy I am able to see inbound and outboud interfaces, I have generated the class for th outbound interface and configured default logical port for the same.
The report is as follows:
REPORT ZAK_TEST_PROXY.
DATA:
Reference variables for proxy and exception class
lo_clientProxy TYPE REF TO ZCO_EMPLOYEE_MASTER_DAT,
lo_sys_exception TYPE REF TO cx_ai_system_fault,
Structures to set and get message content
 ls_request TYPE ZEMPLOYEE_MASTER_DAT361,
 ls_response TYPE ZEMPLOYEE_MASTER_DAT360.
 Instantiate your client proxy.
TRY.
create proxy client
 CREATE OBJECT lo_clientProxy.
 ( LOGICAL_PORT_NAME )
*LOGICAL_PORT_NAME is the name of the logical port that you want to use, which is used to define the receiver. You can omit this parameter if you are using a default port or the XI runtime.
 To send a message, call the corresponding client proxy method. WSDL allows several such methods (specified by the element <operation>). In XI, there is only one method, with the default name EXECUTE_SYNCHRONOUS or EXECUTE_ASYNCHRONOUS. Catch at
*least the exception cx_ai_system_fault:
do synchronous client proxy call
 CALL METHOD lo_clientProxy->execute_synchronous
 EXPORTING output = ls_request
 IMPORTING input = ls_response.
 CATCH cx_ai_system_fault INTO lo_sys_exception.
Error handling
write:/ lo_sys_exception->errortext.
ENDTRY.

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

Is this possible: SAP Java Connector - XI - R3 with XI RFC Adapter?

Hi,
I try to call a RFC on a remote R/3 System over the XI Server in a Java Application with SAP Java Connector.
I have configured a RFC Sender Adapter in XI. I get the
following Exception:
"lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'SenderChannel_RFC"!
Is this scenario possible? Or do the connection from
a SAP Java Connector App to the XI RFC Adapter not work?
You can't set the Client and System ID of a Third-Party or
Standalone Java system in the SLD.
Thanks for any help!
Regards
Wolfgang

Hi,
We use a JCO for directly connecting to sap systems.
In that case we need not use any XI also.
But if you want to use RFC adapter and java application the best way is to use java proxies as sender and reciever as RFC adapter.
I donot think there is any architectural significance in using rfc adapter of XI while using JCO.
Let me know if I mis-understood the context.

RFC adapter vs Proxy? Kindly help!

Hi experts,
When to use RFC adapter and Proxy? Which is better and why?
Kindly give examples.
Thanks
Gopal

Hi,
RFCs-
-Useful when it is already in place.
-No effort required to recode in the ABAP proxy.
-Overhead of function calls.
Proxies-
-Helpful when large volume of data is processing.
- Need to code it .
-Skillset and Effort is required.
More on these threads-
RFC VS PROXY
Go thru these blogs-
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
Regards,
Moorthy

Using RFC adapter as TRFC call

Similar Messages

Maybe you are looking for