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

Similar Messages

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

XI and RFC adapter

Hi
The RFC Adapter configuration has been done successfully and the adapter starts up successfully.
In our scenario, we attempt to receive an xml message from my local machine through a file adapter, and pass this along to the RFC Outbound adapter to execute a RFC on the CRM box.
The following error message is encountered in the XI monitoring tool.
==============================================================================================================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="connection closed (no data)" p2="" p3="" p4="">RFC_ADAPTER.SYSTEM_FAILURE_OUTBOUND</SAP:Code>
<SAP:Text language="EN">System error when calling the outbound RFC adapter (connection closed (no data))</SAP:Text>
</SAP:ErrorHeader>
===================================================================================================
I then stop the RFC adapter and attempt the scenario again. I get the following error message in XI monitoring tool.
================================================================================================================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="Exception in handleRequest of server Xmb2RfcService: java.lang.Exception: Bean n" p2="" p3="" p4="">RFC_ADAPTER.SYSTEM_FAILURE_OUTBOUND</SAP:Code>
<SAP:Text language="EN">System error when calling the outbound RFC adapter (Exception in handleRequest of server Xmb2RfcService: java.lang.Exception: Bean n)</SAP:Text>
</SAP:ErrorHeader>
==================================================================================================================

Hi Eduardo ,
Please check wether the following steps are done in BPM:
1.Async Recieve
A.Properties :
Please set the following
Message:Message 1
Mode:asynchronous
B.Container Data :
Declare Message 1 as asynchronous abstract interface with message type of outbound interface(File Structure).
2.Sync Send
Pre-Requisite:
Copy the inbound Syncronous Interface to Sync_interface_abstract by changing the direction in the message interface of Interface object in the Integration Repository.
A.Properties
Mode:Synchronous
Request:Message 1
Response:Message 2
Syncronous Interface:Sync_interface_abstract
Recievers From :Send Context
B.Container Data:
Message 2 should be declared as the asynchronous message interface with Response message type in inbound interface(Rec Syst Interface).
3.Async send
A.Properties:
Mode:Asynchronous
Message:Message 2
Acknowledgment:None
Recievers From :Send Context
Integration directory has to be configured to send data forth and back to BPM.
1.Send MESSAGE From Outbound interface to BPM.
OutBound and Abstract Interface needs to be mapped in the interface determination and Abstract interface has to be binded to Business Process Name in the repository.
Outbound->Your OutBound Interface(File Interface)
Abstract->Message 1
Reciever Service-> Your Business Process Name
2.Send MESSAGE From BPM to Inbound interface.
Abstract and Inbound interface needs to be mapped in the interface determination and Abstract Interface has to be binded to the Receiver Service/Business System.
Abstract->Message 1
Inbound->Your Inbound Interface(RFC)
Reciever Service-> RFC SYSTEM(SAP)
These are the general steps to follow for Async/sync pattern.
Please let me know if all the steps are configured.

RFC adapter installation in SAP XI 2.0

HI all,
Can any one inform me how to install outbound rfc adapter in sap xi 2.0. In tech_adapter directory i didnot find any batch file to install rfc adapter whereas installation batch files are available for file,jdbc,soap and jms adapters. Any help is highly appreciated.
Rgds,
Ram Sri

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

Outbound RFC to file: Received HTTP response code 500

hello:
i am doing outbound rfc from ecc to other system using PI and I get the below error in the PI.
I am on PI 7.0 and looked at the RFC destiantions in ECC and all look good.
The registered program in TCP/IP RFC destination was tested and looks fine .
I checked the SMICM in PI running at port 8000 and it looks file and also i checked the SXMB_ADM Interation configuration in PI which looks good too .
Even the PI integration engine is restarted . i am sure its in PI and I am hoping its related to user in PI -adapter frame work user XIAFUSER?
can you please let me know how to fix the below issue ..
"Transmitting the message to endpoint http://HGSGXI50:8000/sap/xi/engine?type=entry using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Internal Server Error"
thanks,

HI
for the error com.sap.aii.af.ra.ms.api.RecoverableException Received HTTP response code 500 Internal Server Error"
HTTP 500 can be any problem at receiver side. Are you sure, that the payload fits to the receiver requirements
Please refer this thread answered by Stefan Grube
Plain HTTP adapter error
check the similar thread HTTP server code 500 reason Internal Server Error

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

RFC adapter...How it handles multiple calls...

Hi folks
Basic doc'tation on RFC adapter states...qRFC is not supported..Agreed..
I have a scenario where I need to dump lot of transactions from a flat file to an RFC.
I have split the single structure by 1:n mapping(multi) and pushed each message using a Loop(For-each/Par-For-each) to RFC function..
Now question here..Is this a good approach to invoking RFC's(I find response times to be pretty slow on my server upto 20 secs for each RFC call). Cant I parallely execute all the messages by calling the RFC on SRM systems.(PAR for each loop has a limit of 999 loops)..Is there any other option you can suggest for this scene.?

chk this link
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
there is a recommendation on when to use parForEach. From what i understand , parForEach is helpful if u intend to send "One" Message to multiple receiver systems and intend to handle the responses in different context.I beleive it won't help if u send "different" messages to the same receiver system.
One more approach , i can think of is to make a Jco call from your "Message Mapping" itself using User defined functions instead of "configuring an RFC adapter" and "calling it in ccBPM". The below link should help on this.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/how to perform sap data lookups within xi mappings.
Good Luck
cheers
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

How to limit the response rows while invoking a stored procedure from OSB 10gR3

Dear Experts,
I am trying to limit the response while invoking a stored procedure from OSB via DB adapter.
Here the stored procedure returns cursors as response. I tried using the MaxTransactionSize propertiy (which is used for polling the database option in DB adapter).
We are investigating the ways to protect the application from response containing huge number of rows.
Is there any way to restrict the number of rows returned in each and every cursor while invoking the stored procedure via DB adapter?
Thanks
Ram

Hi James ,
I want to know how to run stored procedure using jca adapter in OSB11g.
I am new to stored prcoedure,will be great if you could share some example on it as above.
Req: Single input xml will be posted on queue ,need to perform 3 DB operation (with same input):
1.Insert operation to insert master table contents.
2.select the primary key column value from master table for the last inserted record.
3.Need to insert primary key column value + other fields frm same xml file to child table.
Pls assist me on how to create a simple stored procedure and to run the same with OSB 11g.I am familiar with creation of DB adapter using Jdeveloper,we have option to perform insert and to call stored procedure here,will it be useful for this scenario?
Edited by: Anitha R on Nov 21, 2010 9:30 PM

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 Adapter not Call

Hello Friends,
I am working on XI 2.0
My Scenario is
IDOC --> XI --> RFC Adapter --> R/3 System
I am configuring the RFC adapter for the SAP system.
But when I am able to try to call using the Integration Engine its not call the RFC adapter.
I define the end point as
RFC Adapter
(X) Load Balancing Deactivated
Application Server -- <host name>
System Number -- 00
When I run the scenario it show me in the sm58 transaction as
Connection Close (no Data)
And in the SXMB_MONI Transaction it shows
A. Status as Green Flag means Message schedule on outbound side.
So can you please identify and suggest me the solution or what else configuration is required.
Thanks & Regards,
Gaurav Jain

try to register all queues in SXMB_ADM -> Manage queues.
I think that should help you solve the issue.

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

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

Outbound RFC Adapter - Limit in Response

Similar Messages

Maybe you are looking for