Skip to Content
author's profile photo Former Member
Former Member

soap attachment mapping problem, xop:include

Hello experts,

I am using PI 7.3

I have a senario SOAP to IDOC which SOAP is a sender adapter.

My Web Service receives attachment which includes MTOM, xop:include

I read the attachment in the message mapping by User-Defined function.

But I have another problem while message mapping.

<SAP:Category>Application</SAP:Category>

<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>

<SAP:P1>Unexpected value <null> for node /ns0:TrainingAttachment/ns1:binary</SAP:P1>

in attachment part of the web service is following,

<urn1:attachment>

<urn1:binary>

http://www.w3.org/2004/08/xop/include" />

</urn1:binary>

</urn1:attachment>

I think my message mapping doesnt resolve the binary part

I tried the Do Not Resolve XOP Includes checkbox, nothing changed

Thanx for your help

Hasan

Edited by: ordu_hasan on Feb 23, 2012 4:12 PM

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on May 27, 2013 at 11:23 AM

    Hi Hasan,

    Please, try to implement next xslt mapping before message mapping.

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

    <ns0:stylesheet version="1.0" xmlns:ns0="http://www.w3.org/1999/XSL/Transform" xmlns:xop="http://www.w3.org/2004/08/xop/include" xmlns:ns2="https://onlineservice.creditreform.de/webservice/0400-0005">

    <ns0:template match="node() | @*">

    <ns0:copy>

    <ns0:apply-templates select="node() | @*"/>

    </ns0:copy>

    </ns0:template>

    <ns0:template match="xop:Include"/>

    </ns0:stylesheet>

    Regards, Dzmitry

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 03, 2015 at 04:11 PM

    Hello,

    did you find solution?

    Thanks

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 14, 2016 at 06:33 PM

    Hello Experts

    I am trying to send a similar MTOM attachment message from soapUI to my test scenario (Webservice -> PI -> ERP WebService) in SAP-PI7.3.1:

    Here is the input: (with attachment: test.txt)

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v1="http://ccsap.bit.admin.ch/soa/ccsap/SalesOrderChange/v1">

    <soapenv:Header/>

    <soapenv:Body>

    <v1:SOASalesOrderAttachmentRequest>

    <SALES_DOCUMENT>12234</SALES_DOCUMENT>

    <AR_OBJECT>VBAK</AR_OBJECT>

    <SAP_OBJECT>cid:test.txt</SAP_OBJECT>

    <SIMULATION>X</SIMULATION>

    </v1:SOASalesOrderAttachmentRequest>

    </soapenv:Body>

    </soapenv:Envelope>


    I used WS (sender) Adapter to send the above message.


    in SXMB_MONI, it look like as follows:



    Main Document

    As explained by Dzimtry above, I have added the XSLT mapping before the message mapping but still getting the following exception:

    Additional Error Text: Typ Content-ID contains invalid characters, Kernel Error Id Please change the mapping.

    after this error, the payload look like this ( attachment is converted to BASE64)

    Can anybody tell, what I am doing wrong here?

    Thanks for your valuable time in advance!

    Best Regards

    Satish.


    1.PNG (20.5 kB)
    2.PNG (3.1 kB)
    3.PNG (10.6 kB)
    4.PNG (18.7 kB)
    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.