Incorrect payload in receiver adapter

Hi everybody!
We came across following situation.
We have a PI scenario IDOC->File. We have one ERP as a Sender and a couple of Receiver FTP systems. There are 3 inbound interfaces for each Receiver system with different message types and mappings for each type and Service interface accordingly. So we send one IDOC from ERP and get 3 different files on FTP with different content. Everything worked fine on Development server.
Then we moved the scenario to QA Server using CMS. And there we got issues with the scenario. We start getting 3 files on Receiver FTP with different names but same content inside. It seems like they are using same Service interface. But in SXI_MONITOR everything is fine on every step! Proper service interfaces are used, proper mapping is called, proper receiver is determined and communication channel is right too. And payloads after each step are correct! But in Communication channel monitoring in Runtime Workbench we see incorrect payloads for incorrect service interfaces. So the system behavior is very strange.
We tried to clear cache, restart PI, recreate Interface determination and Receiver agreement but nothing seems to help. We are still getting wrong payload in end file.
Did anybody experience similar issues? Or maybe any ideas on that point. Any thoughts are much appreciated.
Thanks in advance,
Andrew

Hi Andrew,
Here are my check list which might help to re think on the issue.
1. Have you even transported the configuration objects(i.e., Sender, receiver agreements..)?
If not, it is better to re configure the scenarios.
2. I think the problem might be at your communication channel, have a check at this.
3. Majorly i believe the problem might be at Receiver Determination and Interface Determination.You have to again go through this thoroughly
By giving my above thoughts i might not able to solve your problem, but i might help you to re-check these and find the solutions.
Hope this helped
Regards
Ramesh

Similar Messages

Filename from payload - FTP receiver adapter

Hello everyone!
I have a scenario wherein I need to get the value from a field coming from an IDOC and then give that value as the "filename" of the file that is saved in the FTP folder.
IDOC > XI > FILE
For example, if /ORDERS05/IDOC/E1EDK02/BELNR = 620000123
then I want the name of the file to be saved in the FTP folder to be 620000123.xml
I understand you may use the 'variable substitution' property in the FTP receiver adapter, but subsequent attempts at trying to configure that property have resulted in errors. Can anyone help me out?
Warm regards,
Glenn

do u have recordset name (root message)
For Ex: If you want to refer to the field which is bold
below is your variable substuition:
payload:root,1,e1,1,e2,2
<?xml version="1.0" encoding="UTF-8" ?>
<root>
<dummy>
     <e1>
        <e2>Data_1</e2>
        <f/>
       <g attr="abc">text</g>
        <e2>Data_2</e2>
     </e1>
</dummy>
<e1>
     <e2>illegal/value</e2>
     <f/>
     <g attr="abc">text</g>
     <e2 attr="fghij">Example Value</e2>
   </e1>
</root>
Similarly
for your strucutre:
<MS_MT>
<order>
      <number>
the variable substuition would be
payload:MS_MT,1,order,1,number,1
you have to give complete XML to arrive to this value.

Payload at Adapter for System Errors - SOAP receiver adapter

Hi Everybody,
I am working on an Idoc to SOAP asynchronous scenario.
There are connection issues between SOAP adaper and the target webservice.
I need to capture the Idoc number from the message payload for the Erroneous messages at the adapter for the System errors.
Is there any way of capturing field values from the payload (Say, Idoc number) at the SOAP receiver Adapter level.
Helpful answers will be rewarded points.
Thanks & Regards,
Zabiulla

Hey,
I think you need to implement a module inorder to get the payload at receiver adapter module.
As far i concern you can not directly refer the payload in adapter in receiveer communication channel unless you have your own module, which gets the payload. Check the Modules tab in the communication channel and also regarding how to get the payload for error information, follow the steps mentioned in the below link, which gets the payload in file. hop it will resolve your issue.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/snippets/writepayloadtoafilefromAdapter+Module
Regards..
Prasanna..

Extra header lines appearing in payload after singning and encrypting in Mail Receiver adapter PI 7.31

Hi,
We have a mail receiver adapter which is sending out a edi payload as attachment to the external receiver.
When we send the normal .edi file it is ok.
But when we sign and encrypt the payload and send it out, the external customer receiver decrypts and validates the message successfully but when their application tries to read the edi payload it finds the extra header lines as below :
content-id:
<[email protected]>
Content-Disposition: attachment; filename=xxxxxxxx.edi Content-Type:
application/xml
At their end, their application (DataPower) expects the first three characters of the payload
(decrypted payload) to be either UNA or UNB.This is how it validates whether the incoming message is an EDI message.
But it encounters the extra MIME headers in the payload.
Therefore it gets rejected by DataPower which thinks the content is an
unknown message type.
How to suppress the header lines appearing in the payload(after decryption and validation).
Thanks,
Guest

hi,
try content-type as "text/xml"

Q? how to change filename of receiver adapter includeing payload attribute?

hi all.
our scenario is IDOC - XI - FILE.
IDOC is standard type .xml"
Despite of searching help library, just read about how to change using payload value.
How to change the filename using payload attribute?
Message was edited by: ChangSeop Song

Hi,
You can create the file name dynamically from the payload of the receiver adapter as follows.
From the requirement you have stated, you want your file to be named as,
TPSDLS<shipmentid>.
For this, in the reciver file adapter, give your filename as <b>TPSDLS%var%</b> and under variable name substitution,
<b>var</b> --> <b>payload:IDOCTYPE,1,Shipments,1,ShipmentID,1</b>
here, var acts as your variable name and it first looks for IDOCTYPE and its first occurence, shipment and its first occurence and finally, shipmentID and its first occurence. There by generating the filename dynamically.
For more info on this, check the topic <b>variable substitution</b> under this link.
http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
hope this helps,
let me know if you have any clarification,
regards,
bhavesh

Soap receiver adapter payload with certficate signature

I have a requirement.. where XI calls external webservice using SOAP.
I have configured SOAP receiver adapter, but the webservice wants the certificate authentication.. From XI we sent the certficate to external webservice and then in the comm channel I did activate the 'certficate' check box. It did not work.
For test purpose now they have deactivated the certficate authentication in their end.. it works if they deactivate. It means there is no issue with request structure.. purely the issue is when I use the certficate.
External webservice sent me the copy of the soap request which works for them.. <b>that has security signature inside the payload.</b> ( I have atteched below).
If anybody has done it have an idea how to do it please let me know.
- <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <soapenv:Header>
- <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" wsu:Id="CertId-62149565">MIIGOzCCBaSgAwIBAgIQIKVRaj76KNaG5Dl6P5X7wzANBgkqhkiG9w0BAQUFADCBnjEPMA0GA1UEChMGaHAuY29tMRowGAYDVQQLExFJVCBJbmZyYXN0cnVjdHVyZTELMAkGA1UEBhMCVVMxIDAeBgNVBAoTF0hld2xldHQtUGFja2FyZCBDb21wYW55MUAwPgYDVQQDEzdIZXdsZXR0LVBhY2thcmQgUHJpbWFyeSBDbGFzcyAyIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MDMyMzAwMDAwMFoXDTA4MDMyMjIzNTk1OVowUDEgMB4GA1UEChQXSGV3bGV0dC1QYWNrYXJkIENvbXBhbnkxEDAOBgNVBAsUB1NlcnZlcnMxGjAYBgNVBAMTEWl0Zy5lcHJpbWUuaHAuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDVGa1x5j/RJHHkqYzEb9NIQGChffTb1D0LiYAP5arbxz0trCp8ZeG4FCH71jc6x9Ks3gC4YdWgQbOCz64wnpM8NvEVCZBHuxvdnPZpziPWQqDr0yvwSoCXg8mkeJrHql0MSm7TNiyhzCAzlmB9JgmoHrRtArJdXMRpHjdZQK3QIDAQABo4IDxTCCA8EwDAYDVR0TAQH/BAIwADAOBgNVHQ8BAf8EBAMCBaAwHwYDVR0jBBgwFoAUSlYfvIpRj/SDE8naXHlUyAK6q58wHQYDVR0OBBYEFE99o7D6AITUcqWVmeYzu/2k66VEMIIBKAYDVR0fBIIBHzCCARswggEXoIIBE6CCAQGUWh0dHA6Ly9vbnNpdGVjcmwudmVyaXNpZ24uY29tL0hld2xldHRQYWNrYXJkQ29tcGFueUlUSW5mcmFzdHJ1Y3R1cmUvTGF0ZXN0Q1JMLmNybIaBuWxkYXA6Ly9sZGFwLmhwLmNvbS9DTj1IZXdsZXR0LVBhY2thcmQlMjBQcmltYXJ5JTIwQ2xhc3MlMjAyJTIwQ2VydGlmaWNhdGlvbiUyMEF1dGhvcml0eSxPPUhld2xldHQtUGFja2FyZCUyMENvbXBhbnksQz1VUyxPVT1JVCUyMEluZnJhc3RydWN0dXJlLE89aHAuY29tP2NlcnRpZmljYXRlcmV2b2NhdGlvbmxpc3Q7YmluYXJ5MCoGA1UdJQEB/wQgMB4GCCsGAQUFBwMBBggrBgEFBQcDAgYIKwYBBQUHAwQwggEWBgNVHSAEggENMIAwgAYKKwYBBAELBAMCATCAMCkGCCsGAQUFBwIBFh1odHRwOi8vZGlnaXRhbGJhZGdlLmhwLmNvbS9jcDCABggrBgEFBQcCAjCAMB4WF0hld2xldHQtUGFja2FyZCBDb21wYW55MAMCAQIagZVBdXRob3JpdHkgdG8gYmluZCBIZXdsZXR0LVBhY2thcmQgQ29tcGFueSBkb2VzIG5vdCBjb3JyZXNwb25kIHdpdGggdXNlIG9yIHBvc3Nlc3Npb24gb2YgdGhpcyBjZXJ0aWZpY2F0ZS4gSXNzdWVkIHRvIGZhY2lsaXRhdGUgY29tbXVuaWNhdGlvbiB3aXRoIEhQLgAAAAAAAAAAAAAwge4GCCsGAQUFBwEBBIHhMIHeMCsGCCsGAQUFBzABhh9odHRwOi8vb25zaXRlLW9jc3AudmVyaXNpZ24uY29tMIGuBggrBgEFBQcwAqSBoTCBnjEPMA0GA1UEChMGaHAuY29tMRowGAYDVQQLExFJVCBJbmZyYXN0cnVjdHVyZTELMAkGA1UEBhMCVVMxIDAeBgNVBAoTF0hld2xldHQtUGFja2FyZCBDb21wYW55MUAwPgYDVQQDEzdIZXdsZXR0LVBhY2thcmQgUHJpbWFyeSBDbGFzcyAyIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MA0GCSqGSIb3DQEBBQUAA4GBAMB3vOFZYe26MaZ8mpnoZwhWbLBFV/lxtefZT1uT7mKZiaHjVqwu3tN1eAYAUXtJQHVJTnCnbDm9zFunlvuEzGMt9PwXS61MK6GwPmtjEsevRnGIA7arvpjSJ1/EQlD620I7icM9BNXbElYFfsnZjlWKFTZz3VX1OT2qmJtVWpD</wsse:BinarySecurityToken>
- <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
- <ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
<ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" />
- <ds:Reference URI="#id-24819136">
- <ds:Transforms>
<ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
</ds:Transforms>
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
<ds:DigestValue>6Mzpm7P8k3f8UuxbBMP4ZTC83Yc=</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue>HcqMChOzlHFXTRRAf7kyTSQ5Jd53Yiu7oFLjkh5P3vayo2G4sjFv/qFKHX0E6a5xkBMTIRrW+30t7IdB4X0x35FPO1dTulz37KM1/jpLSGVxnjnWWeFZvseVjJsk5NTPiSE6GAjO7rFW/Vled2djATTmZsIgJCIfhLYVp112Uis=</ds:SignatureValue>
- <ds:KeyInfo Id="KeyId-21369792">
- <wsse:SecurityTokenReference xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="STRId-29015968">
<wsse:Reference URI="#CertId-62149565" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" />
</wsse:SecurityTokenReference>
</ds:KeyInfo>
</ds:Signature>
</wsse:Security>

go through this webinar and follow the steps...It will solve your problem..
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1b657d59-0c01-0010-4fa8-f792fa412823
Regards,
Ravi

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

SOAP receiver adapter - payload inside the soap envelop

Hi,
We have to send a SOAP message to 3rd party from PI 7.1. Using SOAP receiver adapter - we are trying to achieve this. 3rd party software is unable to accept payload as an attachment of the main envelop - they want it enside the main envelop.
I tried with "Keep attachment" option - but PI still keping the payload as an attachment. I think this option is for handling "extra" attachment.
Is there any way we can keep the payload inside the envelop?
In run-time WB, at the moment envelop looks like
<SOAP:Envelope xmlns:SOAP="http://schemas....
<SOAP:Body>
<sap:Payload xlink:type="simple" xlink:href="cid:payload-d6518670ca1311debbd9ca347000800b...">
</SOAP:Body>
</SOAP:Envelope>
And the payload d6518670ca1311debbd9ca347000800b... ( again viewed from RWB) - contains the data.
<?xml version="1.0" encoding="UTF-8" ?>
<ns2:Order> ....
</ns2:Order>
Can we insert this payload directly inside the SOAP:Envelope body instead of a link there?
Regards,
Sudhin

Hi!
It seems to me that this 3rd party is expecting only XML not SOAP.
If this is the case, you should use the HTTP Receiver adapter instead of SOAP.
Some systems 'say' they can speak SOAP but they can only speak XML. Not to blame, it's a mistake many make these days.
The only way you use SOAP Receiver adapter with this 3rd party, is that if someone from the 3rd party hands you a WSDL file.
Ricardo Sancio Lóra
Brazil

JDBC Receiver Adapter:Incorrect syntax near the keyword 'FROM'

Hi All,
I'm trying to get data from an SQL 2005 server using synchronous JDBC receiver adapter. I'm using PI 7.0. My outgoing message is as follows:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_IZIN_YUKU_REQ xmlns:ns0="http://holding.com/brd/">
- <STATEMENT>
- <ECZ_IZIN_YUKU action="SELECT">
<table>ECZ_IZIN_YUKU</table>
<access />
- <key>
<iy_yil compareOperation="GT">1900</iy_yil>
</key>
</ECZ_IZIN_YUKU>
</STATEMENT>
</ns0:MT_IZIN_YUKU_REQ>
I've found the following log in the trace file:
#1.5#0014C23BCFC900630000003D000013B000042740B0A858B1#1169058702046#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#sap.com/com.sap.aii.af.app#com.sap.aii.adapter.jdbc.XI2JDBC.onInternalMessageBinary(Message)#J2EE_GUEST#0####fa10f5f0a65811db84410014c23bcfc9#XI XI2JDBC[CC_JDBC_RECI_BRD_TO_BHT/HUMANIST/]_2574##0#0#Error#1#com.sap.aii.adapter.jdbc.XI2JDBC#Plain###Error processing request, rollback: Error processing request in sax parser: Error when executing statement for table/stored proc. 'ECZ_IZIN_YUKU' (structure 'STATEMENT'): com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near the keyword 'FROM'.#
Thanks a lot..

Hi,
Make sure the XML structure for your SQL statement is correct. Include the all the fields in the structure of XML.
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_IZIN_YUKU_REQ xmlns:ns0="http://holding.com/brd/">
<STATEMENT>
          <TECZ_IZIN_YUKU ACTION="SELECT">
                 <TABLE>ECZ_IZIN_YUKU</TABLE>
                          <ACCESS>
                               <EMPNO></EMPNO>
                               <NAME></NAME>
                           </ACCESS>
                             <KEY>
                                   <iy_yil compareOperation="GT">1900</iy_yil>
                             </KEY>
</TABLENAME>
</STATEMENT>
</ns0:MT_IZIN_YUKU_REQ>
Best Regards

HTTP Receiver Adapter payload as single line plain text with out any tags.

Hi PI experts,
I have a strange problem in http receiver adapter.
Sender RFC (SAP) Receiver: HTTP.
Receiver system expects the output from XI in the below format in a single line plain text with out any tags in the payload. and the content type should be application/x-www-form-urlencoded
Group=Test&Sentinel=Web%20Server&Facility=5345&Order Number=XT-XWHM-Y-NA&Serial Number=123456&@LABEL_QUANTITY=5&@LABEL_NAME=111114_Q
Is there any way to achieve this using http receiver adapter. Business is not ready to accept the output from XI not even in a single element instead they only need it as a JUST a plain text.
Appreciate early response on this.
Thanks in Advance,
Jitender

Dear Ola,
Could you elaborate how you achieved in catching the response data from the receiver in case of HTTP receiver adapter?
The target service is not a WebService but some python script that must to receive some paramters via POST request.
HOW can I post this parameters?
Here you entered the fields of the message type of the request in the header parameters of the receiver adapter? Thats fine.
But what about the message type and vice versa of the response from the receiver?
Regards
Rebecca

Zipping the output payload and Unzipping the incoming payload with HTTP_AEE Receiver adapter

Dear Expert,
I have a synchronous scenario(ABAP proxy to HTTP_AEE) to send the payroll of the employees to bank. As payroll payload size will be huge, I need to Zip the outgoing payload to bank, also I need to unzip the incoming payload(response) from the bank, because bank will be sending the response in zip format.
As I am using HTTP_AAE receiver adapter, therefore HTTP_AAE receiver adapter needs to zip the output payload as well as unzip the incoming payloads from bank.
I understand we have PayloadZipBean , to do zip and unzip, and we can configure it under module tab, however I just want to clarify the below point.
1- Can I do zip and unzip both under the HTTP_AAE receiver adapter, if yes then what will be the order? I mean first zip then unzip right?
2- Has anyone used PayloadZipBean with HTTP_AAE receiver adapter in sync mode, if yes, please share you experience.
3- I need to name ZIP file after zipping as "PRMSG" , how can I give name in HTTP_AAE adapter, I have tried with zip.filenameKey but it didn't work.
Thanks,
Farhan

Hi Praveen,
Thanks a lot for the response, seems I can rely on this PayloadZipBean for my requirement.
One more question, As I have already created the HTTP response and Proxy response structure message type, moreover message mapping has been created to map these. So, once I will receive the response from bank, in zip file format, and when PayloadZipBean will unzip the convert it to XML payload, do I need to do anything else to map it my response structure?
Thanks,
Farhan

Error while updating database using jdbc receiver adapter

Hi All,
I am trying to update a single record using jdbc receiver adapter.
This is my the message that is getting created..
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:Data xmlns:ns0="urn:Test">
- <STATEMENT>
- <TABLENAME ACTION="UPDATE_INSERT">
<TABLE>ORDERS</TABLE>
- <ACCESS>
<OrderID>99999</OrderID>
<CustomerID>VICTE</CustomerID>
<EmployeeID>3</EmployeeID>
<ShipAddress>VICTE</ShipAddress>
</ACCESS>
- <KEY>
<OrderID compareOperation="EQ">99999</OrderID>
<ShipAddress compareOperation="EQ">VICTE</ShipAddress>
</KEY>
</TABLENAME>
</STATEMENT>
</ns0:Data>
But in Adapter Monitoring i am getting the following error..
<i>Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'ORDERS' (structure 'STATEMENT'): java.sql.SQLException: [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near 'VICTE'.</i>
Regards,
Rahul

Rahul,
> In this case i believe the interface has to be synch.
> So what will the response message type be like..
Not necessary. UPDATE can be asynch as well.
Can you turn the trace on like pointed by Michal and then you can see the Query in the Audit Log of the adapter montioring. Try to execute the same query from your DB Client like TOAD and see what is the Syntax error you are getiing.!
The problem looks like some field has some dataype / column name mismatch.
Regards
Bhavesh

Mail receiver adapter: THeaderREPLY-TO not working on ASMA

Hello people,
(note: all the @ where changed by " at " because of limitations of SDN)
I'm trying to set some adapter specific message attributes (ASMA) in a mail receiver adapter.
Two properties I'm trying to set: THeaderFROM e THeaderREPLY-TO.
The first one is working great, the second one does not work.
My scenario is Soap to Mail. I send a soap message, in the message mapping a user defined function get the mail address (to and reply-to) and set it with DinamicConfiguration like this (hard coded to be simple):
DynamicConfiguration conf = (DynamicConfiguration)container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/Mail", "THeaderREPLY-TO");
conf.put(key, "reply.to at teste.com";);
DynamicConfigurationKey from = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/Mail", "THeaderFROM");
conf.put(from, "from at teste.com";);
As in the documentation, it should work. But the mail message reaches the mailbox with mime header Return-Path = from at teste.com.
Reading all the notes related to mail adapter (and adapter module processing) I found the tool TCPGateway to monitor what is going from adapter engine to the mail server. So I changed a little the scenario to test it and now the scenario is Soap->TCPGateway->MailServer. In the TCPGateway I got this:
EHLO brjgs916.weg.net
MAIL FROM:<from at teste.com>;
RCPT TO:<roberti at mycompany.net>;
DATA
Date: Thu, 5 May 2011 19:55:17 -0000
Subject: mail - teste
To: roberti at mycompany.net
From: from at teste.com
MIME-Version: 1.0
content-id: payload-98c5c8b0775111e090110018714e4a28 at sap.com
Content-Type: text/xml;charset=utf-8
Content-Disposition: attachment;filename="Untitled.xml";
Content-Transfer-Encoding: binary
<?xml version="1.0"; encoding="UTF-8"?>
<ns0:MTP_SAMPLE_MAIL_MESSAGE xmlns:ns0="http://soa.weg.net/sampleMail"><Title>titulo</Title><Body>body a ser preenchido</Body><Footer>footer tambem</Footer></ns0:MTP_SAMPLE_MAIL_MESSAGE>.
QUIT
With this information, I found that something is not right in the mail adapter, because it is not writing the relevant reply-to attributes to the mail message.
Some of you has any idea about it?
Thank you in advance.
waldemar roberti
Edited by: Waldemar Roberti on May 5, 2011 5:02 PM

Satish,
Actually (for testing purposes) I have the email roberti at mycompany.com set in all fields of receiver mail adapter mail attributes (from, to, cc and bcc). I turned all of them on and of and analysed the result. It seems that the information whe put on ASMA overloads the information on these mail attributes. But, in mail attributes, we don't have a field for REPLY-TO, just on ASMA we have this field.
So... the problem is in REPLY-TO. It has not been set in mail adapter, even if I set it with dinamic configuration.
thank you.
Waldemar Roberti

File Receiver Adapter Error

I'm using Variable substitution for the Directory I determine dynamically using UDF. I'm gettig following error. Would someone clarify how to wrok around this error.
2006-09-28 14:43:38 EDT: Message processing failed: Error during variable substitution: java.text.ParseException: Security violation encountered during variable substitution: Content of variable var2 is not safe: /sales/temp

Doss,
for Directory I was using variable substitution.
for example %var2% and then Var1 Iam getting from the Payload ( Iam populating the payload from UDF ).
When I checked 'disable security checks' on the receiver adapter screen, I'm not getting this error anymore.
Message was edited by: Ram Krish

Usage of Module processor in SOAP Receiver Adapter

Hi,
I have scenario where I am calling an external Web Service via XI. Unfortunately I need Java Mapping to generate the complete SOAP Message (there are some special header elements required by the Web Service) and flag 'no soap' in the SOAP Receiver Adapter. This works fine, but I have additional Web Service Calls that have the same Header logic and I don't want to use Java Mapping all the time.
I was wondering if it is possible to use graphical User Mapping for the Business Data that goes to the SAOP Body as a payload and use Java code to generate the SOAP Message (actually the SOAP Wrapper and the Header).
Can I do this in XI using the Module processor in the SOAP Receiver adapter or do I have to use two mappigs, one based on the Graphical mapping and another using Java Mapping? Is it feasible at all in XI?
Thanks in advance.

Hi,
You can use Module Processor.
But,
1. If it is a synch call, in when the message is going from the SOAP adapter to the Webservice, you will need to manually Add the SOAP header as you want . ( you will need to create the entire SOAP mesage as the output of the Module ).
2. When the response comes back, the same module will need to remove the SOAP header etc and pass a valid , XML message to the Graphical mapping.
If you have a requirement that some fields of the SOAP header will be needed to be accesed in the Response mapping, then you would need to either add this field to some field in the response payload.
Better option would be to use, Either a Java or a XSL mapping that does all the required stuff for you.
Regards
Bhavesh

Incorrect payload in receiver adapter

Similar Messages

Maybe you are looking for