EMail Receiver adapter.

Hi All,
Please send me documents for File to Mail Scenario.
1. If I want to send mail content as attachment then do I need to select Message Protocol as XIPAYLOAD or XIALL ?
2. If I want my mail content should come as message format in my mail and not as attachment then do I need to select Message Protocol as XIPAYLOAD or XIALL ?
Regards

Hi Rick,
Mail Adapter Scenario:
/people/prasad.ulagappan2/blog/2005/06/07/mail-adapter-scenarios-150-sap-exchange-infrastructure
Messages with Attachments:
The specified item was not found.
The specified item was not found.
eMail Report as Attachment (Excel/Word)
http://www.riyaz.net/blog/index.php/2008/02/23/xipi-sending-emails-using-xi-mail-adapter/
http://****************/Tutorials/XI/IDoctoMail/demo.htm
The specified item was not found.
Regards,
Vinod.

Similar Messages

How to refer MessageID in email receiver adapter

Hi All,
We are using module configuration in Receiver Mail adapter to send emails. Below is my configuration. (We are using SAP PI 7.11). Emails are being sent. However I am trying to include messageID in the email body however I could not.
I have defined MessageID as a param in my XSLT However i still don't see messageID. Do i need to do anything extra in Module configuration?
Any pointers is greatly appreciated..
<xsl:param name="MessageId"/>
<Subject>
<xsl:value-of select="concat($subject, $MessageId)" />
</Subject>
Below is my configuration..
Parameter/General tab:
Message Protocol : XIPAYLOAD
Use Mail package option is selected.
Content Encoding = none
Module tab:
Processing Sequnce:
AF_Modules/MessageTransformBean : XSLT
sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean : mail
Module Configuration:
XSLT Transform.Class com.sap.aii.af.sdk.xi.adapter.XSLTConversion
XSLT Conversion.XSLTFileName /tmp/GL_POST_RESPONSE_EMAIL.xsl

Hi Chirag,
Thanks for the response. I am having MessageId above the template match tag. But message ID is still not accessible within the XSLT. It is probably because XSL is used in the mail adapter module configuration. Is there any way to include the message ID in the receiver email adapter setup?
<xsl:param name="MessageId"/>
<xsl:param name="RefToMessageId"/>
<!<xsl:param name="inputparam"/>>
<xsl:template match="/">

Message monitoring Status Waiting for email receiver

Hi Guru,
Scenario: SAP ECC will call Error Handling interface class. The communication channel for the Error Handling interface is Email Adapter.
Below is CC setting:
Adapter Type: Mail (Receiver)
Transport Protocol: SMTP
Message Protocol: XIALL
Adapter Engine: Integration Server
URL: smtp://11.11.11.111/
Check - Configure User Authentication
User : user1
Password: password
Mail Attributes:
From: [email protected]
To : [email protected]
Subject : test
Content Encoding: base64
I encountered one problem where my email receiver status in message monitoring is always 'Waiting'. I do not know what went wrong in the setting? Does anyone know how to solve my problem ?
Thanks in advance.
Regards

XI tries 3 times before changing the status of the message to System Error. One can Manually resend the error messages by using the RESEND button in RWB. In scenarios where XI was trying to send the message to an end system that was down for maintenance, you would want XI to resubmit the message automatically without human intervention. What would be nice is to able to tune the retries like IS_Retry which is available for Integration engine.
We can achieve this by changing the retry count used by the Adapter Engine, by default its set to 3 times, 5 minutes apart. This count can be changed in Visual Admin->server->services-> SAP XI Adapter: XI.
Here change the number Retries parameter from 3 to 10 and change the retry retryInterval to around 10minutes. For these configuration changes to be picked up, restart SAP XI Adapter: XI.
please visit the blog
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically

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"

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

Email Receiver Error

Hello everybody,
I have the next error in the configuration of an Email receiver communication channel:
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: java.net.ConnectException: Connection refused: connect
this error is displayed in the RuntimeWorkbench, now everything seems OK in the configuration, any suggestions of what could be happening?, I mean I'm lost on what to look for in this kind of error, cause I've configured another channel like this before and worked really well, I'm sure on the SMTP server name in the configuration, any suggestions would be really appreciated, thanks in advance.
Regards,
Julio Cesar

Thanks for your anser, actually I have configured that server in my Outlook, so that's how I confirmed is up, I've tried gmail, hotmail and company emails, so I don't now if there's something in the network or with the adapter, now I have no idea what to check if there's something with the network, any sugeestions?, thanks again.
Regards,
Julio Cesar

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.

Error in Mail Receiver Adapter

Hi Everyone,
    I have been doing Mail Receiver Adapter Scenario.I am getting this error in Adapter Monitoring in Runtime Workbench.
<b>not initialized: failed to initialize the channel: com.sap.aii.messaging.util.URI$MalformedURIException: no scheme</b>
I would appreciate if anyone would provide a solution for this issue.
Thanks & Regards,
Varun Reddy.K

Hi Jai Shankar, Thanks for your reply.
     This is the XML source code generated after doing Mapping.
<?xml version="1.0" encoding="UTF-8"?>
<ns0:SourceMT_mail27 xmlns:ns0="http://isg.com/xi/training/MailReceiver27">
   <Subject>This is only a test mail</Subject>
   <From>[email protected]</From>
   <To>[email protected]</To>
   <Content>hi sudhir, How are you doing?</Content>
</ns0:SourceMT_mail27>
Regards,
Varun Reddy.K

File receive adapter command line error handling

Hi,
This is our requirement - After the file receive adapter, we need to run a script. Based on the return code of the script, we need to handle the error handling of the interface (i.e. send an email about the error).
I have looked at the operating system command line in the file adapter. How does XI handle return codes for the command line? If the command line has a error return code, how to send an email from XI?
If anyone has ideas on this topic, please respond!!
thanks,
lasya

Hi,
I don't think so, it is possible directly. You can not get the Response back to XI pipeline from the shell script.
But you can think, if you are able to call this from Mapping.
And one more option is using Transport Acknowledgement ( with BPM) if the file is not able to write into the target directory you can raise an alert-
Blog on this-
/people/michal.krawczyk2/blog/2006/06/22/xi-playing-with-the-file-adapters-acknowledgments
Regards,
moorthy

Mail Receiver Adapter Attachment Content Encoding

Hello to all,
we use a mail receiver adapter to sent XI messages as email. Everything works fine but the content encoding of the attachment is set to UTF-8. I need ISO-8859-1 instead of UTF-8. How could I achieve this ?
Thanks Christian

Hello Stefan,
we've tried this too (content type to: text/plain;charset="ISO-8859-1"), but it didn't work.
This is our output structure
<?xml version="1.0" encoding="ISO-8859-1"?><ns:Mail xmlns:ns="http://sap.com/xi/XI/Mail/30"><Subject>Daten von 01.07.2008 12:20</Subject><From>mail(at)dummy.de</From><To>max.muster(at)web.de</To><Content_Type>multipart/mixed; boundary="--AaZz"</Content_Type><Content>----AaZz
Content-Type: text/html; charset=ISO-8859-1
Content-Disposition: inline
Mit freundlichen Grüßen
----AaZz
Content-Type: text/plain; charset=ISO-8859-1; name=Daten 01.07.2008 1220.txt
Content-Disposition: attachment; filename=Daten 01.07.2008 1220.txt
"N";2000000003;"1234123412341234";1234500009;000000000000;01;"L";"OKDAU";1;"Prof. Dr.";"Max";"Mustermann";"";"Musterstraße";"";000000;"PLZ45";"Musterhausen";"";19990101;"max.mustermann(at)muster.com";"";"";"";"";"1";"Titel";"Vorname";"Name";"20000101";"";"0";"Max Mustermann";"L";"BLZ";"100000001";"Musterbank";00;;01;000000;;;00;1;0;0;1;0;"ForumNr";1;1;0;1;0;1;0;0;20080620;0;;0;20080620;0;20080620;0002;STANDARD
"N";2000000004;"5678567856785678";1234567009;000000000000;01;"L";"OKDAU";1;"Prof. Dr.";"Stefan";"Maier";"";"Teststraße";"";000000;"PLZ65";"Testhausen";"";19991201;"stefan.maier(at)test.de";"";"";"";"";"1";"Titel";"Vorname";"Name";"20001201";"";"0";"Stefan Maier";"L";"BLZ";"100000001";"Testbank";00;;01;000000;;;00;1;0;0;1;0;"ForumENr";1;1;0;1;0;1;0;0;20080620;0;;0;20080620;0;20080620;0002;STANDARD</Content></ns:Mail>
But the attachment is UTF-8
Thanks for your help.
Christian

Mail Body Formatting - Mail Receiver Adapter

Hello,
I use the Mail Receiver Adapter (SMTP) with and use Mail Package to set Attributes during Mapping.
My Question: Is there any possibility to format the body of the Email Message (e.g. line feeds) when mapping the field "Content" of the target structure?

If you use the graphical mapping tool, then you can use a user defined function for this issue. In this function you add the line feeds.
Regards
Stefan

Variable Substitution File Receiver Adapter

Hi,
I am in the process of implementing a scenario involving the conversion of a .jpg file to .bmp. In my scenario, I'd like to the .bmp file name to be dynamically controlled; therefore, I have used the Variable Substitution option in the File Receiver Adapter.
In both the File Sender & Receiver comm. channels, I have ticked 'Adapter Specific Messsage Attributes' check-box and selected the 'File Name' option.
The File Receiver comm. channel also has the following:
File Name Scheme*: %File_Name%.bmp
Variable Name: File_Name
Reference: message:FileName
Having done the above, I am getting the following error message in Comm. Channel Monitoring:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error during variable substitution: com.sap.aii.adapter.file.varsubst.VariableDataSourceException: Unknown message header category 'FileName' for variable 'File_Name'.: com.sap.aii.adapter.file.configuration.DynamicConfigurationException: Error during variable substitution: com.sap.aii.adapter.file.varsubst.VariableDataSourceException: Unknown message header category 'FileName' for variable 'File_Name'.
Would really appreciate your assistance on this.
Regards,
Reuben.
PS: The Sender File Adapter has the

Hi,
The full error message is s follows:
Runtime exception during processing target field mapping /ns0:MaterialBITMAP_In. The message is: Exception:[java.lang.NullPointerException] in class com.sap.xi.tf._Test_Conversion_ method setfilename$[17092008, osinef, com.sap.aii.mappingtool.tf3.rt.Context@d3b0d3b] com.sap.aii.mappingtool.tf3.MessageMappingException: Runtime exception during processing target field mapping /ns0:MaterialBITMAP_In. The message is: Exception:[java.lang.NullPointerException] in class com.sap.xi.tf._Test_Conversion_ method setfilename$[17092008, osinef, com.sap.aii.mappingtool.tf3.rt.Context@d3b0d3b] at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:350) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:401) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:142) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInternal(ServerMapService.java:431) at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:169) at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.execute(MapServiceBean.java:52) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0_0.execute(MapServiceRemoteObjectImpl0_0.java:301) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0_0p4_Skel.dispatch(MapServiceRemoteObjectImpl0_0p4_Skel.java:146) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:215) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Exception:[java.lang.NullPointerException] in class com.sap.xi.tf._Test_Conversion_ method setfilename$[17092008, osinef, com.sap.aii.mappingtool.tf3.rt.Context@d3b0d3b] at com.sap.aii.mappingtool.tf3.rt.FunctionWrapper.getValue(FunctionWrapper.java:56) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:294) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:401) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:142) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInternal(ServerMapService.java:431) at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:169) at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.execute(MapServiceBean.java:52) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0_0.execute(MapServiceRemoteObjectImpl0_0.java:301) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0_0p4_Skel.dispatch(MapServiceRemoteObjectImpl0_0p4_Skel.java:146) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:215) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at com.sap.aii.mappingtool.tf3.rt.FunctionWrapper.getValue(FunctionWrapper.java:47) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:294) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:401) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:142) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInternal(ServerMapService.java:431) at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:169) at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.execute(MapServiceBean.java:52) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0_0.execute(MapServiceRemoteObjectImpl0_0.java:301) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0_0p4_Skel.dispatch(MapServiceRemoteObjectImpl0_0p4_Skel.java:146) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:215) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: java.lang.NullPointerException at com.sap.xi.tf._Test_Conversion_.setfilename$(_Test_Conversion_.java:61) ... 24 more RuntimeException in Message-Mapping transformation: Runtime exception during processing target field mapping /ns0:MaterialBITMAP_In. The message is: Exception:[java.lang.NullPointerException] in class com.sap.xi.tf._Test_Conversion_ method setfilename$[17092008, osinef, com.sap.aii.mappingtool.tf3.rt.Context@d3b0d3b]
11:15:02 End of test
Reuben.

Problem with Variable Substitution Receiver Adapter

Hi,
I need to use a dynamic filename so I'm using the variable substitution in my receiver adapter. BUT, the filename can't appear in the file. So i used this blog in reference --> Solution to the problem encountered using Variable Substitution with XI-SP12
The PROBLEM is I still get and extra blank line in the file. How can I eliminate this extra line?
Thanks in advance.
Using XI 7.0

Hi Gaurav,
Data Type:
Lines
Line
Config
FileName
XML - example:
<?xml version="1.0" encoding="utf-8"?>
<nr1:MT_TP_TipoCambio_Detalle_ECC_Req xmlns:nr1="urn:erplatam/tipocambio:tp:ecc">
<Lines>
<Line>USDSOL0000000000003.10000013-09-200813-09-2008V</Line>
</Lines>
<Lines>
<Line>USDSOL0000000000002.50000014-09-200814-09-2008V</Line>
</Lines>
<Config>
<FileName>SIGMA_TCSAP_F081031.DAT.TXT</FileName>
</Config>
</nr1:MT_TP_TipoCambio_Detalle_ECC_Req>
Output - File, has 3 lines should have only 2:
USDSOL0000000000003.10000013-09-200813-09-2008V
USDSOL0000000000002.50000014-09-200814-09-2008V
FCC parameters:
RecordSet Structure: Lines,Config
Lines.fieldSeparator 'nl'
Lines.endSeparator 'nl'
Config.fieldSeparator 'nl'
Config.endSeparator 'nl'
Thanks in advance!

PI 7.11 - FCC Receiver Adapter

Hi
I've got a simple xml which i have to convert in a fixed length text file. Is it possible to convert it using FCC with following structure:
          <root>
               <data>
                    <record>
                         <name>john</name>
                         <surname>doe</surname>
                         <zip>12345</zip>
                         <city>abcd</city>
                    </record>
                    <record>
                         <name>bart</name>
                         <surname>simpson</surname>
                         <zip>131313</zip>
                         <city>springfield</city>
                    </record>
               </data>
          </root>
I did this conversion already with PI 7.0, but i removed the <data> element to get a simpler substructure. Is it also possible without removing this?
I found following entry [Re: File Adapter Reciver Side: FCC Convetion Problum in PI 7.1], but it didn't works for me. Any suggestions?
Thanks in advance
Michael

Hi,
Are you looking for a content conversion at teh Receiver adapter or the sender adapter?
If you have defined teh structure in ur Data type as u have mentioned then don't remove anything because ur source file would be containing the following structure itself.
If you are getting the XML structure at source
<root>
   <data>
      <record>
               <item1>
               <item2>
      </record>
   </data>
</root>
the follow the same structure at the receiver side as well. If u want to delete the data node at teh receiver side then delete at teh source side FCC as well.
Just try and let me know. I will help you out.
Thanks
Veeru

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

EMail Receiver adapter.

Similar Messages

Maybe you are looking for