File To Mail - Error in sender CC

Hi All,

I am trying out a File to mail scenario following the Blog /people/michal.krawczyk2/blog/2005/03/07/mail-adapter-xi--how-to-implement-dynamic-mail-address

I am getting the following error in the File Sender Comm Channel :

Mail: error occurred: com.sap.aii.af.mp.module.ModuleException caused by: com.sap.aii.messaging.srt.BubbleException: Failed to call the endpoint [null "null"]; nested exception caused by: java.io.IOException: no sender address specified

I could also see the payload is empty in the Receiver Mail CC

Now can anybody help getting me the mail ...

Thanks in advance

SAP Managed Tags:
SAP Process Integration

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (4)

hi all.

iam new to tds design.

now i just want to create tds for scenario like xi should taks data from sap R/3 TABLES and those fields i have to map with file.

which adapters we have to use in this scenario.

waiting for ur response.

regards.

varma

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

In MONI, Response --> Payloads --> Main Document . Click on this and you will be able to see the payload.

Regards,

Bhavesh

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

That is my agony I dont get a payload node

when I check Mail Reciever CC -- > Message Content ~~>Message Display tool~~> I see only this :

<?xml version="1.0" encoding="UTF-8" ?>

<ns1:Mail xmlns:ns1="http://sap.com/xi/XI/Mail/30" />

and the rest of the xml is not parsed ...

2) In the Reciever Mail CC if I change the Msg Protocol as XIALL and hardcode the Mail Attributes i get mails

and the error I pasted in the post is the last msg I get from my File sender CC ..

am I a bit clear now ?

This looks like some mapping issue.

Can you copy the payload ( file payload--incoming message) from MONI nad test your mapping with this message.

If the data comes out of mapping then there will be no issue. Check your mapping.

Regards,

Bhavesh

<?xml version="1.0" encoding="UTF-8" ?>

<ns1:Mail xmlns:ns1="http://sap.com/xi/XI/Mail/30" />

>>>>

i guess your mapping is not filling the data .. check your mapping.

In the Reciever Mail CC if I change the Msg Protocol as XIALL and hardcode the Mail Attributes i get mails

and the error I pasted in the post is the last msg I get from my File sender CC ..

am I a bit clear now ?

>>> untill your mapping fills the Mail XSD you will face probs in your mail CC.

Shabarish,

S, It Msg Mapping is failing

I get the following error now in moni :

RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:Mail. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target

My Input DT something like this ;

File_sendr_DT

Mail

Subject

From

Content

and Out put Data Type I have downloaded from Market place and disabled rest of the fields as per the blog

mapped Mail element in the input file to Mail element in the external definition

Map all the fields in the target.

Dont miss the Root node too.

Check if any of the mandatory fields are not mapped in the target side.

Also check if your source data coming in is of the struc. you have defined in XI.

Hi,

Goto SXMB_MONI and download the Input Payload and save it as XML file in ur desktop. Go to messahe mapping test tab and you wil find a XML icon click on it to load the xml from your desktop. See if it is loaded properly and then test the mapping.

Thanks,

Prakash

Hi All,

In the File sender adapter if I send an XML in this format <ns:Mail xmlns:ns="http://sap.com/xi/XI/Mail/30">

<Subject>Hello</Subject>

<From>sender@sender.com</From>

<To>receiver@receiver.com</To>

<Content_Type>text/plain; charset="ISO-8859-1";

name="MyFile.xml"</Content_Type>

</ns:Mail>

Then I am able to get a mail but In my scenario I get a CSV file So I created a data type Mail with the rest of the subelements but know how do I replicate the above structure in FCC . ie., How should my Recordset structure and parameter description should appear to achieve the above structure.

Kind Regards,

K.L.K

Hi,

First you need to define a data type like

DT_SourceFile

..Recordset

....Row

......Field1

......Field2

......Field3

The above is for the source structure and for the target download the mail XSD from this URL https://websmp205.sap-ag.de/~sapidb/012006153200000361852004E/ximail30_xsd.txt

and do the mapping form the source to the target.

Since source is a CSV file you need to go for content conversion.

You can refer this blogs for using mail package

/people/prasad.ulagappan2/blog/2005/06/07/mail-adapter-scenarios-150-sap-exchange-infrastructure

/people/michal.krawczyk2/blog/2005/03/07/mail-adapter-xi--how-to-implement-dynamic-mail-address

/people/community.user/blog/2006/09/07/email-reporting

You can refer this blog for reading CSV file

/people/sap.user72/blog/2005/01/06/how-to-process-csv-data-with-xi-file-adapter

Thanks,

Prakash

Hi,

WHat is the response message in MONI? Is it filled with the data?

Can you give the output in MONI here.

Also, can you confirm that the encoding in the mail adapter is base64 and mail package has been selected.

Regards,

Bhavesh

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Bhavesh,

I get a checkered flag in Moni ,

But the response has only SOAP header and Body with out payload , I Mail package is checked and base64 is selected ..

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Response

-->

- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">

<Trace level="1" type="T">Party normalization: sender</Trace>

<Trace level="1" type="T">Sender scheme external = XIParty</Trace>

<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>;

<Trace level="1" type="T">Sender party external =</Trace>

<Trace level="1" type="T">Sender party normalized =</Trace>

<Trace level="1" type="T">Party normalization: receiver</Trace>

<Trace level="1" type="T">Receiver scheme external =</Trace>

<Trace level="1" type="T">Receiver agency external =</Trace>

<Trace level="1" type="T">Receiver party external =</Trace>

<Trace level="1" type="T">Receiver party normalized =</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>

<Trace level="1" type="T">COMMIT is done by XMB !</Trace>

- <!-- ************************************

-->

- <!-- ************************************

-->

<Trace level="1" type="T">XMB entry processing</Trace>

<Trace level="1" type="T">system-ID = XIL</Trace>

<Trace level="1" type="T">client = 002</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PIAFUSER</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Message-GUID = 1DC20B0043D611DBC937000D60D4EDB5</Trace>

<Trace level="1" type="T">PLNAME = CENTRAL</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>

<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>

<Trace level="1" type="T">Queue name : XBTI0009</Trace>

<Trace level="1" type="T">Generated prefixed queue name = XBTI0009</Trace>

<Trace level="1" type="T">Schedule message in qRFC environment</Trace>

<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Going to persist message</Trace>

<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>

<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>

<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>

<Trace level="1" type="T">----

</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

<Trace level="1" type="T">system-ID = XIL</Trace>

<Trace level="1" type="T">client = 002</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PIAFUSER</Trace>

<Trace level="1" type="T">----

</Trace>

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">

<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>

<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>

- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">Cache Content is up to date</Trace>

</Trace>

- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">Cache Content is up to date</Trace>

</Trace>

- <!-- ************************************

-->

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <!-- ************************************

-->

<Trace level="1" type="T">number of receivers: 1</Trace>

<Trace level="1" type="T">Single-receiver split case</Trace>

<Trace level="1" type="T">Post-split internal queue name = XBTO3___0001</Trace>

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Persisting single message for post-split handling</Trace>

<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>

<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>

<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>

<Trace level="1" type="T">----

</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

<Trace level="1" type="T">system-ID = XIL</Trace>

<Trace level="1" type="T">client = 002</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PIAFUSER</Trace>

<Trace level="1" type="T">----

</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>

<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>

<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>

- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">

<Trace level="1" type="T">Interface Mapping http://sap.com/xi/XI/Mail/30 GK_File2Mail_IM</Trace>

</Trace>

- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

</Trace>

- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">

- <!-- ************************************

-->

- <!-- ************************************

-->

- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">

</Trace>

</Trace>

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Async processing completed OK.</Trace>

<Trace level="1" type="T">system-ID = XIL</Trace>

<Trace level="1" type="T">client = 002</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PIAFUSER</Trace>

<Trace level="1" type="T">----

</Trace>

- <!-- ************************************

-->

</SAP:Trace>

<b>no sender address specified</b>

>>>

Check your adapter configuration.

Note: You sud have a sender file adapter and a receiver mail adapter

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Ask a Question

Top Q&A Solution Author

User

Count