Receiver XI Adapter: Error 401

Hi All,
I am getting the below error in a file to proxy(XI Adapter) scenario. What is the role that i need to add to the user that i am using on the XI Adapter?
"HTTP response contains status code 401 with the
description User not authorized for message
processing"
Thank you in Advance,
D

Hi Danny,
Please see very important link:-
http://en.wikipedia.org/wiki/List_of_HTTP_status_codes
[Reward points for useful reply.]
Vishal

Similar Messages

Receiver SOAP Adapter error

Hi All,
         I am getting this response error message in my receiver SOAP Adapter while invoking a synchronous webservice.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <ProcessMessageResponse xmlns="http://Sleek.Integrator.Messaging" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ProcessMessageResult>Value cannot be null. Parameter name: Request string is a null reference.</ProcessMessageResult>
</ProcessMessageResponse>
Thx in advance
Ravijeet

Hi All,
         I am still getting the same error value is null. I am not able to track what could be the cause of the error. If I am taking the message from SXMB_MONI and using it in a client tool it is successfully calling the webservice.
Do we need to explicitly mention in some configuration that content type is soap/xml. SOAP header is omitting the content type or is not specifying "soap/xml" as the content type.
I am interacting with a WAF websevice, is there any compatibilty issue with Windows Webservice and SAP XI?
Also what should I pick as the SOAP Action from this wsdl file definition
<wsdl:portType name="IMessageProcessor">
          <wsdl:operation name="ProcessMessage">
               <wsdl:input message="tns:IMessageProcessor_ProcessMessage_InputMessage" wsaw:Action="XXX.Messaging/ProcessMessage"/>
               <wsdl:output message="tns:IMessageProcessor_ProcessMessage_OutputMessage" wsaw:Action="XXX.Messaging/ProcessMessageResponse"/>
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:service name="MessageProcessor">
          <wsdl:port name="BasicHttpBinding_IMessageProcessor" binding="i0:BasicHttpBinding_IMessageProcessor">
               <soap:address location="http://XXX.com/cardax/provisioningservice"/>
          </wsdl:port>
Thx in advance
Ravijeet

Receiver File Adapter error

Hi all,
I am trying to convert the XML to Plain file in receiver file adapter. I am using module - StrictXml2PlainBean
My target structure is -
<MT_Name>
    <records>
        <Header>
        </Header>
        <Item>
        </Item>
    </records>
</MT_Name>
<Header> and <Item> are at same level.
When I use --
1. Header.fieldSeparator = ,
2. Item.fieldSeparator = ,
3. recordTypes = Header,Item
Then I get this error -
Message processing failed. Cause: com.sap.aii.af.app.modules.conversion.xml2plain.ConversionException: Invalid structure name encountered during conversion: records at XML element MT_Name,records
When I use --
1. records.fieldSeparator = ,
2. singleRecordType = records
Then I get this error -
Message processing failed. Cause: com.sap.aii.af.app.modules.conversion.xml2plain.ConversionException: The element nesting level for the structure MT_Name is too deep (reference: 3 levels, found: 4 levels) at XML element MT_Name,records,Header,Item
To add more details to the scenario, multiple records can be generated but one record will have only one Header, with multiple Items.
Any help in this regard will be highly appreciated.
Thanks,
Abhi

Hi Abhi,
Here you go....
For your target structure as:
<MT_Name>
<records>
<Header>
</Header>
<Item>
</Item>
</records>
</MT_Name>
Where I have assumed that <Header> and <Item> are at same level.
DO NOT use any Module just simply configure the receiver channel as below:
In the file Receiver Channel
Recordset Structure = Header,Item
Name                                                                    Value
Header.fieldSeparator                                             ,
Item.fieldSeparator                                                  ,
I have tried this and it works.
Let me know if you are facing any issues.
Cheers
Dhwani

Receiver file adapter error for special char.

I am using MTB in my receiver file adapter. I am getting a special character from source system at end of the string. How to resolve this type of error u2013 please advice.
This error is not coming for every message.
Error message:
Column value xxxx Â too long - must stop, probably configuration error in file adapter
Thanks
Vick

Hi,
Itu2019s basically IDOC to file scenario.
This error is coming for name field.
What I am thinking at this stage to do changes in MTB by define parameters like (NameA.enclosureConversion)

Receiver Mail adapter errors

I am trying to configure a receiver mail adapter..
Our system is using microsoft exchange server and i specified the following,
URL: Microsoft Exchange Server
and I get the following exception in Adapter monitoring,
Mail: error occured: com.sap.aii.af.mp.module.ModuleException
Has anybody encountered this error and if so how should this be resolved?

Hi
<i>>>Our system is using microsoft exchange server</i>
Ok ur company is using Microsoft Exchange Server, then r u sure the name of ur server is also Microsoft Exchange Server becoz in our company we hav a specific name of our Microsoft Exchange Server.
<i>>>URL: Microsoft Exchange Server</i>
The URL shd b something like this
<b>URL</b>: smtp://<b>name of Microsoft Exchange Server</b>
Hope it helps.
Regards
Arpit Seth

Receiver XI adapter error

Hi All,
I have configured the Receiver XI Adapter which i will use to send the
data to the J2SE adapter.
The XI adapter configuration is :-->
Transport Protocol-- HTTPS
Message Protocol- Xi3.0
Adapter Engine- Intergration Server
Addressing type-- URL Address
Target Host- host Name
Service number- Port i.e 8202
Path -- /file/if216at3
The J2SE Adapter receiver configuration:-->
File adapter java class
classname=com.sap.aii.messaging.adapter.ModuleXMB2File
version=30
mode=XMB2FILE
##Adress for XMB endpoint
XI.httpPort=8212
XI.httpService=/file/if216at3
##File Adapter specific parameters
file.createDir=1
file.targetDir=C:/XI/Inbox
file.targetFilename=IF216AT3*.txt
file.writeMode=new
#file.writeMode=overwrite
file.writeMode=addTimeStamp
file.counterMode=immediately
#file.counterMode=afterFirst
file.counterSeparator=_
file.counterFormat=00000
file.counterStep=1
I am getting the error :--
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>404</SAP:P1>
<SAP:P2>Not Found</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 404 with the description Not Found Error when sending by HTTP (error code: 404, error text: Not Found)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Some more checks
file.targetFilename=IF216AT3*.txt -> can we use wild charcter to define a file name ?
fi
le.writeMode=new ->>????? i dun think we have this parameter *new
(#file.writeMode=overwrite / file.writeMode=addTimeStamp / ) ---> use one
(#file.counterMode=afterFirst, file.counterSeparator=_ ,file.counterFormat=00000
file.counterStep=1)
You are using write mode = overwrite then why is File.counterMode set here >?
File.countMode should only be set if you have file.writeMode=addCounter
for further reference go through these
http://help.sap.com/saphelp_nw04/helpdata/en/6f/246b3de666930fe10000000a114084/frameset.htm
<b>Cheers,
*RAJ*
*REWARD POINTS IF FOUND USEFULL*</b>

Call Adapter Error - 401 Unauthorized

Hi,
We are using Multi Mapping where it splits 1 message into n messages. The n messages split by this scenario in trun calls another scenario configured in the same PI server using SOAP Adapter.
The called scenario is SOAP --> Siebel using iWay Adapter.
When the number of messages split are huge in order of thousands, the server is going for a toss and the called scenaio is failing at Call Adapter Step in IE with HTTP Error 401 Unauthorized. Few of the messages manage to pass successfully.
Anticipating your valuable inputs.
Thanks.
Regards,
Sudharshan N A

Hi Sudharshan,
There can be different reasons for getting HTTP 401: Unauthorized error. As you said, few of the messages are being passed to the called application, I would request you to check the scalability of the Seibel Server.
Also if you are using a connections from a connection pool, then it may be that the pool itself is getting exhausted, though mostly we get Socket exception/Connection Exception/IO Errors in these cases.
The other reasons can be that the user you are using to connect Seibel dont have enough permissions. But it is ruled out as you said some messages have been processed.
If the Seibel server is SSL enabled, and your PI doesn't have any certificate configured, then also you may get such errors.
Regards,
Sugata

Receiver Mail adapter Error

HI All
   i    am doing   a   scenario     SFTP    to mail adapter,   i am sending a    file    to    SFTP ADAPTER and   Mail adapter   send the   mail to    clint,   i am   using java mapping ,   i have checked the message in    RWB mesage is    fail   in mail adapte,
   ERROR :   Message processing failed. Cause: java.lang.Exception: java.io.IOException: server does not support PLAIN or LOGIN authentication
anyone suggest me     soloution?

Hi Pankaj,
Remove your mail server user id and password and keep authentication mode as Plain and try in mail adapter configuration.
You can try accessing ID from within IR via menu options or via a direct URL.
Thanks,

Receiver Mail Adapter Error ( Dynamic mail address to be used)

Hi EveryBody,
I am getting an error in the RWB (Communication Channel Monitoring) as Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error: invalid XIMailAdapter channel 'a089879fd0b63a4b92ca72d4a4af2ec4'.Mail is not send to the receiver.I have tried using USE MAIL PACKAGE as base64 and NONE.
Can somebody help me out in the configuration.

Hi,
have u refered the below weblog of michal:
Mail Adapter (XI) - how to implement dynamic mail address
/people/michal.krawczyk2/blog/2005/03/07/mail-adapter-xi--how-to-implement-dynamic-mail-address
Thnx
Chirag gohil.

Receiver XI adapter error :HTTP Status Code 200 during Reponse Parsing

Hi Exeprts,
My Scenario is mail to ABAP proxy , I have got the bellow error in moni while testing my secnario .
Please help me reslove this .
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">OK_BUT_NO_XI_MESSAGE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP Status Code 200 Received But Error During Response Parsing: No XI Response Received XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Regards
Upendra

Hi Mark ,
No error message in attachement . only it daisplay the following information
SAP Library
SAP Library contains the complete documentation for SAP NetWeaver Application Server Java. You can access it by choosing SAP NetWeaver.
      SAP NetWeaver Administrator
A powerful administration, configuration and monitoring tool, which bundles key administrative tasks to keep your SAP NetWeaver system landscape running. SAP NetWeaver Administrator can be used in a central or local scenario. Here you access the local NetWeaver Administrator.
    System Information
System information provides administrators with an overview of the system configuration and its state. It shows all of the system's instances and processes, their current state and important parameters (such as ports) that may be required for support cases, as well as the versions of the components installed.
      Services Registry
The Services Registry is a UDDI based registry that contains definitions of enterprise services and references to their metadata.
   User Management
The user management administration console provides administrators with the functions they need to manage users, groups, roles, and user-related data in the User Management Engine (UME). Users without administrator permissions can use it to change their user profile.
      UDDI Client
The UDDI client provides query and publishing functions for UDDI entities to any UDDI compliant registry.
   Web Services Navigator
Web Services Navigator is a tool that gives you a short overview of a specific Web service based on its WSDL, and enables you to test your Web service by creating and sending a client request to the real end point.
      Web Dynpro
Web Dynpro is a User Interface technology available within the SAP NetWeaver Developer Studio.
Various Web Dynpro tools provide administrators and application developers with performance measurement and application administration capabilities. The Web Dynpro runtime is already deployed.
Regards
Upendra

Receive File Adapter - Error in CallSAPAdapter Name not known

Using xml to File Adapter. Just want to store the xml file somewhere ie on XI Server in folder E:\usr\sap\interface\XMLfiles
Getting error in Adapter Engine - Exception caught by adapter framework: Object not found in lookup of CallSAPAdapter.
Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Object not found in lookup of CallSAPAdapter.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of CallSAPAdapter..
Receiver Adapter configured to receive file write a .tmp version no conversion so set type to Binary.
I can see the Communication Channel in the monitor green.
Any ideas to find the problem
thanks,

I tried changing the communication channel as suggested with no further success. I have viewed the LogViewer on the server in cluster->server->logs defaultTrace.trc and com.sap.xi -> xi.log with no more information available.
So is it that I cannot do a simple XML send to file receiver and leave its content unchanged?
My test message payload was of the order
<?xml version="1.0"?><LIST><S_STX><C_STDS><D_STDS1>... with all the data in.
Adapter type = file
Receiver
Transport Protocol = File System (NFS)
Message Protocol = File
Adapter Engine = Integration Server
Target Directory = E:/usr/sap/Interfaces/XMLFiles (and tried it with /usr/sap/interface/XMLFiles)
Create filedirectory = ticked
Filename filename.xml
File Construction Mode = add timestamp
Write Mode = use temporary file
Temporary filename scheme = filename.tmp
Filetype = Binary
Module Tab
1 localejbs/CallSAPAdapter Local Enterprise Bean 0
and thats it.
On testing from the Integration Engine it reaches the Adapter Engine and reports the error as stated in my first post.
The message data is of the construct
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SOAP:Header>
- <sap:Main xmlns:sap="http://sap.com/xi/XI/Message/30" versionMajor="3" versionMinor="0" SOAP:mustUnderstand="1" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<sap:MessageClass>ApplicationMessage</sap:MessageClass>
<sap:ProcessingMode>asynchronous</sap:ProcessingMode>
<sap:MessageId>09c99665-f3cf-d247-993b-8cb46c37d820</sap:MessageId>
<sap:TimeSent>2007-09-19T16:42:31Z</sap:TimeSent>
- <sap:Sender>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty">AS2</sap:Party>
<sap:Service>XMLFILE</sap:Service>
</sap:Sender>
- <sap:Receiver>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty">MyCompany</sap:Party>
<sap:Service>XMLFILE</sap:Service>
</sap:Receiver>
<sap:Interface namespace="http://warburtons.com/genhdr">MI_XMLFILE_V3</sap:Interface>
</sap:Main>
- <sap:ReliableMessaging xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:QualityOfService>ExactlyOnce</sap:QualityOfService>
</sap:ReliableMessaging>
- <sap:Diagnostic xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:TraceLevel>Information</sap:TraceLevel>
<sap:Logging>Off</sap:Logging>
</sap:Diagnostic>
- <sap:HopList xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
- <sap:Hop timeStamp="2007-09-19T16:42:31Z" wasRead="false">
<sap:Engine type="IS">is.00.srvsapxidev</sap:Engine>
<sap:Adapter namespace="http://sap.com/xi/XI/System">XI</sap:Adapter>
<sap:MessageId>09c99665-f3cf-d247-993b-8cb46c37d820</sap:MessageId>
- <sap:Branch>
<sap:MessageId>707ecbbd-a474-514d-b731-f4003c38c4df</sap:MessageId>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty">ASD</sap:Party>
<sap:Service>IP_I_XMLFILE_Collect</sap:Service>
</sap:Branch>
- <sap:Branch>
<sap:MessageId>09c99665-f3cf-d247-993b-8cb46c37d820</sap:MessageId>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty">MyCompany</sap:Party>
<sap:Service>XMLFILE</sap:Service>
</sap:Branch>
<sap:Info>3.0</sap:Info>
</sap:Hop>
- <sap:Hop timeStamp="2007-09-19T16:44:56Z" wasRead="false">
<sap:Engine type="AE">af.xid.srvsapxidev</sap:Engine>
<sap:Adapter namespace="http://sap.com/xi/XI/System">XIRA</sap:Adapter>
<sap:MessageId>09c99665-f3cf-d247-993b-8cb46c37d820</sap:MessageId>
</sap:Hop>
</sap:HopList>
</SOAP:Header>
- <SOAP:Body>
- <sap:Manifest xmlns:sap="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <sap:Payload xlink:type="simple" xlink:href="cid:[email protected]">
<sap:Name>PayloadName</sap:Name>
<sap:Description>PayloadDescription</sap:Description>
<sap:Type>Application</sap:Type>
</sap:Payload>
</sap:Manifest>
</SOAP:Body>
</SOAP:Envelope>
The Payload is
<?xml version="1.0" ?>
- <LIST>
etc
Message status
2007-09-19 17:44:56 Success Message successfully received by messaging system. Profile: XI URL: http://srvsapxidev:50000/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
2007-09-19 17:44:56 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2007-09-19 17:44:56 Success Message successfully put into the queue.
2007-09-19 17:44:56 Success The message was successfully retrieved from the receive queue.
2007-09-19 17:44:56 Success The message status set to DLNG.
2007-09-19 17:44:56 Success Delivering to channel: CC_toMyCompany_XMLFILE
2007-09-19 17:44:56 Error Exception caught by adapter framework: Object not found in lookup of CallSAPAdapter.
2007-09-19 17:44:56 Error Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Object not found in lookup of CallSAPAdapter.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of CallSAPAdapter..
2007-09-19 17:44:56 Success The asynchronous message was successfully scheduled to be delivered at Wed Sep 19 17:49:56 BST 2007.
2007-09-19 17:44:56 Success The message status set to WAIT.
Now I have been reading all the documentation available and forum questions in this area but there is a lot of information but not quite for what I am currently trying to do. I need to preserve the xml file as xml for further processing. This is just a resting place for the file as I am trying to cut down a long running (over a day) collect BPM scenario by collecting the files in the directory then triggering the collect scenario to read in the files from this directory and perform all the processing and mapping in one chunk of short time. (But that is another story)
Any more suggestions appreciated could the SAPCallAdapter not be where I think it is? Does my directory and filename case have to be exact lower and upper case. (I will test this tomorrow)...and let you know if any difference and continue to read the links put on by the other person who answered.
thanks,

Receiver mail adapter error -mail not going to other domain users

in xi this error is coming in mail adapter -
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: server not responding OK to MAIL FROM; Domain of sender address XXXat d rate of XX.XX.com does not resolve
any resolution.upto yday everything was working fine.i crosschecked scot settings they r ok.

Hii,
In SXMB_MONI , its showing successful.
In RWB , its showing error
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: server not responding OK to MAIL FROM; Domain of sender address XXXX does not resolve.
I checked mail id is perfect and settings r ok.
Pls let me know wat else we can check and rectify it.

Sender SOAP adapter error 401

Hello All,
Here the scenario is SOAP -> XI -> SAP ECC.
When the webservice is seding the message I am getting error in Sender SOAP channel.
Message is not going to Integration Engine.
Its failing with 401Un Authorized in sender soap adapter channel.My sender soap channel is plain channel with no authentication check and certificated etc.When webservice is seding request to XI its sending wit some usernmae which was there on XI box.I am facing this issue in Quality Env. The same is working fine in Dev box.
Please give me the list of points that I need to check here.
Thanks,
Regards,
Naresh

Hi,
I am facing this issue in Quality Env. The same is working fine in Dev box.
Once the scenario is transported from Dev to QA the location where the Webservice is hosted will also change
Hence you will have to change the target URL .....just the HostName / IP address and the port for all the webservices (that you transported to QA)
Once you are in QA and with no change to the URL the sender (which I suppose is also in QA env) will be still trying to ping the same old Dev-URL....in such situation the sender is bound to get UnAuthorized error....
So one in all change the URL in your WebService to point to QA and then test....
Same logic applicable to QA --> PROD
Regards,
Abhishek.

Receiver SOAP Adapter : Error Connection Refused (errno: 239)

Hello
I am testing a simple scenario using SOAP Adapter. I am getting the following error.
com.sap.aii.af.ra.ms.api.DeliveryException: Connection refused (errno:239)
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Connection refused (errno:239)</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can you please tell me what could be the error for the following scenario.
Best Regards,
Kiran

Hi Venkat,
We are actually not using the sender comm channel
http://<server>:<port>/ sap/xi/engine?type=entry&version=3.0&Sender.Party=<party name>&Sender.Service=<>&Interface=<namespace>^<interface>
This stated endpoint is fine there is no error with it.
Thanks.
Kiran

Receiver RFC Adapter Error

Hi All,
I have a file to RFC scenario. I keep getting the below error: Any Ideas?
Danny,
Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.af.rfc.util.bapi.BapiException: Parameter with name RETURN not found.: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.af.rfc.util.bapi.BapiException: Parameter with name RETURN not found..

is this BAPI an SYNC one
check this link
RFC adapter Call BAPI error
Re: Invoice Not getting posted

Receiver XI Adapter: Error 401

Similar Messages

Maybe you are looking for