Unknown receiver adapter (name = SOAP)

Hi,
I have an IDOC-XI-SOAP(Web service) scenario which is resulting in the following error
<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">ADAPTER_NAME_INVALID</SAP:Code>
<SAP:P1>SOAP</SAP:P1>
<SAP:P2>PLSRV_CALL_ADAPTER</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unknown receiver adapter (name = SOAP)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any pointers..?

hi Siru TK
Check with thread
receiver soap error
Error in SOAP synchronus request.
Thanks!!

Similar Messages

Unknown outbound adapter (name = SOAP)

Hi folks,
I am working on a PROXY --> PI --> SOAP scenario. I get this error in PI'S SXMB_MONI. How to resolve this issue and what is causing it?
<?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">ADAPTER_NAME_INVALID</SAP:Code>
<SAP:P1>SOAP</SAP:P1>
<SAP:P2>PLSRV_CALL_ADAPTER</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unknown outbound adapter (name = SOAP)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Your help is very much appreciated.
Regards,
Adil Khalil

Hi Adil
Have you tried out the solution provided by Nisar Khan in the thread below. It looks similar to your case.
http://scn.sap.com/thread/609965
Here is another case similar to yours. You need to check if your SLD and cache are ok.
RFC Adapter Problem: Adapter Engine Field Blank
Rgds
Eng Swee

Problem in testing SOAP receiver adapter using SOAP UI

Dear Experts,
I'm trying to test my SOAP receiver adapter as mentioned in the blog http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/21844. [original link is broken] [original link is broken] [original link is broken] But, my request from ECC proxy keeps failing in XI communcation channel monitor. I've configured my receiver adapter http://ip:8080/mockSoapHTTPBinding and kept the authentication as NONE. Can any of you suggest?
ip - is my system ip shown in ipconfig.
mockSoapHTTPBinding - is the path.
Thanks.

What is the error of the messages? Are the messages leaving the SOAP adapter?
Please try both:
1. Go to Runtime Workbench -> Component Monitoring -> Adapter Engine -> Test message. Then, execute the message directly without the intermediate of the Proxy sender. This will allow you to check only the receiver SOAP.
2. Please use the TCPGateway tool attached from the note below. It will be a "man-in-the-middle" between the target WS and the Receiver SOAP channel, tracking the whole HTTP/SOAP message. Check if the message is well-formed.
[Note 856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=856597]
under question "Q: How can I trace the whole message?"

SOAP receiver adapter message: PI payload in parameter or body

Hi,
We tried to send messages via the following way to an external partner: SAP --> IDoc > XI (7.1)> HTTP(s) --> external partner.
We tried 2 techniques:
1. using a HTTP receiver communication channel with HTTP destination (using certificate).
As the path prefix in the destination, including parameters, exceeds 256 characters, we had to search for another solution
2. using the SOAP receiver communication channel with a target URL (https string) and indicator 'Do not use SOAP envelope' set
When sending the message, the body of the message, the IDoc XML payload doesn't seem to be read by the partner, probably related to the fact that they do not use the right software to do so, as decribed in forum:
SOAP receiver adapter error (SOAP receiver adapter error.)
Is this the right interpretation and is there no other solution than try to append the payload to the parameterlist ?
Regards,
Jan Macken

The partner found a way to read the body correctly

Missing soap action in the soap axis receiver adapter ?

Hi Guys,
I could not find the soap action field in the soap receiver adapter and i followed the OSS note
Note 1054986 - SOAP (Axis) receiver adapter's SOAPAction field missing
Please apply the following patch and use the handler parameter defaultSOAPAction for the XI30OutboundHandler handler in the request chain. This handler parameter can be configured as a module parameter for the HandlerBean module associated with this handler. It is noted that this module parameter takes precedence over the channel parameter for SOAPAction if this field is available.
For SP12
XI ADAPTER FRAMEWORK CORE 7.0
Support Package 12, Patch Level 1 (SAPXIAFC12P_1.SCA)
we are on SP15 so i think the option should be available ?
Do i need to add this parameter in the Module Configuration ?
Moduel Key : ?
Parameter Name: handler.type ---> is this right
Parameter Value ---> ?
we need to validate the user id and pw on IIS for NTLM authentication. Any help regarding developong the handlers would be great
any help would be appreciated.
Thanks,
Srini

Srinivas,
You are on the right path...........yes that is the right note for this issue.
The problem is this is not a general fix that comes with all service packs as the axis adapter is not used a lot, that being said.if you dont see it with sp15..i would safely go apply this fix and see if it works..else you might have to open an oss note for the same...
Hope that helps..
Regards
Ravi Raman
P.S: On my home system..i did apply the fix and i was on a much higher sp level ..i saw some errors..in the logs but nothing a restart couldent fix..

SOAP Receiver Adapter problem (client certificate required)

My Scenario is similar to described in https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3721. [original link is broken] [original link is broken] [original link is broken] I have two PI servers running on one machine. I am trying to post message HTTPS with Client authentication via SOAP adapter from one PI system to SOAP adapter of other PI server. I have done the following configuration.
PI Server AXD - (Client) - Receiver SOAP adapter
PI Server AXQ - (Server) - Sender SOAP Adapter.
Steps in AXD
1. I have created a certificate of AXD in the service_ssl view of key storage.
2. I have imported the AXQ public certificate in to AXD in the TrustedCAs of Key storage
Steps in AXQ
1. I have created a certificate of AXQ in the service_ssl view of key storage.
2. I have imported the AXD public certificate in to AXQ in the TrustedCAs of Key storage.
3. I have created a user in AXQ and assigned the certificate of AXD under usermangement in Security provider to this user.
4. I have added the AXD certificate under Client Authentication tab with require client certificate option checked in the SSL Provider.
5. I have assigned the user created in AXQ in the step above to the Sender Agreement.
Now when I post message from AXD with Configure Client Authentication checked (Here I have selected the certificate of AXD and view as service_ssl) I am getting the following error.
Exception caught by adapter framework: SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION - java.security.AccessControlException: client certificate required at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:884) at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_3
Any pointer to solve this problem is highly appreciated.
Thanks
Abinash

Hi Hemant,
I have couple of questions. Why do we need to import certificate for SOAP WS-Security and from where I can get it?
As far as my scenario goes I am not using message level security.
Secondly what do you mean by TRUSTED/WebServiceSecurity? I don't see any such view inside the Key Storage. I can see a view named just WebServiceSecuity though.
Also I don't have a decentralized adapter installation rather I have two separate PI instances having their own central adapter engine.
Abinash

Soap Receiver Adapter Error. Pls advice urgent

Hi All,
While using Soap Receiver Adapter for synchronous communication
*My Soap Request is:*
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:SendMessage xmlns:ns1="urn:MMWebSrvService">
<strFrom>XI</strFrom>
</ns1:SendMessage>
*My Soap Response from server is:*
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<tns:SendMessageResponse xmlns:tns="urn:MMWebSrvService" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<return xsi:type="xsd:int">-1</return>
<strErrorDescription xsi:type="xsd:string">String reference not set to an instance of a String. Parameter name: s</strErrorDescription>
</tns:SendMessageResponse>
How to resolve the error.
Regards

Henry,
Your xml message is not xsd compliant...see if you can generate a xml message using your wsdl with random values, compare that to your imcoming msg..and thats your issue..
Hope that helps
Regards
Ravi Raman
Reward points if helpful !

SOAP receiver adapter for Axis

Hi,
I used SOAP receiver adapter for Axis like below:
Transport Prorocol : HTTP
Message Protocol : Axis
Url: http://<IP>:<Port>/xxx/WebService/services/Head/yyy
Authentication : Basic
User: <user>
Password: <password>
SOAP Version : 1.1
SOAP Action: : <method>
Encapsulation Format : MIME
Payload Extraction : SOAP Body
When i drive PI message it generates error below.
What must i do to solve this problem?
Thanks.
Error message
com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.ejb.EJBException: Exception in getMethodReady() for stateless bean sap.com/com.sap.aii.axis.appxml|com.sap.aii.adapter.axis.ejb.jarxml|AFAdapterBean; nested exception is: com.sap.engine.services.ejb3.util.pool.PoolException: javax.ejb.EJBException: Exception raised from invocation of public void com.sap.aii.adapter.axis.modules.AFAdapterBean.ejbCreate() throws javax.ejb.CreateException method on bean instance com.sap.aii.adapter.axis.modules.AFAdapterBean@20715646 for bean sap.com/com.sap.aii.axis.appxml|com.sap.aii.adapter.axis.ejb.jarxml|AFAdapterBean; nested exception is: javax.ejb.CreateException: java.lang.NoClassDefFoundError: org/apache/axis/types/URI$MalformedURIException

*Url:* http://172.28.6.194:8080/AssetManagerWebService/services/Head/SapTest
When i use Url with *?wsdl* it generates below (it'is very long. I give part of it)
wsdl
<?xml version="1.0" encoding="UTF-8" ?>
- <wsdl:definitions targetNamespace="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns:intf="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns:tns1="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Types" xmlns:tns2="http://schemas.hp.com/AssetManager/R51/ACMetaData" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- 
- <wsdl:types>
- <schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:AdministrationTypes="http://schemas.hp.com/AssetManager/Custom/Head/Administration/Types" xmlns:CableTypes="http://schemas.hp.com/AssetManager/Custom/Head/Cable/Types" xmlns:CatalogTypes="http://schemas.hp.com/AssetManager/Custom/Head/Catalog/Types" xmlns:ChargebackTypes="http://schemas.hp.com/AssetManager/Custom/Head/Chargeback/Types"
<import namespace="http://schemas.hp.com/AssetManager/R51/ACMetaData" />
<import namespace="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Types" />
- <annotation>
<documentation>Auto-generated schema for AssetCenter web services for Head/SapTest Implementation</documentation>
</annotation>
<import namespace="http://schemas.hp.com/AssetManager/Custom/Head/SAM/Types" schemaLocation="../../schema/Head/SAM/SAMTypes.xsd" />
<import namespace="http://schemas.hp.com/AssetManager/R51/ACMetaData" ......
<wsdl:operation name="retrieveAllBusinessAPIListByName">
<wsdlsoap:operation soapAction="retrieveAllBusinessAPIListByName" />
<wsdl:input name="retrieveAllBusinessAPIListByNameRequest">
<wsdlsoap:body use="literal" />
</wsdl:input>
<wsdl:output name="retrieveAllBusinessAPIListByNameResponse">
<wsdlsoap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="SapTestService">
<wsdl:port binding="impl:SapTestSoapBinding" name="SapTest">
<wsdlsoap:address location="http://172.28.6.194:8080/AssetManagerWebService/services/Head/SapTest" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

Soap receiver adapter exception

Hi,
I am using SOAP receiver adapter to access a web service that is hosted on SAP Web AS (in this case it is the integration server Web AS). I use the web services navigator to test the web service and the web service works fine. The name of the web service is 'RemoteCrossReferenceProcessor' and it has one operation 'crossReference'.
But with the soap adapter, I am getting OperationNotFoundException in the logs and my web service is not getting accessed. Here is the server log:
<u><i>An error occurred while processing the message security. Reason: . See trace entry .#3#com.sap.engine.interfaces.webservices.runtime.OperationNotFoundException#Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:RemoteCrossReferenceProcessor'; Key name:'SoapRequestWrapper' key value:'crossReference'; #[no trace for com.sap.security.core.server.ws.service.ServerSecurityProtocol (severity above PATH)]#
#1.5#0003BA0FF9EA0022000000840000688D0003F9349A3C2D61#1118429251382#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage)######b40aca80d9be11d994360003ba0ff9ea#SAPEngine_System_Thread[impl:5]_47##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: NO_BACK_SYSTEM_IN_HOPLIST:#http://sapsand1:8000/sap/xi/engine?type=entry#</i></u>
Here is adapter configuration:
Transport Protocol:HTTP
Message Protocol:SOAP 1.1
Adapter Engine:Integration Engine
Target URL: http://<server_name>>:50000/RemoteCrossReferenceProcessor/Config?style=document
User:
Password:
Default SOAP Action:
I imported the WSDL into the external definition and used the messages from the WSDL for defining my interface mappings.
I am using XI 3.0 SR1 (SP 09).
I am out of ideas as to why the SOAP adapter is not calling my web service. Please help me with your suggestions.
Thanks and Regards.

HI Dani,
I was looking for this error and I found this post AXIS SOAP Receiver. This post says about other errors, but sugests many ideas to found the soluction, like:
1- non-deployed all AXIS jars; (but in this case it deployed all)
2- Exists this note for one erro in AXIS: (https://service.sap.com/sap/support/notes/1028961).
3- this document (http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b092777b-ee47-2a10-17b3-c5f59380957f) that have sets for header parameters. This is interesting becouse one of this parameters is obligatory but isn't filled, can occur error like "null object".
By the way, you can check if have update to AXIS (http://ws.apache.org/axis/), becouse isn't a SAP application and in other systems can have this error.
I hope this helps,
Romerito Silva

Do not use SOAP Envelope checkbox, MainDocument set as MainAttachment after call the receiver adapter

Hi experts,
We have a Proxy to SOAP scenario and we have the same issue mentioned in this post and in note 1522630, the version is SAP PI 7.31 (AEX). We configured 2 XSLT mappings and we use the MessageTransformBean (Transform.ContentType=text/xml;charset=utf-8) before call the standar module for SOAP receiver adapter.
Everything looks good but in the payload appears MainAttachment (in SAP PI and SXI_MONITOR in SAP ECC 6.0 SAP_BASIS 731) and the proxy can´t read the response for this reason.
This is that we see in the message content:
<sap:Manifest xmlns:sap='http://sap.com/xi/XI/Message/30' xmlns:xlink='http://www.w3.org/1999/xlink'><sap:Payload xlink:type='simple' xlink:href='cid:[email protected]'><sap:Name>MainAttachment</sap:Name><sap:Description>Main document</sap:Description><sap:Type>Application</sap:Type></sap:Payload></sap:Manifest>
Do you have any updates of this problem or any suggestion?
Thanks and regards.

Hi Sriram and Mark,
Thanks a lot for your help.
After a lot of test we solve the problem.
We are using an Integrated Configuration and the keepAttachment checkbox is not necesary.
The problem was that the value "ns0" in the message type of the xml was not added by the XSLT mapping(altova), we added manually in the xsl file and the proxy read the information.
The message content was not changed and looks like an attachment, also y sxi_monitor looks as MainAttachment in the payload but is interpreted good.

URL in SOAP Receiver Adapter

Hi,
I was given a WSDL file which contains the following:
<wsdl:port name="ZISU_INSTLN_CREATE" binding="tns:ZISU_INSTLN_CREATE">
<soap:address location="http:// hostname:port /sap/bc/srt/rfc/sap/zisu_instln_create/100/zisu_instln_create/zisu_instln_create" />
</wsdl:port>
I've configured a SOAP receiver adapter. In the URL i put the SOAP address location from the WSDL.
Is this correct?
I am seeing the following error when i try to send a message:
Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection refused: connect.
Is the error because of the url I use?
Thx
Robert

Hi,
I do have details in the message:
- <detail>
- <ns:SystemFault xmlns:ns="http://www.sap.com/webas/710/soap/runtime/abap/fault/system/">
<Host>undefined</Host>
<Component>COREMSG</Component>
- <ChainedException>
<Exception_Name>CX_SOAP_CORE</Exception_Name>
<Exception_Text>SRT: Wrong Content-Type and empty HTTP-Body received: ("HTTP Code 200 : OK")</Exception_Text>
</ChainedException>
and there is lot more if it helps finding the error, but maybe this is already enough.
Also i tried testing with SOAPUI now:
Result is good. I dont get error's. I get a response from my request as expected.
But if I test with XML from the RWB, with he same data as in SOAPUI, i get the error message again.
Conclusion:
SOAPUI can communicate with my SAP ISU system.
But PI cannot communicate with it.
Why?
Thx
Robert

HTTPS config in SOAP receiver adapter ?

Hi Guys,
I have configured the soap receiver adapter with the URL
*https://xxxx.abcd.com/xyzv/bbbb.asmx with the user authentication *
I have tested the url and the user and pw in the browser and they are working fine but the messages are failing the soap receiver adapter with the 401 unautorized error as the message from the Audit log in the RWB.
Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized. Setting message to status failed.
Do i need to configure the Java Stack for HTTPS ? The communicaion is between the XI system and a third part system internally.
any help would be appreciated ?
Thanks,
Srini

Hi Guys,
I have solved the problem and NTLM works with PI 7.0 but we need to configure soap axis adapter
The Windows NTLM authentication is supported by Axis's CommonsHTTPSender handler and consequently it is supported by the Axis adapter's corresponding handler com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender. Read about How Can I use CommonsHTTPSender as the transport handler? if CommonsHTTPSender is not enabled on your system. Once it is enabled, you can use com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender instead of default com.sap.aii.adapter.axis.ra.transport.http.HTTPSender as the transport handler in the module configuration and set the authentication setting to NTLM and enter usename as domain\username in the channel configuration
To use CommonsHTTPHandler, the optional Jakarta-Commons-Net, Jakarta-Commons-HttpClient, Jakarta-Commons-Codec libraries are required. Make sure that these libraries are available for the Axis adapter at the deployment check page If these components are not available, you will need to include the corresponding jar files (commons-codec-1.3.jar, commons-httpclient-3.0.jar, and commons-net-1.0.0-dev.jar from the Axis 1.4 release) in aii_af_axisprovider.sda and deploy this archive (see How to prepare aii_af_axisprovider.sda?).
The provider.xml file must include the jar-name entries for these jar files, as shown in:
    <jars>
       <jar-name>commons-net-1.0.0-dev.jar</jar-name>
       <jar-name>commons-codec-1.3.jar</jar-name>
       <jar-name>commons-httpclient-3.0.jar</jar-name>
    </jars>
Once you do all the above settings, NTLM works fine
Thanks,
Srini

Configure User Authentication on SOAP Receiver Adapter

Hi,
I am calling a WebService that is available over the internet. We are on PI 7.1 and I am using a Soap Receiver Adapter. The configuration was downloaded from SAP in a partner package. The development in the package was done on XI3.
I need to call the WS with user authentication. I've selected the "Configure User Authentication" radio button and entered the username and password. The message fail with "HTTP 401 Unauthorized" and it is because the user details are not being send from the adapter. If I copy the XML payload to a XML tool, like Stylus Studio, I can call the webservice successfully. I've read through numerous blogs and messages on this Forum, including adding the adapter module (MessageTransformBean) and changing the Conversion Parameters without any luck.
Any suggestions please?
Thanks

I am calling a WebService that is available over the internet.
I copy the XML payload to a XML tool, like Stylus Studio, I can call the webservice successfully.
normally the webservices that we use (from internet) are freely available...meaning they dont require any username/ password.
if no credentials are required then do not select Configure User Authentication...uncheck it....if user-details are provided by the Webservice, then use these details (not your XI/ PI user details) in the channel.
Are you using any user-name/ password while testing from SOAP tools?
Regards,
Abhishek.

Dynamic Receiver file name in AS2 adapter

Hi Experts,
How to get dynamic receiver file name in AS2 adapter. We need receiver file name same as of sender file name.
We tried selecting dynamic attributes file name but we are getting followin error in CC.
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: com.seeburger.xi.connector.queue.TaskBuildException: Mandatory attribute dtAS2FileName is not present in XI message., Mandatory attribute dtAS2FileName is not present in XI message.
Thanks,
Hari

hi hari,
You can't do it manually. As both adapter are in different context.
You can go with UDF to slove ur problem.
Just extract the input file name using Dynamic configuration
Store that in some variable.
Use same name in the dynamic file name in AS2 receiver. Below code might be useful.
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create( "http://seeburger.com/xi/common/dtAS2FileName", "DYNFILENAME");
conf.put(key,strfilename);
Thanks
Jai
Edited by: Jaideep Baid on Apr 9, 2010 9:16 AM

Xml file in dynamic file name in file receiver adapter

Hi,
I'm doing the dynamic file name in file receiver adapter. I have done as per instructed in /people/jayakrishnan.nair/blog/2005/06/20/dynamic-file-name-using-xi-30-sp12-part--i
All turned out okay. I have got the file name I require. Except that the file format is XML and I need to suppress the filename node occupied by the dynamic file name.
The content conversion mentioned in /people/sravya.talanki2/blog/2005/08/11/solution-to-the-problem-encountered-using-variable-substitution-with-xi-sp12, does not seem to solve my problem. As it is only for file format other than the XML one, because we only do the content conversion if we want to "convert" the format of the content from XML to the other format.
Does anybody have the solution to my problem? thanks in advance

Thank you Raj for the direction
The way to do it is :
1. In ID, advanced tab, put a check on the adapter-specific message attributes - file name.
2. Put a "*" on the file name scheme
3. In IR, create a UDF to set up target file name :
DynamicConfiguration conf = (DynamicConfiguration) container
.getTransformationParameters()
.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
// set up file name for receiver adapter
String SourceFileName = conf.get(key);
conf.put(key, TargetFileName);
return " ";
4. Map the above UDF to the header level of the target structure.
Regards,
Idi

Unknown receiver adapter (name = SOAP)

Similar Messages

Maybe you are looking for