Are you seeing IDOC data in a string variable in the pipeline,if so then for parsing use stringToDocument,documentToRecord(parses based on the IDOC recordstructure specify recordName gives output boundNode (IDATA structure) etc…do mapping further to target format XML in your case.
I’m having some odd effects happening via the XSLT transformation package…
If I create two parameters XMLDocument, XSLT as strings ‘Large Editor!’ then copy a XML document in and an XSLT, run the flow… the transformed XML is generated fine, no issues…
If the XML comes from the ‘recordtodocument’ package - then I call the XSLT from a file the transformation fails - it seams to add a 0 after a date in the payload attribute and orderdate attribute…