@wani-amol, it appears that you are using Oracle Financials (Cloud?) and the ERP Integration Service’s loadAndImportData operation.
According to this documentation:
the type of the <ns1:Content> field is {http://xmlns.oracle.com/adf/svc/types/}base64Binary-DataHandler - I imagine that means the file content is Base64-encoded.
SnapLogic provides Base64 encoding via the Expression Language and also via the Binary to Document Snap - you could use either of those depending on your pipeline design. Mapping the Base64 encoded data to the $document.Content property, so that it may be used in the SOAP Execute’s template, should complete the required steps.
Hey Robin,
I figured the issue. I was trying to find a way to reference the file I am attaching to the soap snap in the envelope. Refer below:
erp:Content
<xop:Include
xmlns:xop=“http://www.w3.org/2004/08/xop/include” href=“cid:ArAutoinvoiceImport.zip”/>
</erp:Content>
I had to add the xop line and reference the filename to send it across.
I had encoded the file in Base64 format but it gave me an error. When i sent the file without encoding, it went through which was weird but it solved my error.
Thanks for your help though! 🙂
-Amol
