cancel
Showing results for 
Search instead for 
Did you mean: 

BPM stops after receiving payloads from sender email channel

former_member189519
Participant
0 Kudos

Hi,

my current situation:

i have a sender email cc which sends the content plus attachments into the xi. here i map it to an BAPI-request structure and forward it to an BPM-process. this BPM does a sync call to an r/3. i use the payload swap bean to switch the attachment-1 as content.

-> when i generate the email with e.g. thunderbird the scenario runs

Problem:

but if i use outlook or notes the email appears as a multipart message with attachments (that should not be a problem as i still use the attachment-1) the forward to the BPM causes a stuck?

<b>this one works:</b>


--SAP_f5e98a51-c25a-11db-8164-000e7fef2133_END
Content-ID: <soap-f5e98a50c25a11db94b7000e7fef2133@sap.com>
Content-Disposition: attachment;filename="soap-f5e98a50c25a11db94b7000e7fef2133@sap.com.xml"
Content-Type: text/xml; charset=utf-8
Content-Description: SOAP

<SOAP:Envelope>lots of funny stuff</SOAP:Envelope>

--SAP_f5e98a51-c25a-11db-8164-000e7fef2133_END
Content-ID: <payload-ef2dc142c25a11dbae43000e7fef2133@sap.com>
Content-Type: text/html; charset=ISO-8859-1
Content-Disposition: attachment;filename="MailMessage.htm"
Content-Description: MailMessage

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
</body>
</html>

--SAP_f5e98a51-c25a-11db-8164-000e7fef2133_END
Content-ID: <payload-ef2dc143c25a11dbb5c8000e7fef2133@sap.com>
Content-Type: text/xml;charset=iso-8859-15
Content-Disposition: attachment;filename="MailAttachment-1.bin"
Content-Description: MailAttachment-1

<?xml version="1.0" encoding="utf-8"?>
<ns:salesorderlines_recordset xmlns:ns="http://namespace">
and so on

<b>this not:</b>


--SAP_1ce0ab21-c25b-11db-c38b-000e7fef2133_END
Content-ID: <soap-1ce0ab20c25b11dbb864000e7fef2133@sap.com>
Content-Disposition: attachment;filename="soap-1ce0ab20c25b11dbb864000e7fef2133@sap.com.xml"
Content-Type: text/xml; charset=utf-8
Content-Description: SOAP

<SOAP:Envelope>same entries as above</SOAP:Envelope>

--SAP_1ce0ab21-c25b-11db-c38b-000e7fef2133_END
Content-ID: <payload-18285332c25b11dbca99000e7fef2133@sap.com>
Content-Type: multipart/alternative; boundary="=_alternative 002A6CACC125728A_="
Content-Disposition: attachment;filename="MailMessage.bin"
Content-Description: MailMessage


--=_alternative 002A6CACC125728A_=
Content-Type: text/plain; charset="US-ASCII"


--=_alternative 002A6CACC125728A_=
Content-Type: text/html; charset="US-ASCII"


--=_alternative 002A6CACC125728A_=--
--SAP_1ce0ab21-c25b-11db-c38b-000e7fef2133_END
Content-ID: <payload-18285333c25b11dbb56e000e7fef2133@sap.com>
Content-Type: text/xml;charset=iso-8859-15
Content-Disposition: attachment;filename="MailAttachment-1.bin"
Content-Description: MailAttachment-1

<?xml version="1.0" encoding="utf-8"?>
<ns:salesorderlines_recordset xmlns:ns="http://namespace">
and so on

could it be the "Content-Type: multipart/alternative; boundary..." ??

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member189519
Participant
0 Kudos

Oh yeah...

found it by myself

everything with type "multipart/alternative" stucks in SAP XI

at my side the only solution was:

1. module

PayloadSwapBean with "swap.KeyName = content-type" and "swap.KeyValue = multipart/alternative"

to select the problematic part

2. module

MessageTransformBean with "transform.ContentType = text/plain; charset=UTF-8"

to assign the part a standard/readable encoding (for XI)

3. module

PayloadSwapBean with "swap.KeyName = content-name" and "swap.KeyValue = Attachment-1"

to go on with the attachment...

both conversions "text/plain" and "text/xml" worked fine