XSL Debugging.

Question

Hi Experts,
       I am using the standard component of IR , Store Connnectivity. There The standard Interface mapping that I am using is GMTLog2POSDM. File 2 RFC scenerio.
    It contaiins 2 XSL mapping and 1 graphical mapping.
In sxmb_moni I am getting error : Exception occurred during XSLT mapping of the application, meaning that the data send from file to RFC scenerio do not match with the standard mapping.
   Unlike Graphical mapping where I could pick the load from sxmb_moni and put it in messege mapping , and dry test it and find out which perticular field was giving error, here in this case, i cant make out which pericular field data is not matching in the XSL mapping.
Can u suggest any way, by which i canfind out where in the standard XSL mapping is the load failing.
Regards,
Arnab

Answer 1

Pratik,
            Have you tried using the payload from the test tab of Interface Mapping?
     Ya,, but here again, as i hav said there are 2 XSL mappings and 1 java maping.... Hw do I diversify from these 3 mappings amd chexck individually???
   Altova / XML spy,, well I will try on it.
Vishnu,
              ya,, that ios the last option,,,, but i was wondering for som simpler sol.
Srinivasrao
     as per my knowledge you go to SXMB_Moni and go to TRACE error in the message u can find the exception
In SXMB_MONI, in trace, I see a BIG error.....startin with
<Trace level="1" type="T">TransfromerException during XSLT processing:</Trace>
  <Trace level="1" type="T">javax.xml.transform.TransformerException: java.lang.ArrayIndexOutOfBoundsException at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:255) at com.sap.aii.ibrun.server.mapping.MappingTransformer.transform................................blah blah blah......
eally cant make out anythin from here.. if u can explain futher , I can put up the entire trace error.
Patrick,
There you see that there is a way of displaying errors and warnings.
To answer your question Briefly, within SAP xi the message mapping works with namespaces. (Like ns0:). When creating an XLS please first load the message(s) inside the Graphical mapper and view as XML. Ensure that your XSL represents the predefined XML namespace as also done in the Graphical Mapper.
If you need more info let me know.
Greets
well the load that I am having is very big,, really don know,, hw to do that...
When creating an XLS please first load the message(s) inside the Graphical mapper
.... ya, goin through ur links ..
Awaitin reply....
Arnab .