Attachments on Manage Activities WebServices

Hello Community,

we have the requirement of automatic creation of Activities (E-Mails and Appointments in particular) in our C4C tenant by an external system. The Activities will contain for sure Attachments.

We proposed to use the Standard WebService API provided with SAP Cloud for Customer, and in particular, for our purposes,  the standard WebService  "Manage E-Mail Activities" (technical name: ManageEmailActivityIn). All the provided specs and docs about the WS can be found at the following URL: Inbound Service Interface (public)

Our procedure had then the following steps:

1. Create a new working Communication Arrangement for the WebService;
2. Download the WSDL file for the active Comm Arrangement;
3. Test the WS with a basic SOAP Request (with no attachments), by using any Test tool (we used SoapUI);
4. Test the WS with a SOAP Request + Attachments.

The first 3 steps have been closed with a success. We are able to remotely create activities by using the following sample Request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:glob="http://sap.com/xi/SAPGlobal20/Global">

   <soapenv:Header/>

   <soapenv:Body>

      <glob:EmailActivityBundleMaintainRequest_sync_V1>

        

         <EmailActivity actionCode="01">

            <MessageFromParty>

               <EmailURI>c.elridge@trsollicitors.co.uk</EmailURI>

            </MessageFromParty>

           

            <MessageToParty>

               <EmployeeID>1</EmployeeID>

            </MessageToParty>

           

            <Text actionCode="01">

               <TextTypeCode>10002</TextTypeCode>

               <ContentText>Sample Text.</ContentText>

            </Text>

       

         </EmailActivity>

      </glob:EmailActivityBundleMaintainRequest_sync_V1>

   </soapenv:Body>

</soapenv:Envelope>

Nevertheless, we are experiencing an issue on achieving step 4. Since it is considerable bigger than the basic request, we attached on this post the SOAP Request containing the attachment. The request has all the attachment-relevant XML fields populated and the Binary Code of the attachment formatted as a Base64 string. We can confirm that the MIME Type involved in our tests (application/msword) has been enabled for upload in the Business Configuration.

Could you please advise about it? Is there any information missing (or wrong) in the SOAP Request attached?

We are always available for further information and/or clarification.

Kind regards,

Davide