cancel
Showing results for 
Search instead for 
Did you mean: 

TransformerException occurred during XSLT mapping

Former Member
0 Kudos

Hi friends,

I updated some Message mappings and external definitions in Enterprise Services Builder, since then, I am getting this error when I run the sap program which communicates with an external web service:

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

- <!--  Inbound Message

  -->

- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

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

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

  <SAP:P1>remover_namespace_totalupload</SAP:P1>

  <SAP:P2>http://xsales.com</SAP:P2>

  <SAP:P3>17513720-6c0d-11e3-c08f-dca80a8cc0de</SAP:P3>

  <SAP:P4>-1</SAP:P4>

  <SAP:AdditionalText />

  <SAP:Stack>TransformerException occurred during XSLT mapping remover_namespace_totalupload (http://xsales.com, 17513720-6c0d-11e3-c08f-dca80a8cc0de, -1)</SAP:Stack>

  <SAP:Retry>M</SAP:Retry>

  </SAP:Error>

 

  I have a doubt with the following message:

  TransformerException occurred during XSLT mapping remover_namespace_totalupload

 

  What is exactly remover_namespace_totalupload? Where can I find it? Is it the cause of the problem? I don't know anything about PI, so I don't know what to do.

 

  Any help would be appreciated.

 

  Best regards.

Accepted Solutions (0)

Answers (4)

Answers (4)

peter_wallner2
Active Contributor
0 Kudos

Hello,

Can you test the XSL map "remover_namespace_totalupload" locally using the source payload XML?

If you do not have Oxygen, Eclipse, etc. you can do it online - for example

Free Online XSL Transformer (XSLT) - FreeFormatter.com

An application like Oxygen would help because you also have a debugging mode and it is easier to find transmformation problems.

Best regards,

Peter

Former Member
0 Kudos

You probably have an XSLT mapping named remover_namespace_totalupload defined inside the Operation Mapping. Something has changed the source message such that this XSLT mapping can no longer read the message.

You can find the source of it inside the ESR / Designer under the specific Software Component version \ Namespace look inside the Imported Archives.

There you can see the source of the XSLT mapping by double clicking on the Archive Program .xsl Name.

Former Member
0 Kudos

Hi,

Can you paste the message mapping trace? That will provide more info on the mapping error.

Regards,

Anuj

Former Member
0 Kudos

Hi,

Can you please share the XSLT mapping which you will get in Imported Archives of ESR ?

Regards,

Souvik