Sender mail adpater

Hi,
I am doing a sender mail adpater scenario where XI will pick the data from the attachment of an email and use it in the payload.
Please provide me info about the configuration od CC and how to pick attachement. Also, the name of the attachemnt file can change so what is to be writtten in module configuration ?
Priya

Hi,
Refer this blog
/people/michal.krawczyk2/blog/2005/12/18/xi-sender-mail-adapter--payloadswapbean--step-by-step
Do configuration accordingly your attachment will be read as main payload.
Give a specific file name with extension. Even if the filename change it ll read the content of attachment.
Regards,
Sakthi

Similar Messages

Sender Mail adapter : Delete after reaD

I am working on a sender mail adpater. Now, my requirement is that once the XI reads the attachement of an unread mail, the status of the mail should be set to read.
In the sender mail adpater, there is a check box available :
Delete the mail once it has been read.
Do you suggest this will help or if you have any appraoch, please let me know.

Hi Priya,
I dont know about how to make the mail status unread after reading attachment but just for your information please be careful while using mail adapter on sender side as it affects performance and also it may delete all your inbox mails and that check box Delete the mail once it has been read. wont solve your problem.
Regards,
Amit.

Sender Mail Adapter ASMA issue - due to limitation of length upto 200 only.

Hi,
I have a scenario where i have to pull the emails from the mail server using sender mail adpater with XIPAYLOAD as message protocol.
Also i am setting the "Set Adapter Setting Messgae Attributes" for retrieving values form header such as SHeaderCC etc..
I use dynamic config in the mapping to get those values.
The Scenario works fine, but when the cc length is more that 200, i am not getting any value in the inbound messgae to mapping.
In SAP help, it says, "The length of the attribute value is defined by the XI message protocol. Values can be a maximum of 200 characters long. If, for example, you assign longer values in the mapping or adapter modules then this can lead to processing errors at runtime or the values are shortened to 200 characters. This shortening can also lead to a processing error. The processing error that occurs depends on the components that access the attributes."
In my case, the cc is empty if the length is more that 200.
Any idea how to tackle this issue? I think even writng the sender adapter module wont solve the issue as the any attribute lenght inthe message ehader cannot be greater than 200.
All ideas are welcome.
Regards,
Manikandan R

Hi
As you said this error will occur when the mail messages with header attributes containing the values more than 200 chars. By including the adapter module u2013 DynamicConfigurationBean (valuelength) in the configuration part - Advanced you can avoid this error.
Processing Sequence:
AF_Modules/DynamicConfigurationBean
Module Configuration
dc.valueLength 200
Note:
This module will remove the header attributes if the value is > 200.
Regards
Ramg

PayloadSwapBean: Sender mail adapter

Does any codeing is required after adding payloadswapbean in the adpater module in sender mail adpter ?

Hi,
There is some possibility of PayloadSwapBean error,
it may come
1. XI 3.0 Adapter Framework provides a standard module for replacing the
application payload with one of the other payloads in the message. The
new application payload can be selected based on its payload attributes
(payload-name, payload-description) or its content attributes
(content-type, content-disposition, content-description, etc).
2. The payload swapping module (PayloadSwapBean) in the XI 3.0 Adapter Framework may not find the new main payload if this payload is placed at the first entry (assuming the old main payload is placed not at the first entry).
This problem occurs, when one uses two swapping modules to switch back and forth the main payload. For example, when the first swapping module is used to switch the main payload typically placed at the first entry to another one, this new main payload is processed using another module, and then the second swapping module is used to switch back the main payload to the original payload placed at the first entry.
When this problem occurs, the message monitor shows
Swap: no matching payload found
So please check or set
1. [Module Name]
AF_Modules/PayloadSwapBean
[Module Parameters]
The following parameters are used for this module
swap.keyName          the name of a supported attribute.
swap.keyValue         the value of a partial string that is required
                        to appear.
The supported attributes (swap.keyName) include the payload attributes
such as payload-name, payload-description and any content attributes
such as content-type, content-disposition, content-description, etc.
2. Import the appropriate archive for SAP Exchange Infrastructure XI 3.0 as described in the NetWeaver 04 Support Package stack guide.
The archive and the guide are available on the SAP Service Marketplace
under the link "SP-stacks -> SAP NetWeaver -> SAP NetWeaver 04" ie
Apply patch
XI ADAPTER FRAMEWORK 3.0
Support Package 12, patch Level 3 (SAPXIAF12P_3.SCA)
or
Support Package 13, patch Level 1 (SAPXIAF13P_1.SCA)
if you are using higher, then check out for the first solution.
Also refer this sap note for other details. SAP Note 746393.
Hope this will help you.
regards
Aashish Sinha
PS : reward points if helpful

Mail Adapter Send Mail with Attachment

Hi all,
I'm doing some tests on XI and implemented a little scenario, that send Mails.
So this works fine, but I want to have the content as the content of the mail (no prob) and a attachment with a little more information for the user in a plain text file.
I tried to code it with content-type multipart and all these stuff, but didn't come to a solution.
Some one solved such a scenario already and can help?
I also read some thread on SDN, but no solution. Perhaps its to simple
Thanx
regards
Olli

Oliver,
We have found the solution for you.
You should configure the mail adapter with 'use the mail adpater' and 'keep attachments'.
Create an XML file conform the XML structure provide by SAP
The mail package should look like this:
<?xml version="1.0" encoding="utf-8"?>
<ns:MT_Mail_Sent xmlns:xi="http://sap.com/xi/XI/Mail/30">
 <xi:Mail>
 <Subject>Item</Subject>
 <From>[email protected]</From>
 <To>[email protected]</To>
 <Content_Type>multipart/mixed; boundary="AaBb--984dfgeSSd3532"</Content_Type>
 <Content_Disposition>attachment</Content_Disposition>
 <Content>
AaBb984dfgeSSd3532
Content-Type: text/plain
Hello, this is sample data.
AaBb984dfgeSSd3532
Content-Type: text/plain;name="CSV_data.csv"
Order number;Item number;description<xsl:text>
</xsl:text>
 <xsl:for-each select="Article_line">
 <xsl:value-of select="Ord_nmbr"/>;<xsl:value-of select="Item_nmbr"/>;<xsl:value-of select="Description<xsl:text>
</xsl:text></xsl:for-each>
AaBb984dfgeSSd3532
Content-Type: text/plain;name="TXT_data.txt"
Order number;Item number;description<xsl:text>
</xsl:text>
 <xsl:for-each select="Article_line">
 <xsl:value-of select="Ord_nmbr"/>;<xsl:value-of select="Item_nmbr"/>;<xsl:value-of select="Description<xsl:text>
</xsl:text></xsl:for-each>
AaBb984dfgeSSd3532
 </Content>
 </xi:Mail>
</ns:MT_Mail_Sent>
In the above example you should have some content and 2 attachments (1 csv file and 1 txt file).
After each break (AaBb984dfgeSSd3532) specify again the 'Content-Type'.
Good luck
Regards
Ron

File to Idoc .If order is their need to send mail

Hi All,
I have scenario like this.
Sending file (order) to SAP -IDoc
I using RFC lookup .There is funtion module which has been developed in SAP R/3 it contains 5 import parameters and return SUBRC.
If the result is subrc = 4
This is the normal situation and the order / idoc should be
generated as normally.
If the result is subrc = 0
Now we are in a situation where we earlier have received this order.
Instead of generation an IDOC, an email must be send to respective persons with contents
SUBJECT: We have already received this EDI -order before.
And the mail should contain following:
We have already received this EDI-order before.
Purchase order no: <value of purchase order no>
Sold-to: <value of sold-to>
Salesorganisation: <value of salgsorganisation>
Distribution channel: <value of distribution channel>
Division: <value of division>
Note : BPM not recomended
Thanks
MMV

Hi,
Check the following link
/people/michal.krawczyk2/blog/2005/12/18/xi-sender-mail-adapter--payloadswapbean--step-by-step
it is possible to configure the mail adpater to send attachemnts without any ABAP coding. Just check out these
blogs by michal that deal with the mail adapter,
/people/michal.krawczyk2/blog/2005/11/23/xi-html-e-mails-from-the-receiver-mail-adapter
/people/michal.krawczyk2/blog/2005/03/07/mail-adapter-xi--how-to-implement-dynamic-mail-address
You can also check these links on SAP help for configuring the mail adapter,
http://help.sap.com/saphelp_nw04/helpdata/en/ad/bf93409c663228e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/23/c093409c663228e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/6b/4493404f673028e10000000a1550b0/content.htm
Please reward points if it helps
Thanks
Vikranth

Auto Population of Email Definition fields while sending mails to user

Hi,
I have the requirement that after a resource object has been provisioned to an user, a mail should be sent to him for confirmation.
I am able to successfully send mails to users after the resource object has been provisioned to him by making the configuation settings in the OIM system.
I have made use of a Resource Object , Resource Form , IT resource of type mail server , Email definition etc.
The point is while provisioning the resource object I am populating the User Defined Fields. These fields are visible at the xlWebApp console through the resource form. I am populating these fields while requesting the resource through the xlWebAPp UI.
Now i need to send mails to the user with these fields populated with the values that i m providing while provisioning the resource. Currently my sent mails just consist of plain email definition with a subject line and a body text.
Please let me know how can i include the values in the populated fields in the body of the mail through settings in OIM.
Since i m a QA person i cannot go ahead and write code for creating an adpater for this task. Kindly let me know is there any way by which I can do the same through config settings in OIM.
Thanks in advance.
Pooja.

Hello,
Actually i have a resource object as "Laptop" suppose, so for me the user defined fields are Laptop_type, RAM value, ROM Value and Emp ID.
These fields are made visible as UDF through Pre-pop adapters and all the other required settings.
While provisioning the same in the xlWebApp console I am populating them.
The resource form for me (Form Designer for the resource object) is made visible and i am filling in values while provisioning.
Now while sending the mails these values should reflected in the mail body for the fields.
Eg: Subject [hi] Mail body [ The following resource has been provisioned. Laptop_type : Dell, RAM value: 512, ROM value: 40, EMP ID: 123] where these values are filled in the resource form while provisioning the resource object.
Pleased let me know how can i send such mails through config settings in OIM. Right now my mail simply looks like
Eg: Subject [hi] Mail Body [The resource has been provisioned to you]
Thanks again.
Pooja.

How to send Mail in case of Output Determination - Transmission medium 5

Dear Friends,
I have a below requirement.
- Create custom output type having Transmission medium 5, which triggers on creation of order.
- Write driver program attached to that output type that sends e-mail to the person who has created the order.
- Mail contain information regarding pricing for individual line item wise.
I have gone through many posts but not sure about process of generate the mail in case of Transmission medium 5.
My query is:
Do we require to write FM (SO_NEW_DOCUMENT_ATT_SEND_API1) to send e-mail to respective person or it will take care by system (Transmission medium 5)?
If FM not required then how can we write code that triggers the mail to specific mail ID?
Nilay

Yes, for your custom requirement you will have to create a Z report.
LIke your requirement must be to put something specific in mail body or attach something with mail. All this will not be catered by the standard report maintained against your output type and transmission medium.
As i understand for any output type a message is triggerd and stored in database table (like NAST) and then these requests are picked by standard report (like RSNAST00). These reports then in return call the Program/form maintained against the ouptut type and transmission medium (table TNAPR).
So i would suggest that create a custom report and use the FM for sending mails. These FMs are pretty simple to use. Find a sample code in the below link:
[http://wiki.sdn.sap.com/wiki/display/ABAP/SendExternalMailwithattachment]

Sending mail with multiple attachment

hi.
i want to send mail with multiple attachment.
i m succeed in sending multiple attachment but the second pdf is not open.
its given error like "This file is damaged and could not be open.
pls check my code. and
give the solution....
point should be assured...........
hope all u r understand my problem..
& tell me where is i m missing something.
REPORT YSDPASALE1_MAIL LINE-SIZE 110.
data : year_month(6) type c.
data : from_date like sy-datum,to_date like sy-datum.
INITIALIZATION.
year_month = sy-datum+0(6).
CONCATENATE year_month '01' into from_date.
to_date = sy-datum.
ranges : temp for mkpf-budat.
temp-low = from_date.
temp-high = to_date.
append temp to temp.
DATA: P_JOBCNT LIKE TBTCJOB-JOBCOUNT,
 jobname like TBTCJOB-JOBNAME,
 L_RELEASE(1) TYPE c.
CONSTANTS : l_c_device(4) VALUE 'LOCL'.
DATA : t type i value 0.
DATA : p_email1 like somlreci1-receiver,
 p_sender LIKE somlreci1-receiver.
Data Declaration
DATA: gd_recsize TYPE i,gd_recsize1 TYPE i.
Spool IDs
TYPES: BEGIN OF t_tbtcp.
 INCLUDE STRUCTURE tbtcp.
TYPES: END OF t_tbtcp.
DATA: it_tbtcp TYPE STANDARD TABLE OF t_tbtcp INITIAL SIZE 0,
 wa_tbtcp TYPE t_tbtcp.
Job Runtime Parameters
DATA: gd_eventid LIKE tbtcm-eventid,
 gd_eventparm LIKE tbtcm-eventparm,
 gd_external_program_active LIKE tbtcm-xpgactive,
 gd_jobcount LIKE tbtcm-jobcount,
 gd_jobname LIKE tbtcm-jobname,
 gd_stepcount LIKE tbtcm-stepcount,
 gd_error TYPE sy-subrc,
 gd_reciever TYPE sy-subrc.
DATA: w_recsize TYPE i.
DATA: gd_subject LIKE sodocchgi1-obj_descr,
 it_mess_bod LIKE solisti1 OCCURS 0 WITH HEADER LINE,
 it_mess_att LIKE solisti1 OCCURS 0 WITH HEADER LINE,
 it_mess_att1 LIKE solisti1 OCCURS 0 WITH HEADER LINE,
 it_mess_att2 LIKE solisti1 OCCURS 0 WITH HEADER LINE,
 gd_sender_type LIKE soextreci1-adr_typ,
 gd_attachment_desc TYPE so_obj_nam,
 gd_attachment_desc1 TYPE so_obj_nam,
 gd_attachment_name TYPE so_obj_des,
 gd_mtitle LIKE sodocchgi1-obj_descr.
Spool to PDF conversions
DATA: gd_spool_nr LIKE tsp01-rqident,
 gd_destination LIKE rlgrap-filename,
 gd_bytecount LIKE tst01-dsize,
 gd_buffer TYPE string.
CONSTANTS: c_dev LIKE sy-sysid VALUE 'DEV',
 c_no(1) TYPE c VALUE ' ',
 c_device(4) TYPE c VALUE 'LOCL'.
Binary store for PDF
DATA: BEGIN OF it_pdf_output OCCURS 0.
 INCLUDE STRUCTURE tline.
DATA: END OF it_pdf_output.
DATA: BEGIN OF mailstr OCCURS 0,
 p_email like somlreci1-receiver,
 END OF mailstr.
DATA: mailtab like STANDARD TABLE OF mailstr WITH HEADER LINE.
DATA: ypp18tab like STANDARD TABLE OF mailstr WITH HEADER LINE,
 ymis008tab like STANDARD TABLE OF mailstr WITH HEADER LINE,
 ysd15tab like STANDARD TABLE OF mailstr WITH HEADER LINE,
 ymis10tab like STANDARD TABLE OF mailstr WITH HEADER LINE.
SUBMIT YSDPASALE1 with bdt in temp
 to sap-spool
 with line-size = '255'
 with KEEP_IN_SPOOL = 'X'
 with IMMEDIATELY = ' '
 WITHOUT SPOOL DYNPRO
 AND RETURN
 NEW-PAGE PRINT ON
 DESTINATION l_c_device
 IMMEDIATELY ' '
 KEEP IN SPOOL 'X'
 NEW LIST IDENTIFICATION 'X'
 NO DIALOG.
 new-page print off.
IF sy-batch EQ 'X'.
 PERFORM get_job_details.
 PERFORM obtain_spool_id.
 PERFORM convert_spool_to_pdf.
 select yemail as p_email into CORRESPONDING FIELDS OF TABLE ymis008tab
 from ymail
 where ytcode = 'YMIS008'.
ELSE.
 SKIP.
 WRITE:/ 'Program must be executed in background in-order for spool & mail sending',
 'request to be created.'.
ENDIF.
wait up to 3 seconds.
submit YSD_MONTHLY_SALES
 USING SELECTION-SET 'MAIL'
 to sap-spool
 with KEEP_IN_SPOOL = 'X'
 with IMMEDIATELY = ' ' "SPACE
 WITHOUT SPOOL DYNPRO
 AND RETURN
 NEW-PAGE PRINT ON
 DESTINATION l_c_device
 IMMEDIATELY ' '
 KEEP IN SPOOL 'X'
 NEW LIST IDENTIFICATION 'X'
 NO DIALOG.
 new-page print off.
 IF sy-batch EQ 'X'.
 gd_attachment_desc1 = 'YMIS10'.
 gd_mtitle = 'Monthly Sales Report'.
 PERFORM get_job_details.
 PERFORM obtain_spool_id.
 PERFORM convert_spool_to_pdf1.
 loop at it_mess_att.
 move it_mess_att1 to it_mess_att.
 APPEND it_mess_att.
 endloop.
 APPEND LINES OF it_mess_att1 to it_mess_att.
 free it_mess_att1.
 it_mess_att[] = it_mess_att1[].
 insert LINES OF it_mess_att1 into it_mess_att.
 APPEND LINES OF it_mess_att2 to it_mess_att .
 insert LINES OF it_mess_att1 into it_mess_att.
 insert LINES OF it_mess_att2 into it_mess_att.
 loop at ymis008tab into mailstr.
 p_email1 = mailstr-p_email.
 p_email1 = '[email protected]'.
 PERFORM process_email.
 endloop.
 clear mailstr.
 wait up to 5 seconds.
 SUBMIT rsconn01 WITH mode = 'INT'
 WITH output = 'X'
 AND RETURN.
ELSE.
 SKIP.
ENDIF.
 FORM obtain_spool_id *
FORM obtain_spool_id.
CHECK NOT ( gd_jobname IS INITIAL ).
CHECK NOT ( gd_jobcount IS INITIAL ).
SELECT * FROM tbtcp
 INTO TABLE it_tbtcp
 WHERE jobname = gd_jobname
 AND jobcount = gd_jobcount
 AND stepcount = gd_stepcount
 AND listident <> '0000000000'
 ORDER BY jobname
 jobcount
 stepcount.
READ TABLE it_tbtcp INTO wa_tbtcp INDEX 1.
IF sy-subrc = 0.
 message s004(zdd) with gd_spool_nr.
 gd_spool_nr = wa_tbtcp-listident.
 MESSAGE s004(zdd) WITH gd_spool_nr.
ELSE.
 MESSAGE s005(zdd).
ENDIF.
ENDFORM.
 FORM get_job_details *
FORM get_job_details.
Get current job details
CALL FUNCTION 'GET_JOB_RUNTIME_INFO'
 IMPORTING
 eventid = gd_eventid
 eventparm = gd_eventparm
 external_program_active = gd_external_program_active
 jobcount = gd_jobcount
 jobname = gd_jobname
 stepcount = gd_stepcount
 EXCEPTIONS
 no_runtime_info = 1
 OTHERS = 2.
ENDFORM.
 FORM convert_spool_to_pdf *
FORM convert_spool_to_pdf.
CALL FUNCTION 'CONVERT_ABAPSPOOLJOB_2_PDF'
 EXPORTING
 src_spoolid = gd_spool_nr
 no_dialog = c_no
 dst_device = c_device
 IMPORTING
 pdf_bytecount = gd_bytecount
 TABLES
 pdf = it_pdf_output
 EXCEPTIONS
 err_no_abap_spooljob = 1
 err_no_spooljob = 2
 err_no_permission = 3
 err_conv_not_possible = 4
 err_bad_destdevice = 5
 user_cancelled = 6
 err_spoolerror = 7
 err_temseerror = 8
 err_btcjob_open_failed = 9
 err_btcjob_submit_failed = 10
 err_btcjob_close_failed = 11
 OTHERS = 12.
CHECK sy-subrc = 0.
Transfer the 132-long strings to 255-long strings
LOOP AT it_pdf_output.
 TRANSLATE it_pdf_output USING ' ~'.
 CONCATENATE gd_buffer it_pdf_output INTO gd_buffer.
ENDLOOP.
TRANSLATE gd_buffer USING '~ '.
DO.
 it_mess_att = gd_buffer.
 APPEND it_mess_att.
 SHIFT gd_buffer LEFT BY 255 PLACES.
 IF gd_buffer IS INITIAL.
 EXIT.
 ENDIF.
ENDDO.
ENDFORM.
FORM convert_spool_to_pdf1.
CALL FUNCTION 'CONVERT_ABAPSPOOLJOB_2_PDF'
 EXPORTING
 src_spoolid = gd_spool_nr
 no_dialog = c_no
 dst_device = c_device
 IMPORTING
 pdf_bytecount = gd_bytecount
 TABLES
 pdf = it_pdf_output
 EXCEPTIONS
 err_no_abap_spooljob = 1
 err_no_spooljob = 2
 err_no_permission = 3
 err_conv_not_possible = 4
 err_bad_destdevice = 5
 user_cancelled = 6
 err_spoolerror = 7
 err_temseerror = 8
 err_btcjob_open_failed = 9
 err_btcjob_submit_failed = 10
 err_btcjob_close_failed = 11
 OTHERS = 12.
CHECK sy-subrc = 0.
Transfer the 132-long strings to 255-long strings
LOOP AT it_pdf_output.
 TRANSLATE it_pdf_output USING ' ~'.
 CONCATENATE gd_buffer it_pdf_output INTO gd_buffer.
ENDLOOP.
TRANSLATE gd_buffer USING '~ '.
DO.
 it_mess_att1 = gd_buffer.
 APPEND it_mess_att1.
 SHIFT gd_buffer LEFT BY 255 PLACES.
 IF gd_buffer IS INITIAL.
 EXIT.
 ENDIF.
ENDDO.
ENDFORM.
 FORM process_email *
FORM process_email.
DESCRIBE TABLE it_mess_att LINES gd_recsize.
DESCRIBE TABLE it_mess_att1 LINES gd_recsize1.
CHECK gd_recsize > 0 or gd_recsize1 > 0.
PERFORM send_email." USING p_email1.
perform send_email using p_email2.
ENDFORM.
 FORM send_email *
--> p_email *
FORM send_email." USING p_email.
CHECK NOT ( p_email IS INITIAL ).
REFRESH it_mess_bod.
Default subject matter
gd_subject = 'Subject'.
gd_attachment_desc = gd_attachment_desc1 .
gd_attachment_desc = 'YPP18 - Daily Highlights'.
CONCATENATE 'attach_name' ' ' INTO gd_attachment_name.
it_mess_bod = 'Dear Sir,'.
APPEND it_mess_bod.
it_mess_bod = ' '.
APPEND it_mess_bod.
it_mess_bod = ' '.
APPEND it_mess_bod.
it_mess_bod = 'kindly find the attached document'.
APPEND it_mess_bod.
it_mess_bod = ' '.
APPEND it_mess_bod.
it_mess_bod = 'Do not reply on this mail, It is generated from SAP'.
APPEND it_mess_bod.
it_mess_bod = ' '.
APPEND it_mess_bod.
it_mess_bod = ' '.
APPEND it_mess_bod.
it_mess_bod = 'Regards,'.
APPEND it_mess_bod.
it_mess_bod = 'Arpit Shah'.
APPEND it_mess_bod.
If no sender specified - default blank
IF p_sender EQ space.
 gd_sender_type = space.
ELSE.
 gd_sender_type = 'INT'.
ENDIF.
Send file by email as .xls speadsheet
PERFORM send_file_as_email_attachment
 tables it_mess_bod
 it_mess_att
 it_mess_att1
 using "p_email
 gd_mtitle
 'Testing mail generated from SAP'
 'Daily Highlights Abstract Report - YPP18'
 'PDF'
 gd_attachment_name
 gd_attachment_desc
 p_sender
 gd_sender_type
 changing gd_error
 gd_reciever.
ENDFORM.
*& Form SEND_FILE_AS_EMAIL_ATTACHMENT
 Send email
FORM send_file_as_email_attachment tables it_message
 it_attach
 it_attach1
 using "p_email
 p_mtitle
 p_format
 p_filename
 p_attdescription
 p_sender_address
 p_sender_addres_type
 changing p_error
 p_reciever.
DATA: ld_error TYPE sy-subrc,
 ld_reciever TYPE sy-subrc,
 ld_mtitle LIKE sodocchgi1-obj_descr,
 ld_email LIKE somlreci1-receiver,
 ld_format TYPE so_obj_tp ,
 ld_attdescription TYPE so_obj_nam ,
 ld_attfilename TYPE so_obj_des ,
 ld_sender_address LIKE soextreci1-receiver,
 ld_sender_address_type LIKE soextreci1-adr_typ,
 ld_receiver LIKE sy-subrc.
data: t_packing_list like sopcklsti1 occurs 0 with header line,
 t_contents like solisti1 occurs 0 with header line,
 t_receivers like somlreci1 occurs 0 with header line,
 t_attachment like solisti1 occurs 0 with header line,
 t_object_header like solisti1 occurs 0 with header line,
 w_cnt type i,
 w_sent_all(1) type c,
 w_doc_data like sodocchgi1,w_doc_data1 like sodocchgi1.
ld_email = p_email.
ld_mtitle = p_mtitle.
ld_format = p_format.
ld_attdescription = p_attdescription.
ld_attfilename = p_filename.
ld_sender_address = p_sender_address.
ld_sender_address_type = p_sender_addres_type.
Fill the document data.
w_doc_data-doc_size = 1.
Populate the subject/generic message attributes
w_doc_data-obj_langu = sy-langu.
w_doc_data-obj_name = 'SAPRPT'.
w_doc_data-obj_descr = ld_mtitle .
w_doc_data-sensitivty = 'F'.
Fill the document data and get size of attachment
CLEAR w_doc_data.
READ TABLE it_attach INDEX w_cnt.
w_doc_data-doc_size =
 ( w_cnt - 1 ) * 255 + STRLEN( it_attach ).
w_doc_data1-doc_size =
 ( w_cnt - 1 ) * 255 + STRLEN( it_attach ).
w_doc_data-obj_langu = sy-langu.
w_doc_data-obj_name = 'SAPRPT'.
w_doc_data-obj_descr = ld_mtitle.
w_doc_data-sensitivty = 'F'.
CLEAR t_attachment.
REFRESH t_attachment.
t_attachment[] = it_attach[].
For 2nd Attachments
* Fill the document data and get size of attachment
CLEAR w_doc_data.
READ TABLE it_attach1 INDEX w_cnt.
w_doc_data-doc_size = w_doc_data1-doc_size +
 ( w_cnt - 1 ) * 255 + STRLEN( it_attach1 ).
w_doc_data-obj_langu = sy-langu.
w_doc_data-obj_name = 'SAPRPT'.
w_doc_data-obj_descr = ld_mtitle.
w_doc_data-sensitivty = 'F'.
CLEAR t_attachment.
REFRESH t_attachment.
APPEND LINES OF it_attach1 to t_attachment.
t_attachment[] = it_attach1[].
APPEND LINES OF it_attach1 to t_attachment.
Describe the body of the message
CLEAR t_packing_list.
REFRESH t_packing_list.
t_packing_list-transf_bin = space.
t_packing_list-head_start = 1.
t_packing_list-head_num = 0.
t_packing_list-body_start = 1.
DESCRIBE TABLE it_message LINES t_packing_list-body_num.
t_packing_list-doc_type = 'RAW'.
APPEND t_packing_list.
Create attachment notification
t_packing_list-transf_bin = 'X'.
t_packing_list-head_start = 1.
t_packing_list-head_num = 0.
t_packing_list-body_start = 1.
DESCRIBE TABLE t_attachment LINES t_packing_list-body_num.
DESCRIBE TABLE it_mess_att LINES t_packing_list-body_num.
DESCRIBE TABLE it_attach LINES t_packing_list-body_num.
t_packing_list-doc_type = ld_format.
t_packing_list-obj_descr = 'YMIS008'."ld_attdescription.
t_packing_list-obj_name = 'YMIS008'."ld_attfilename.
t_packing_list-doc_size = t_packing_list-body_num * 255.
APPEND t_packing_list.
clear t_packing_list.
for 2 attachments
data : a type i,b type i.
 a = t_packing_list-body_num.
t_packing_list-transf_bin = 'X'.
t_packing_list-head_start = 1.
t_packing_list-head_num = 0.
t_packing_list-body_start = a + 1. "1
DESCRIBE TABLE it_mess_att1 LINES t_packing_list-body_num.
DESCRIBE TABLE it_attach1 LINES t_packing_list-body_num.
t_packing_list-doc_type = ld_format.
t_packing_list-obj_descr = 'YMIS10'."ld_attdescription.
t_packing_list-obj_name = 'YMIS10'."ld_attfilename.
t_packing_list-doc_size = t_packing_list-body_num * 255.
APPEND t_packing_list.
a = t_packing_list-body_num.
clear t_packing_list.
* Create attachment notification
t_packing_list-transf_bin = 'X'.
t_packing_list-head_start = 1.
t_packing_list-head_num = 1.
t_packing_list-body_start = a + 1.
t_packing_list-body_num = t_packing_list-body_num + 1.
DESCRIBE TABLE it_mess_att1 LINES t_packing_list-body_num.
t_packing_list-body_num = a + t_packing_list-body_num .
t_packing_list-doc_type = ld_format.
t_packing_list-obj_descr = 'YMIS10'."ld_attdescription.
t_packing_list-obj_name = 'YMIS10'."ld_attfilename.
t_packing_list-doc_size = t_packing_list-body_num * 255.
APPEND t_packing_list.
Add the recipients email address
CLEAR t_receivers.
REFRESH t_receivers.
loop at ymis008tab into mailstr.
t_receivers-receiver = mailstr-p_email. "ld_email.
t_receivers-receiver = p_email1.
t_receivers-rec_type = 'U'.
t_receivers-com_type = 'INT'.
t_receivers-notif_del = 'X'. "X "Read Acknoledgement
t_receivers-notif_ndel = 'X'.
APPEND t_receivers.
endloop.
 CALL FUNCTION 'SO_DOCUMENT_SEND_API1'
 EXPORTING
 document_data = w_doc_data
 put_in_outbox = 'X'
 sender_address = ld_sender_address
 sender_address_type = ld_sender_address_type
 commit_work = 'X'
 IMPORTING
 sent_to_all = w_sent_all
 TABLES
 packing_list = t_packing_list
 contents_bin = t_attachment
 contents_txt = it_message
 receivers = t_receivers
 EXCEPTIONS
 too_many_receivers = 1
 document_not_sent = 2
 document_type_not_exist = 3
 operation_no_authorization = 4
 parameter_error = 5
 x_error = 6
 enqueue_error = 7
 OTHERS = 8.
Populate zerror return code
ld_error = sy-subrc.
Populate zreceiver return code
LOOP AT t_receivers.
 ld_receiver = t_receivers-retrn_code.
ENDLOOP.
ENDFORM.
Rgds.
Arpit

Hi Arpit,
Take a look at the documentation of FM 'SO_DOCUMENT_SEND_API1' for parameter PACKING_LIST. I think you should set t_packing_list-head_num to a different value than 0 for the second attachment.
Regards,
John.

Sender Mail Adapter

Hi,
I am working on Sender Mail Adapter. I have done the total configuration but unable to sucess the scenarios. In the CC monitoring, it is saying that "Not Intialised" Even though i send and receive the messages from My Lotus Notes Inbox. I activated all the objects.
I have done the following examples:
Transport Protocal: POP3
Message Protocal: XIALL
Given the URL and UserId and PWD also
Poll Intevel: 1 (Mins)
Adapter Status: Active
Please help to me solve this problem. I already raised the one more thread today but didn't get solutions.
Note: Do i need to do any setting from the Lotus notes(Mail Server) to diver my messages.
Thanks in Advance,
I found the problem with SMTP Address. Can i use the SMTP Url for POP3 or IMP4 protocal. Is there any thing else because if i use the Same SMTP Address, it is giving exception
Best Regards,
Vijay
Message was edited by:
 Gangisetty Vijaya Bhaskarudu
Message was edited by:
 Gangisetty Vijaya Bhaskarudu

Hi Gangisetty,
 SMTP is the out going server(for sending mails out) while POP3 is the in coming(receiving mails) server. So for a sender channel, you need to use the POP server details not SMTP.
cheers
danus

Sender Mail Adapter - forcing content as an attachement

Hi all,
We are using the Sender Mail Adapter to pull emails from the inboxes of some users of an exchange server. We use the Mail Package option.
We have noticed that the content of the emails are by-default added as attachments when there are no real attachments to the emails. However the content is not added as an attachment when one or more attachments are present in these emails.
Is there a way of forcing the Sender Mail Adapter to always add the content as an attachment and keeping the other attachments as well? and of course maintain the Mail Package message type as the main payload...?
Many thanks,
Aldo

Hi Stefan,
Thanks for your reply. I am glad to hear that I am wrong again )
In your opinion is it possible to force the Outlook Exchange server to add the content attachment every time? I mean by doing some configuration on it...?
The reason why we would like to do this is because when - in the content tag of a Mail Package message - we have MIME message parts that are of content-type text/html we are having problems in decoding the html back to a readable format.
To do this we use the apache QuotedPrintableCodec Java class.
This works fine when the content type of the message is just text/plain but we get an exception when we try with text/html.
The exception we get is:
org.apache.commons.codec.DecoderException: Invalid URL encoding: not a valid digit (radix 16): 13
I don't know if this is because of the two character sets we have in the payload (utf-8 and iso-8859-1) or if it is for other reasons...
If you could help me figure out how to forward any HTML email to another system in a readable format it would be great.
Thanks for your support,
Aldo

Sender Mail Adapter Configuration - Process Multiple Attachments

Dear sirs,
I need to process several attachments at the same mail message as individual payloads.
In default configuration of sender mail adapter only the body of message is used as payload.
So I added PayloadSwapBean Module at Processing Sequence and it processed the attachment I set in Module Configuration. I'm not able to process all attachments available, just one attachment is sent to PI pipeline.
How can I process all attachments of a single mail message?
Thank you in advance.
Fabio Purcino

Hi Jose,
We are trying to implement reading multiple attachment in sender mail adapter.
Our Requirement is : Reading a mail having multiple .xls files. This should be read and converted to payload .
package multiswap;
//import com.sap.aii.adapter.xi.ms.XIMessage;
import com.sap.aii.af.lib.mp.module.*;
import com.sap.aii.af.lib.trace.Trace;
import com.sap.aii.af.sdk.xi.mo.Message;
import com.sap.aii.af.sdk.xi.mo.MessageContext;
import com.sap.aii.af.sdk.xi.mo.xmb.XMBMessageOperator;
import com.sap.aii.af.sdk.xi.mo.xmb.XMBPayload;
import com.sap.aii.af.sdk.xi.util.PayloadType;
import com.sap.aii.af.service.auditlog.Audit;
import com.sap.aii.af.service.cpa.*;
import com.sap.engine.interfaces.messaging.api.MessageDirection;
import com.sap.engine.interfaces.messaging.api.MessageKey;
import com.sap.engine.interfaces.messaging.api.Payload;
import com.sap.engine.interfaces.messaging.api.auditlog.AuditLogStatus;
import java.util.Hashtable;
import java.util.Iterator;
import java.util.Locale;
import javax.ejb.*;
public class MultiSwapRead
 implements SessionBean, Module
 private static final String VERSION_ID = "$Id: //tc/xpi.af/NW731EXT_07_REL/src/_af_application_ejb_module/ejbm/api/com/sap" +
"/aii/af/app/modules/PayloadSwapBean.java#1 $"
 private static final Trace TRACE = new Trace("$Id: //tc/xpi.af/NW731EXT_07_REL/src/_af_application_ejb_module/ejbm/api/com/sap" +
"/aii/af/app/modules/PayloadSwapBean.java#1 $"
 private static final String SIGNATURE_PROCESS = "process(ModuleContext , ModuleData)";
 protected Hashtable cachedChannels;
 protected SessionContext myContext;
 public MultiSwapRead()
 cachedChannels = new Hashtable();
 public void ejbRemove()
 public void ejbActivate()
 public void ejbPassivate()
 public void setSessionContext(SessionContext context)
 myContext = context;
 public void ejbCreate()
 throws CreateException
 public ModuleData process(ModuleContext moduleContext, ModuleData inputModuleData)
 throws ModuleException
 if(TRACE.beLogged(200))
 TRACE.entering("process(ModuleContext , ModuleData)", new Object[] {
 moduleContext, inputModuleData
 ModuleData outputModuleData;
 Iterator itr;
 outputModuleData = inputModuleData;
 String chid = moduleContext.getChannelID();
 TRACE.infoT("process(ModuleContext , ModuleData)", ModuleCategories.SAP_MODULE_ROOT, (new StringBuilder()).append("performing payload swap for channel ").append(chid).toString());
 LookupManager lman = LookupManager.getInstance();
 Channel chan = null;
try {
chan = (Channel)LookupManager.getInstance().getCPAObject(CPAObjectType.CHANNEL, chid);
} catch (CPAObjectNotFoundException e1) {
// TODO Auto-generated catch block
e1.printStackTrace();
} catch (CPAException e1) {
// TODO Auto-generated catch block
e1.printStackTrace();
 Direction direction = chan.getDirection();
 String swapkey = moduleContext.getContextData("swap.keyName");
 String keyvalue = moduleContext.getContextData("swap.keyValue");
 Object obj = inputModuleData.getPrincipalData();
 Object pivotedObj = inputModuleData.getSupplementalData("mp.pivoted");
 boolean pivoted = pivotedObj == null || !(pivotedObj instanceof Boolean) ? false : ((Boolean)pivotedObj).booleanValue();
 Message mo = null;
 if(obj instanceof com.sap.engine.interfaces.messaging.api.Message)
 mo = (Message)((com.sap.engine.interfaces.messaging.api.Message)obj);
 } else
 if(obj instanceof MessageContext)
 mo = ((MessageContext)obj).getMessage();
 } else
 TRACE.warningT("process(ModuleContext , ModuleData)", ModuleCategories.SAP_MODULE_ROOT, "no message found");
 if(mo != null && XMBMessageOperator.numberOfPayloads(mo) > 0)
 // String midstr = XMBMessageOperator.getMessageId(mo).toString();
 MessageKey auditkey = new MessageKey(((com.sap.engine.interfaces.messaging.api.Message) mo).getMessageId(), com.sap.engine.interfaces.messaging.api.MessageDirection.INBOUND);
 itr = (Iterator) mo.getAttachments();
 if(swapkey != null && keyvalue != null)
 StringBuffer textSwappingbyBuf = new StringBuffer();
 textSwappingbyBuf.append("Swap: swapping by '").append(swapkey).append("' ? '").append(keyvalue).append("'");
 String textSwappingby = textSwappingbyBuf.toString();
 TRACE.infoT("process(ModuleContext , ModuleData)", ModuleCategories.SAP_MODULE_ROOT, textSwappingby);
 Audit.addAuditLogEntry(auditkey, AuditLogStatus.SUCCESS, textSwappingby);
 while (itr.hasNext()){
 boolean swappedp = swapPayloads(mo, swapkey, keyvalue);
 String swappedStatus = swappedp ? "Swap: successfully swapped" : "Swap: no matching payload found";
 Audit.addAuditLogEntry(auditkey, AuditLogStatus.SUCCESS, swappedStatus);
 } else
 StringBuffer textInvalidBuf = new StringBuffer();
 textInvalidBuf.append("Swap: parameter missing ");
 if(swapkey == null)
 textInvalidBuf.append("swap.keyName");
 if(swapkey == null && keyvalue == null)
 textInvalidBuf.append(" and ");
 if(keyvalue == null)
 textInvalidBuf.append("swap.keyValue");
 String textInvalid = textInvalidBuf.toString();
 TRACE.warningT("process(ModuleContext , ModuleData)", ModuleCategories.SAP_MODULE_ROOT, textInvalid);
 Audit.addAuditLogEntry(auditkey, AuditLogStatus.WARNING, textInvalid);
 } else
 String messageEmpty = "Swap: message is empty or has no payload";
 TRACE.infoT("process(ModuleContext , ModuleData)", ModuleCategories.SAP_MODULE_ROOT, messageEmpty);
 return outputModuleData;
 private static boolean swapPayloads(Message mo, String swapkey, String keyvalue)
 swapkey = swapkey.toUpperCase(Locale.ENGLISH);
 keyvalue = keyvalue.toUpperCase(Locale.ENGLISH);
 int ifound = -1;
 for(int i = 0; i < XMBMessageOperator.numberOfPayloads(mo); i++)
 XMBPayload pldi = XMBMessageOperator.getPayload(mo, i);
 String pldivalue = null;
 if(swapkey.equals("PAYLOAD-DESCRIPTION"))
 pldivalue = pldi.getPayloadDescription();
 } else
 if(swapkey.equals("PAYLOAD-NAME"))
 pldivalue = pldi.getPayloadName();
 } else
 pldivalue = pldi.getContentAttribute(swapkey);
 if(pldivalue == null)
 continue;
 pldivalue = pldivalue.toUpperCase(Locale.ENGLISH);
 if(pldivalue.indexOf(keyvalue) < 0)
 continue;
 ifound = i;
 break;
 if(ifound >= 0)
 XMBPayload pldfound = XMBMessageOperator.getPayload(mo, ifound);
 if(pldfound.getPayloadType() != PayloadType.APPLICATION)
 XMBPayload pldapp = XMBMessageOperator.getApplicationPayload(mo);
 if(pldapp == null)
 pldfound.setPayloadType(PayloadType.APPLICATION);
 } else
 pldapp.setPayloadType(PayloadType.APPLICATION_ATTACHMENT);
 pldfound.setPayloadType(PayloadType.APPLICATION);
 TRACE.infoT("process(ModuleContext , ModuleData)", ModuleCategories.SAP_MODULE_ROOT, "successfully swapped");
 return true;
 } else
 TRACE.warningT("process(ModuleContext , ModuleData)", ModuleCategories.SAP_MODULE_ROOT, "no matching found");
 return false;
We couldn't go further. Please have a look in highlighted code.
Regards,
Kesava.

Sender Mail adapter encounters MalformedInputException

I have a sender mail adapter that processes the attached .csv file. All is working fine. I use FCC in module to convert the attachment and pass to an IDOC adapter for processing in SAP system.
My problem is sometimes the sender mail CC fails with ...........
exception caught during processing mail message[1]; com.sap.aii.af.mp.module.ModuleException: Transform: failed to execute the transformation: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException caused by: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException
It only fails with some files. At the moment when we test we FORWARD the email to our email account. If I detach the failed email attachment and attach it to a NEW email it will then work.
So why does it not work when forwarding emails? But it works when I attach the same file to a new email and send?
Other threads for this error seem to point to encoding. But how do I know which to use. I currently use the following in my module config:
Transfer.ContentType     application/octet-stream;charset="ISO-8859-1"

I have this in my configuration:
localejbs/AF_Modules/PayloadSwapBean   on local
TRANSFORM
localejbs/AF_Modules/MessageTransformBean   on local
txtxml
TRANSFORM   swap.keyName   payload-name
TRANSFORM   swap.keyValue   MailAttachment-1
txtxml   Transfer.ContentType   application/octet-stream;charset="ISO-8859-1"
txtxml   Transform.Class   com.sap.aii.messaging.adapter.Conversion
txtxml   Transform.ContentDescription   MailAttachment-1
txtxml   Transform.ContentDisposition   attachment;filename="MailAttachment-1.bin"
txtxml   xml.conversionType   SimplePlain2XML
txtxml   xml.documentName   MT_BCD_INVOICES
txtxml   xml.documentNamespace   urn://federalmogul.com/BCDTRAVEL/FINGLOBCD001/00
txtxml   xml.fieldNames   COST_CENTRE,EMPLOYEE_ID,PRODUCT_GROUP,COMP_CODE,BCD_ACCOUNT,INVOICE_DATE,TRAVELER_NAME,TRAVELER_FIRST_NAME,INVOICE_NO,AMOUNT_EXCL_VAT,CURRENCY1,AMOUNT_VAT,CURRENCY2,AMOUNT_DOC_CURRENCY,CURRENCY3
txtxml   xml.fieldSeparator   ;
txtxml   xml.lastFieldsOptional   YES
txtxml   xml.processFieldNames fromConfiguration
txtxml   xml.structureTitle   RECORDSET

Sender "Mail" adapter - CSV file attachment

Hi there
I'm looking for some help in configuring a sender mail adapter that receives ".csv" files. I did read some blogs that mention using the "PayloadSwapBean" module to read the mail attachment instead of the mail content. My problem is to now convert the ".csv" file into a message. Is there a module that I can use ( is it the "MessageTransfomBean" ) and how. Any help would be appreciated.
Thanks
Salil

Hi Salil,
If you want to send a mail with a body and attachments, the message sender HAS to provide an XI message with attachments. I doubt a CSV file does justice.
As Renjith said you need to convert CSV to XmL.
A short description about the Standard Modules:
MessageTransformationBean is a standard module used to apply the XSLT mapping to the adapter module by using Transform.class ( This xslt mapping is done to create a mail package, Dont confuse with the actual mapping in your case this is NOT for converting csv to xml).
Also this module can be used to change the name and type of payloads by using Transform.contentType, Transform.contentDisposition, Transform.contentDescription.
PayloadSwapbean is a standard module for replacing payloads with other payloads (SWAP)
If you want to give each attachment a certain name use Parameters, swap.keyname for name of the payload and swap.keyvalue.
I Hope the use of standard modules is understood.

Sender Mail Adapter, technical Acknowledgement

Hi all,
I have a SMTP --> XI --> Proxy Scenario. For the inbound message I get via SMTP, I'd like to send a technical acknowledgement back to the Sender (via SMTP, too). The acknowledgement has a specific message structure, for example it contains the DocumentID of the inbound message I get via SMTP.
My idea now is: Within ReceiverDetermination, I configure two receivers:
1. Backend system for the Inbound Proxy
2. original Sender System
Within Interface Determination, I'll do 2 mappings:
1. Mapping from source message to ABAP proxy interface
2. Mapping from source message to technical acknowledgement structure
Then, receiver agreements / receiver communication channels for both interfaces.
My question now is: is there a more elegant solution then doing the scenario like described above? Maybe something I can do in the Sender Mail Adapter to create the specific technical acknowledgement and sent it back to the sending application?
Best regards
Holger

Hi Holger !
XI supported acks are not available for your scenariom because the smtp/mail sender cannot request it.
http://help.sap.com/saphelp_nw04s/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/frameset.htm
You should create some kind of artificial ack, that should be part of your own protocol. What I meant with the SYNC proxy, is to use its response message as your own defined ack, because it is not supported as is.
If you call your proxy async, then you will not receive any feedback to use it as ack info.
Another idea could be to forget the ack per se, and just use define an alert in case of problems with the scenario to send a mail to the specified users.
Regards,
Matias

Sender mail adpater

Similar Messages

Maybe you are looking for