XI RFC Adapter 4705: Wrong response

Hi all,
I am trying to configure an RFC Adapter in XI. My scenario is as follows: SAP -> RFC Adapter -> XI -> File Adapter -> Local filesystem.
When I try to send the message I get the following error in the trace document for the RFC Adapter:
>>RfcAdapter> Fri Oct 15 11:48:38 CEST 2004>>
> App2Jco: got RFC Adapter exception
> exception occurred, detail:
> 4705: Wrong response - Z_PS_PROJECT_INFO_TO_XI.Response or *Exception expected
What is strange is that the file is actually written (though empty) on the filesystem, and even more strange is that there are no xml-messages passing through XI (using t-code sxmb_moni).
Can somebody please help me understand this?
Best Regards
Odd Hilt

Hi Odd,
I'm also trying to configure a RFC adapter scenario as sender like yours.
I've configured a TCP/IP destination in SM59 as the XI system (test connection is working fine).
But when I execute the RFC in R/3 with the XI system name as the destination I'm getting the error msg "com.sap.aii.af.rfc.afcommunication.RfcAFWException : lookup of binding via"
Can you help me regarding this?
Thanks & Regards,
Dipankar

Similar Messages

Outbound RFC Adapter - Limit in Response

Dear all!
i face the following problem using a Outbound RFC Adapter:
XI2.0:
We call a RFC-FunctionModule which has an output-param of type XSTRING.
The xml-Schema definition for this param in the XI-Repository is "base64Binary".
As long as the output-param has a character-length < 1536, it works fine, but if it is longer, then the following Message can be seen in the XI-Monitor:
"cannot serialize JCo response to XML"
any advice? thankx in advance!
Christoph

Hi ram.
In XI 2.0 RFC adapter is installed on XI engine not as part of decentral adapter like file adapter.
So you need to configure it on XI engine itself.
Thanx and regards
Vinod ahir

HTTP Response code 404 - RFC Adapter des not connect to Integration engine

Hi,
I seem to have problem with XI Integration engine. My integration process does not go beyond adapter engine and it fails with the following error,
Begining of the erorr report -
2006-01-23 13:35:53 Success RFC adapter received sRFC for ZSCEN2_XI from <sysno>/<client>. Attempting to send message synchronously
2006-01-23 13:35:54 Success Application attempting to send an XI message synchronously using connection AFW.
2006-01-23 13:35:55 Success Trying to put the message into the call queue.
2006-01-23 13:35:55 Success Message successfully put into the queue.
2006-01-23 13:35:55 Success The message was successfully retrieved from the call queue.
2006-01-23 13:35:55 Success The message status set to DLNG.
2006-01-23 13:35:55 Error Returning synchronous error notification to calling application: Received HTTP response code 404 : Not Found.
2006-01-23 13:35:55 Error Transmitting the message using connection http://<host>:55300/sap/xi/engine?type=entry failed, due to: Received HTTP response code 404 : Not Found.
2006-01-23 13:35:55 Error The message status set to FAIL.
2006-01-23 13:35:55 Error Returning to application. Exception: Received HTTP response code 404 : Not Found
end of error report -
and the runtime workbench does not connect to Integration engine and fails with the following error,
begin error report -
javax.ejb.CreateException: Unable to log on to system XID in language en with user XIRWBUSER
 at com.sap.aii.mdt.server.integrationengine.IntegrationEngineMonitoringBean.ejbCreate(IntegrationEngineMonitoringBean.java:374)
 at com.sap.aii.mdt.server.IntegrationEngineHomeImpl10.create(IntegrationEngineHomeImpl10.java:185)
 at com.sap.aii.mdt.server.IntegrationEngineHome_Stub.create(IntegrationEngineHome_Stub.java:56)
end of report -
Have anyone experienced the same issue?. Are we missing some post installation configuration?.
Thanks in advance
Regards,
Arul

HI Anulraja,
Your Adapter Engine searches the pipeline url of the integration engine from the SLD.
Check the Bussiness System in Sld , which you'll have defined for XI Server.
It should have ROLE : Integration Server And
pipeline url: http://ux0800:55300/sap/xi/engine?type=entry
should be this if your http port is 55300.
Check if this url is right in SLD-Bussiness System.
You can check the exact http port in transaction sxmb_adm.
Go to Integration engine configuration and then click on check icon(F7).
It should match with that provided in the BS in SLD.
By default it should be 8000.
Check all these things and then try.
Regards,
Yomesh

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

RFC Adapter not getting data

Hi experts!
I am developing a RFC to File scenario on PI 7.1 EHP1 and ECC 6.0 which is synchronous. Following the Help page Setting Up an RFC Destination for the RFC Adapter I created two destinations. The fist one is a TCP/IP, name RFCDE1COMPANY2, program id BAPI_COMPANY_GETLIST and corresponding gateway host and service I found at SMGW (Parameters). The second one is a Logical with name RFCDE1and reference entry RFCDE1COMPANY2.
At my RFC Sender Adapter I configured the same gateway info and the same program id. After that I tested both destinations and it worked. I created the following report to call the bapi on that destinations::
REPORT ZREP_BAPI_COMPANY_GETLIST.
DATA: company_list TYPE STANDARD TABLE OF BAPI0014_1.
CALL FUNCTION 'BAPI_COMPANY_GETLIST'
IN BACKGROUND TASK
DESTINATION 'RFCDE1'
TABLES
COMPANY_LIST = company_list.
COMMIT WORK.
At SXMB_MONI the request message was processed and the output file generated, but it has only the root tag. At moni the inbound message has no data (company data).
I tested the BAPI_COMPANY_GETLIST at SE37 and there are 149 entries. When I executed this same BAPI with RFC target sys configured to my destination, it didn´t show any data and has an exception called SYSTEM_FAILURE. I think probably the error is on RFC destinations but I can´t figure it out what is wrong.
Best Regards,
Gabriela

Hi experts,
Thank you all for your quick response.
At the TCP/IP Destination there is a button "Unicode Test", according to this test my target system is unicode (character size 2). I changed the option at MDPM&Unicode on that TCP/IP Destination like Madhusudana described. I also selected the checkbutton "Unicode" on sender RFC communication channel.
About the sync/async, I will not use sync async bridge because this scenario can be async. One think that I realized is that when I call my report, I am implicitly calling PI asynchronously and when I call the BAPI directly by the test tool, I am implicitly calling PI synchronously. That is why most part of my tests did not work before.
Now I can see on SXMB_MONI that the scenario worked and the file was generated. But the data are still not being showed on inbound payload. I think something is wrong with my destinations but I can´t figure it out what is.
Ps.: I would prefer to use XI proxies, but this scenario will be configured (not now) on a XI 3.0 with ERP 4.6 C. Now I´m just learning how to handle with RFC Adapter.
Any ideia?
(Points granted)
Thank you and best regards,
Gabriela

RFC Adapter as Sender

Hi Experts,
We have a business scenario wherein I have to execute the RFC function(async) from an ABAP in R/3 and update the data in DB2 tables(async).
I am using RFC as sender(async) and JDBC as receiver(async). I configured/registered the RFC connection in SM59 and used the same program id in RFC sender adapter. I tested the connection in standalone mode, it is working.
The RFC function when I imported will have a request and a response. The data that I require to send to JDBC adapter is in the response. So I tried to use RFC response and created a message interface. Then I used that in my interface mapping and in the sender & receiver agreements. In the message mapping I used response that was imported.
I get an error message saying sender agreement not found. The as per OSS note 730870 I changed the sender agreement to use RFC function as sender interface, I cannot use this function module for my mapping, as it does not contain the response.
Am I doing something wrong. Can somebody show me some direction.

Hi Srinivas ,
If you want to capture the response of an RFC execution in XI and then map this response to another structure(In ur case a JDBC structure) inside XI message mapping , then you will have to use the RFC reciever adapter of XI and NOT the RFC sender adapter.If you use the RFC sender adapter, it means that your SAP system is acting as an RFC CLIENT, what happens is the REQUEST structure in your RFC destination will be converted to RFC-XML by the RFC sender adapter of XI and is available for furthur processing.
But then, If you want to send the RESPONSE structure of an RFC to XI , one way is to execute the RFC in SAP(without passing this thru XI), now you have to pass the result of this RFC execution to XI by assigning it to a request structure of another RFC in your ABAP code and pass it to XI using RFC sender adapter.
If not , you can use a dummy RFC in SAP to send a trigger to XI , execute the actual RFC in XI using RFC reciever adapter , capture the response , map it to ur JDBC structure and you are done.
May be you can give a try on these lines. As for the error , you can chk these threads and see if it helps
com.sap.aii.af.ra.ms.api.DeliveryException
"call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryExceptio
RFC Sender Adapter error " Call to messaging failed"
Thanks
Saravana

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

RFC Sender problem between 46D and RFC adapter

Hi,
I have this simple integration scenario where I want to send data to a archiving system;
SAP -> (tRFC) -> XI -> (MQ) -> BizTalk -> (MQ) Arch.syst.
SAP side ***
A Z-program using a Z func. like;
 CALL FUNCTION 'ZSD_DCF_SEND_TAG'
 IN BACKGROUND TASK
 DESTINATION 'XISYSTEM_TRFC_DCF'
 EXPORTING
 pt_filing_info = gt_filing.
 COMMIT WORK AND WAIT.
XI side ***
Both IR and ID is configured correctly, in the development environment everything works just great. I have created a test program where I can define how many calls I will do, looping over the func. call with a commit inside the loop - 500 or more msgs are ok.
The integration scenario is transported to quality enviroment using CMS, and the RFC sender comm.ch. is configured accordingly.
The problem in quality ***
When sending just 1 msg, everything is just fine, message received and delivered to MQ.
When sending >= 2 msgs, the 1 msg is always ok, BUT all others fails due to the following from Adapter monitor;
RFC_HISTORY
- Error: 2006-01-19 10:55:18 CET: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'RFCSender_XI0002' (02d4d30de3593874942ed0659add0827, party '', schema 'TechnicalSystem', identifier 'Q93#120')
- OK: 2006-01-19 10:55:17 CET: Message processed for interface ZSD_DCF_SEND_TAG
My sending system is Q93 CLI 505 so I can understand the error, BUT I cannot understand why the RFC adapter is saying the TechnicalSystem is Q93#120 - it should be Q93#505. My Q XI has client 120...
It seems to me that the RFC adapter is kind of confused about the sender..
I have created a OSS message and SAP has looged on and looked into it with both a XI expert and RFC expert without being able to answer - all is configured correctly.
- The SLD config. for bus.system Q93 is ok -
- The bus.system in ID is showing correct vaues for
Adapter Specific Identifiers (SID Q93, client 505)
- Both Dev. and Qual. environment are running on XI 3.0 SP 14 latest patch, RFC component version on the SAP side is identical between dev. and qual. SAP systems
- It doesn't matter which gw I use (Q93 gw or XI gw), the error is persistent
- It doesn't matter if I increase initial conn, max conn.
I have also tried to use qRFC instead, but with the same result.
Anyone using tRFC for asynch. communication from SAP to XI seeing something similar?
Meanwhile, I will do RFC trace on GW and RFC Adapter on AE....
Please, do not say SP15, oss msg for FAQ RFC adapter or links to RFCAdapter config....
best regards
Torstein

Hi,
SAP Note 730870 FAQ: XI 3.0 RfcAdapter Q.no 15
Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?
A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".
- Give correct appserver and gateway service details in XI.
- Open the service holding the RFC adapter you are trying to use. On the top menu, goto Service -> Adapter Specific Identifiers..
Regards,
Prateek

RFC 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

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

Sender RFC Adapter AND Rec. File Adapter

Hi
Workflow of my scenario is like this :
SAP R/3 ---> Sender RFC Adapter ---> XI Server -
> Rec. File Adapter -
> Legacy System
I am using Async Inbound interface for this as I dont need any response back & I just need to create file.
I am just picking some data from BAPI & creating a file on a folder in Legacy System.
Now during execution, file is getting created but I am getting dump on SAP R/3 and even when I am using Async communication, response is coming back from Legacy Business System ( service ) & giving an error " No Mapping Program Found " in sxmb_moni.
Kindly suggest how can I avoid getting response from Legacy System. Pls. take note again I am using Async Inbound Interface.
Regards
- Lalit -

Hi Lalit,
When your RFC is called from R/3 by default it would be in Sync mode. When this is in Sync mode it obviously will expect a response and where as in your scenario XI dose'nt give any response and there is no mapping for that and I think that is the reason you are getting that error.
So when your Sender RFC is triggered it will like this in ABAP
CALL Function "Function Name" <SM59 Destination>
and this is Sync call. To make it Async i should be
CALL Function "Function Name" IN BACKGROUND TASK <SM59 Destination>
Hoep this helps
Thanks,
Prakash

RFC-Adapter, order not put in

Hi,
my scenario File -> XI -> R/3-Backend will be precessed successful. The Response Payload have the items and in detail of messages appears succes status
"RFC adapter received an asynchronous message. Attempting to send tRFC for BAPI_PO_CREATE with TID XIfr1OyAQS4Td..."
But in R/3 the order ísn't put on.
Does one of you have an idea why???????
Thanks
Hüsniye

Try this code. This works perfectly for us:
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
EXPORTING
 SALESDOCUMENTIN = SALESDOCUMENTIN
 ORDER_HEADER_IN = ORDER_HEADER_IN
 ORDER_HEADER_INX = ORDER_HEADER_INX
 SENDER = SENDER
 BINARY_RELATIONSHIPTYPE = BINARY_RELATIONSHIPTYPE
 INT_NUMBER_ASSIGNMENT = INT_NUMBER_ASSIGNMENT
 BEHAVE_WHEN_ERROR = BEHAVE_WHEN_ERROR
 LOGIC_SWITCH = LOGIC_SWITCH
 TESTRUN = TESTRUN
 CONVERT = CONVERT
IMPORTING
 SALESDOCUMENT = SALESDOCUMENT
TABLES
 RETURN = RETURN
 ORDER_ITEMS_IN = ORDER_ITEMS_IN
 ORDER_ITEMS_INX = ORDER_ITEMS_INX
 ORDER_PARTNERS = ORDER_PARTNERS
 ORDER_SCHEDULES_IN = ORDER_SCHEDULES_IN
 ORDER_SCHEDULES_INX = ORDER_SCHEDULES_INX
 ORDER_CONDITIONS_IN = ORDER_CONDITIONS_IN
 ORDER_CONDITIONS_INX = ORDER_CONDITIONS_INX
 ORDER_CFGS_REF = ORDER_CFGS_REF
 ORDER_CFGS_INST = ORDER_CFGS_INST
 ORDER_CFGS_PART_OF = ORDER_CFGS_PART_OF
 ORDER_CFGS_VALUE = ORDER_CFGS_VALUE
 ORDER_CFGS_BLOB = ORDER_CFGS_BLOB
 ORDER_CFGS_VK = ORDER_CFGS_VK
 ORDER_CFGS_REFINST = ORDER_CFGS_REFINST
 ORDER_CCARD = ORDER_CCARD
 ORDER_TEXT = ORDER_TEXT
 ORDER_KEYS = ORDER_KEYS
 EXTENSIONIN = EXTENSIONIN
 PARTNERADDRESSES = PARTNERADDRESSES
**checking if the BAPI returned some errors*****
LOOP AT return ASSIGNING <bapiret>.
 IF <bapiret>-type = 'E' OR <bapiret>-type = 'A'.
 success = space.
 EXIT.
 ENDIF.
ENDLOOP.
IF success = 'X'.
****in case of success commit the BAPI*********
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 wait = 'X'
 IMPORTING
 return = wa_bapiret.
ELSE.
 ROLLBACK WORK.
 ENDIF.
Also you need to pass on the information for "inx" structures. What I mean is , if you are sending data to field REF_1 in header_in, then ref_1 in header_inx needs to be passed witha value of 'X'.
The update flag in inx structure needs to be 'C' for create.
If have items in your sales order, then you have to pass the values for item_in and item_inx. Additionally you need to pass values for schedule lines also.
Hope this helps.
Thanks,
Bhaskar

Sender RFC adapter - Tight coupling to an SAP client

Hi ,
We are using a sender RFC adapter to receive a RFC request from SAP , process the request in XI and then send back a response to SAP.
Our requirement is that , this request may come from different SAP clients(client 100, 130 , 200 etc). Looks like RFC adapter configured under a Business System in XI cannot listen to calls from multiple clients and works for only one client. We get dumps in SAP when invoking this RFC from other clients.
Also i hear that the same program id cannot be used in two different RFC sender adapters, meaning i have to create a different RFC destination , create a different program id for each client in SAP.
Is there a way around for this issue ?
Thanks
Saravana

Hi Saravana,
you may try a little workaround:
configure your rfc adapter only with client 100
and try invoking RFC from clients: 130 , 200
on the client 100 first (with a dummy RFC on client 100)
and then from this dummy RFC on client 100 you can start your standard RFC with your rfc adapter
don't know any other way:)
Regards,
michal

Problem with sender RFC adapter

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

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

File- XI- RFC (Error: Received HTTP response code 500..)

Hi,
I am working on File->XI->RFC scenario, getting Processed Successfully status in "SXI_MONITOR".
But Data is not posted in SAP R/3. I check Runtime Workbench Getting following Error in one step.
Can any one help me in analyzing the error.....??????
2006-06-09 14:36:32 Success output 1149888992513 Channel WEBMETHOD_SENDER_SOAPFMTEST: Send binary file "/usr/sap/transx42/data/xi_input.xml". Size 175 with QoS EO
2006-06-09 14:36:38 Success output 1149888998592 Application attempting to send an XI message asynchronously using connection AFW.
2006-06-09 14:36:39 Success output 1149888999757 Trying to put the message into the send queue.
2006-06-09 14:36:40 Success output 1149889000823 Message successfully put into the queue.
2006-06-09 14:36:40 Success output 1149889000824 The application sent the message asynchronously using connection AFW. Returning to application.
2006-06-09 14:36:41 Success SAPEngine_System_Thread[impl:5]_12 1149889001577 The message was successfully retrieved from the send queue.
2006-06-09 14:36:41 Success output 1149889001591 File "/usr/sap/transx42/data/xi_input.xml" deleted after processing
2006-06-09 14:36:41 Success SAPEngine_System_Thread[impl:5]_12 1149889001745 The message status set to DLNG.
2006-06-09 14:37:47 Error SAPEngine_System_Thread[impl:5]_12 1149889067522 Transmitting the message to endpoint http://SAPR3001.bently.com:8042/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500..
2006-06-09 14:37:47 Success SAPEngine_System_Thread[impl:5]_12 1149889067585 The asynchronous message was successfully scheduled to be delivered at Fri Jun 09 14:42:47 PDT 2006.
2006-06-09 14:37:47 Success SAPEngine_System_Thread[impl:5]_12 1149889067695 The message status set to WAIT.
2006-06-09 14:42:47 Success SAPEngine_System_Thread[impl:5]_9 1149889367587 Retrying to send message. Retry: 1
2006-06-09 14:42:47 Success SAPEngine_System_Thread[impl:5]_9 1149889367587 The message was successfully retrieved from the send queue.
2006-06-09 14:42:47 Success SAPEngine_System_Thread[impl:5]_9 1149889367643 The message status set to DLNG.
2006-06-09 14:42:48 Success SAPEngine_System_Thread[impl:5]_9 1149889368435 The message was successfully transmitted to endpoint http://SAPR3001.bently.com:8042/sap/xi/engine?type=entry using connection AFW.
2006-06-09 14:42:48 Success SAPEngine_System_Thread[impl:5]_9 1149889368471 The message status set to DLVD.
2006-06-09 14:42:48 Success SAPEngine_System_Thread[impl:5]_9 1149889368472 The message was successfully delivered.
Thanks & Regards

Hi Umesh,
I think, the reason is because of huge number messages ..
Also just go to RFC adapter, activate the adapter,refresh the cache and try it..
following guide will help you to solve problem~
https://websmp103.sap-ag.de/~sapdownload/011000358700002757652005E/HowtoMintorAF.pdf
Just refresh the cache-The following guide will help you on that~
https://websmp101.sap-ag.de/~sapidb/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf
Refer these SAP notes- 807000,803145
(some hints)
Regards,
Moorthy

XI RFC Adapter 4705: Wrong response

Similar Messages

Maybe you are looking for