XSLT 2.0 support in XSLT SE ?

Hi,
The XSLT SE in the Java CAPS 6 GA version only supports XSLT 1.0. Does anyone know when XSLT 2.0 will be supported?
Thanks.

Hi Kurt,
At this time, there's no plan to support schema-aware xslt in Java CAPS 6. It would likely require partnering with Saxonica to release Saxon-SA with OpenESB, but that's not a conversation that's occurred as far as I know.
I'll discuss the possibility of adding schema-aware xslt with our product management.
Regards,
Kevan

Similar Messages

  • Which XSLT versions are support by Oracle BPEL? v1.1  or v2.0?

    Which XSLT versions are support by Oracle BPEL? v1.1 or v2.0?
    As far as I heard v1.1 is the highest version but some functions of v2.0 are supported as well.
    Is this true?
    If yes: Which XSLT functions of v2.0 are supported?
    Does it matter if I change the
    version="1.1"
    attribute in the topmost
    <xsl:stylesheet......>
    tag?
    Which XSLT processor is built-in/used?
    Peter

    XSL mapper in BPEL supports 1.0 only in-built. And this is true for 11g also. However, we can declare <xsl:stylesheet version = 2.0 ... and use all xpath 2.0 functions. I have used few of them and has been successful so far. Once you declare version as 2.0 the only issue will be that XSL's visual GUI mapper will not work in JDeveloper and you will need to modify the code from the source.

  • XSLT 2.0 support in XI

    Hi,
    I am using XI 3.0 (SP13). How do I know if this supports XSLT 2.0 or not? Is there a special file that I have to look for in the installation folders or is there transaction code that displays the details?
    Also, it will be greatly appreciated if someone can point me to - how to configure a 3rd party XSL processor (like Saxon) on the XI server.
    Thanks,
    Badari

    Here is a way (or probably one of many ways) to do this.
    Simply insert this xsl file into an archive and use it in a mapping with 2 dummy interfaces, one as source and another as target. And run the transform.
    XSL File:
    <?xml version="1.0"?>
    <xsl:stylesheet version="2.0"
         xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
         <xsl:output method="xml" indent="yes" />
         <xsl:template match="*">
              <systemProperties>
                   <xslVersion>
                        <xsl:value-of select="system-property('xsl:version')" />
                   </xslVersion>
                   <xslVendor>
                        <xsl:value-of select="system-property('xsl:vendor')" />
                   </xslVendor>
                   <xslVendorURL>
                        <xsl:value-of
                             select="system-property('xsl:vendor-url')" />
                   </xslVendorURL>
                   <xslProductName>
                        <xsl:value-of
                             select="system-property('xsl:product-name')" />
                   </xslProductName>
                   <xslProductVersion>
                        <xsl:value-of
                             select="system-property('xsl:product-version')" />
                   </xslProductVersion>
                   <xslIsSchemaAware>
                        <xsl:value-of
                             select="system-property('xsl:is-schema-aware')" />
                   </xslIsSchemaAware>
                   <xslSupportsSerialization>
                        <xsl:value-of
                             select="system-property('supports-serialization')" />
                   </xslSupportsSerialization>
                   <xslSupportsBackwardCompatibility>
                        <xsl:value-of
                             select="system-property('xsl:supports-backwards-compatibility')" />
                   </xslSupportsBackwardCompatibility>
              </systemProperties>
         </xsl:template>
    </xsl:stylesheet>
    Output:
    <?xml version="1.0" encoding="utf-8"?>
    <systemProperties>
       <xslVersion>1.1</xslVersion>
       <xslVendor>InQMy Labs.</xslVendor>
       <xslVendorURL>http://www.sap.com</xslVendorURL>
       <xslProductName/>
       <xslProductVersion/>
       <xslIsSchemaAware/>
       <xslSupportsSerialization/>
       <xslSupportsBackwardCompatibility/>
    </systemProperties>
    Thanks,
    Badari

  • XSLT 2.0 supported in Oracle BPEL ?

    Hi,
    is XSLT 2.0 (schema-aware) supported or is there any way to change the built-in XSLT parser to Saxon or another one?
    Thanks.

    For anyone that's interested, I found the solution.
    In order to make it work, I had to add dateTime() around the XPath locations to the vars:
    <xsl:value-of select="dateTime(/ns1:durationTestProcessRequest/ns1:date2) - dateTime(/ns1:durationTestProcessRequest/ns1:date1)"/>

  • Whether XI (3.0 /7.0)  Supports the XSLT 2.0 Version

    Hi,
        I  tried  to do the converting the Date Format using the XSLT (2.0 version) functions like  (MonthFromDate,YearFromDate,DayFromDate),but I am getting the Transformation Exception Error in the Interface Mapping.(i.e.  <b>javax.xml.transform.TransformerException: com.sap.engine.lib.xml.util.NestedException: -> com.sap.engine.lib.xml.util.NestedException: Function with name 'month-from-date' not found in context library</b>).
    In Stylus Studio that XSLT Mapping Program is Working Fine,but iam getting the error while testing the Interface mapping using that XSLT mapping program.
    Can you please give your valuable suggestions,
    Thanks and Rgss,
    Kamal Kumar

    XI XSLT processor doesn't support XSLT 2.0.
    You'll have to stick to XSLT 1.0 or implement your functionallity in a XSLT template or Java function and use it in XSLT with java enhancement.
    http://help.sap.com/saphelp_nw70/helpdata/en/55/7ef3003fc411d6b1f700508b5d5211/frameset.htm
    Regards,
    Henrique.

  • XSLT European Language Support in XMLData class (part of Oracle XML kit)

    My code in JSP (with JDev) looks like this:
    <jsp:useBean id="XSLTProcesseur" class="oracle.jbo.html.databeans.XmlData" scope="request">
    <%
    String sImageBase = (String)session.getValue("ImageBase");
    XSLTProcesseur.initialize(application, session , request, response, out, "bilanmetastatique_BilanModule.MasterBilanMetView");
    XSLTProcesseur.setReleaseApplicationResources(true);
    XSLTProcesseur.setStylesheet(sImageBase + "/BilanMeMasterJSP.xsl");
    XSLTProcesseur.render();
    %>
    </jsp:useBean>
    In the xsl file, BilanMeMasterJSP.xsl, I use French characters and got error messages (exceptions) out of XMLData class.
    Running the same stylesheet with Stylus Editor from Object Design work fine! (IBM XSL Editor works too)
    Any help appreciated, thanks.
    null

    Does your stylesheet use:
    <xsl:output encoding="xxx"/>
    to specify a proper encoding for the
    characters you're trying to use?

  • XSLT Editor in Imported Archives (XSLT)

    Hi,
    The SAP Library Content found at this Link:
    http://help.sap.com/saphelp_nw70/helpdata/EN/4c/b2ad3de2d76b3be10000000a114084/frameset.htm
    says:
    "Changes the selected XSLT program. In an Integration Builder editor you can either change lines or import another XSLT program."
    Does this mean, the default Integration Builder editor can be changed to an editor I prefer?
    My aim is to edit the XSLT-Mapping out of the ntegration Builder with the editor I like.
    In our  Integration Builder  the prefered editor is used when I press button "Open in Client Browser", but I whould like it in "Change Program".
    Many thanks for your ideas!
    Brigitte

    Hi,
    Unfortunatley this is not possible yet because editor choice not configurable or in other term since IR is using simple text editor (which can be simple multiline text box).
    But it is good suggestion and you can forward it to SAP XI design team.
    Regards,
    Gourav

  • XSLT  - Exception error when using XSLT 2.0 code in Transform on LiveCycle ES2

    I'm new to using this forum, so apologies in advance in I have posted this to the wrong place.
    I'm using Adobe LiveCycle ES2.5 (Jboss) and have written several complex XSLT scripts.  All have worked, with the exception of the latest one in which I have to sum a repeating subnode that maynot exist and if it does, may contain a number or be empty.  When I have used SUM by itself, it works perfectly if I all the nodes have values, but returns zero if any are missing or are empty.  After some searching I found a solution (which I have made bold) in the fragment below.
    <xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" ...>
    <xsl:variable name="varUnitValueTotal" select="sum( (if(SOURCEUNITVALUE='') then 0 else SOURCEUNITVALUE) )"/>
    </xsl:stylesheet>
    I developed and tested this xslt in XMLSpy 2011 and it works a treat.  However, when I invoke the XSLT using the Services\XSLT Transformation 1.0\Transform, I get the following exception error:
    javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: Could not find function: if
        at org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.jav a:936)
        at org.apache.xalan.processor.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.j ava:774)
        at com.adobe.livecycle.xslt.XsltTransformer.transform(XsltTransformer.java:151)
    Now as far as the documentation is concerned ES2 and better should be using XSLT 2.0.  However to test a theory I changed the stylesheet version from 2.0 to 1.0 and re-ran the xslt in XMLSpy and it fell over at exactly the same place as the exception error.  Which makes me conclude that LC ES2+ is still using XSLT 1.0.
    Now I am stuck.  The only work around that I can see is to attempt to do the calculation in the form (which sort of defeats the point of usng XSLT).  That said I am reluctant to go down that path, since the maintenance overhead is going to be shocking if I have to apply to dozens of forms.
    Is there a way to tell the Transform service to use XSLT 2.0 and if so, how and what are the settings?  Or do I need to find and use a different transform engine, again if so which one should I use and what settings should I make at either JBoss and/or AdminUI level.
    Really hoping that someone can help.

    The XSLT service is configurable.
    http://help.adobe.com/en_US/LiveCycle/9.5/WorkbenchHelp/WS92d06802c76abadb-1cc35bda128261a 20dd-6750.html
    1) Stop LiveCycle.
    2) Add the .jars of your XSLT processor of choice to the LiveCycle server lib folder.
    3) Restart LiveCycle.
    4) Go to Workbench and stop the XSLT service. Right-click on XSLTService:1.0 and Edit Service Configuration.
    5) Enter the factory name for the given XSLT processor. I think for Xalan 2.7.1 it is org.apache.xalan.processor.TransformerFactoryImpl (but I could be wrong).
    6) Restart the service.
    Steve

  • Using the XSLT processor for non-workbench XSLT

    Hi there,
    is it possible to use the built-in XSLT processor for arbitrary XSLT transformations which aren't checked in in the ABAP workbench but instead given as a runtime object (string or iXML)?
    Instead of the built-in command CALL TRANSFORMATION which according to the doc is restricted to workbench transformations, I am looking for an option like this:
    data: lo_transformation type ref to if_ixml_document,
          lo_source         type ref to if_ixml_document,
          lo_target         type ref to if_ixml_focument.
    * I get lo_transformation and lo_source from somewhere out there
    try.
        lo_target ?= cl_some_fine_class_which_i_am_looking_for=>transform(
                          io_source         = lo_source
                          io_transformation = lo_transformation ).
      catch cx_xslt_runtime_error.
    endtry.
    Does anybody know such a feature?
    For a background about this problem - in German language - see my blog
    http://ruediger-plantiko.blogspot.com/2007/08/xslt-in-bsp-anwendungen-und-in-abap.html
    Thanks and Regards,
    Rüdiger

    Dear Rashid,
    thanks - this is the answer! I wonder why I didn't find this class one year ago. A little test prog shows that it works fine and even performant (about 0.5 millisec for creating the new dynamic XSLT program with the method set_source_stream( ) ). For usage in web apps, it would be nice to know whether the temporary program remains available in the application servers' buffer after end of process. I can't check this, since this is performed on the C/C++ level, and SE30 doesn't track the method set_source_stream() itself (it could show a decrease of runtime after the first call).
    Here comes a little self-contained ABAP program to test the functionality. It works well on our system with SAPKB70012.
    Thanks and regards,
    Rüdiger
    * --- Test usage of a dynamically given non-workbench XSLT program
    report  zz_test_cl_xslt_processor.
    data:
    * iXML master
      go_xml type ref to if_ixml,
    * iXML stream factory
      go_sf  type ref to if_ixml_stream_factory.
    load-of-program.
      go_xml = cl_ixml=>create( ).
      go_sf  = go_xml->create_stream_factory( ).
    start-of-selection.
      perform start.
    * --- Start
    form start.
      data: lo_source    type ref to if_ixml_document,
            lo_result    type ref to if_ixml_document,
            lo_processor type ref to cl_xslt_processor,
            lv_p         type progname,
            lo_ex        type ref to cx_xslt_exception.
      perform get_source changing lo_source.
      create object lo_processor.
      try.
    * Set source
          lo_processor->set_source_node( lo_source ).
    * Set result
          lo_result = go_xml->create_document( ).
          lo_processor->set_result_document( lo_result ).
    * This could be time-critical, the creation of a dynamical XSLT prog?
          perform set_transformation using lo_processor
                                     changing lv_p.
    * call xslt-proc
          lo_processor->run( lv_p ).
    * Display result
          call function 'SDIXML_DOM_TO_SCREEN'
            exporting
              document    = lo_result
              title       = 'Result of Transformation'
            exceptions
              no_document = 1
              others      = 2.
        catch cx_xslt_exception into lo_ex.
          sy-msgli = lo_ex->get_text( ).
          message sy-msgli type 'I'.
      endtry.
    endform.                    "start
    * --- Set XSLT transformation from stream
    form set_transformation using io_processor type ref to cl_xslt_processor
                            changing cv_p type progname.
      data: lo_trans     type ref to if_ixml_istream.
    * sv_p contains temp. name of XSLT program after first call
      statics: sv_p   type string.
      if sv_p is initial.
    * It seems that the name can be buffered on appserver level?
        import progname to sv_p
               from shared buffer indx(zx) id 'ZZ_TEST_XSLT_PROC'.
        if sv_p is initial.
          sv_p = 'X'.
        endif.
      endif.
    * Provide the stream containing the XSLT document (as a stream)
      perform get_transformation changing lo_trans.
    * Set transformation
      io_processor->set_source_stream( exporting stream = lo_trans
                                       changing  p      = sv_p ).
    * Buffer progname on server - seems to work
      export progname from sv_p
             to shared buffer indx(zx) id 'ZZ_TEST_XSLT_PROC'.
    * string -> c move necessary, since xslt-proc-interface doesn't use
    * the generic type csequence for program name
      cv_p = sv_p.
    endform.                    "set_transformation
    * --- Parse a source given as string into an if_ixml_document
    form get_source changing co_src type ref to if_ixml_document.
      data: lv_s      type string,
            lo_stream type ref to if_ixml_istream,
            lo_parser type ref to if_ixml_parser.
      concatenate
    `<?xml version="1.0" encoding="iso-8859-1"?>`
    `<countings filiale="2412" invnu="TIEFKUEHL SEPT.07">`
    `<count recNum="1" gid="1" ean="59111828843" menge="1"`
    `preis="0" recNumFrom="1"></count>`
    `</countings>`
    into lv_s.
    * Eingabestream erzeugen und in if_ixml_document abbilden
      lo_stream   = go_sf->create_istream_string( lv_s ).
      co_src      = go_xml->create_document( ).
      lo_parser   = go_xml->create_parser( document       = co_src
                                           istream        = lo_stream
                                           stream_factory = go_sf ).
      lo_parser->parse( ).
    endform.                    "get_source
    * --- Put the transformation given as string into an if_ixml_istrean
    form get_transformation changing co_trans type ref to if_ixml_istream.
      data: lv_s   type string.
      concatenate
      `<?xml version="1.0" encoding="iso-8859-1"?>`
      `<xsl:transform version="1.0"`
      ` xmlns:xsl="http://www.w3.org/1999/XSL/Transform"`
      ` xmlns:asx="http://www.sap.com/abapxml">`
      `<xsl:strip-space elements="*"></xsl:strip-space>`
      `<xsl:template match="countings">`
      ` <asx:abap>`
      `   <asx:values>`
      `     <SELOPT>`
      `       <WERKS><xsl:value-of select="@filiale"></xsl:value-of></WERKS>`
      `       <INVNU><xsl:value-of select="@invnu"></xsl:value-of></INVNU>`
      `     </SELOPT>`
      `     <COUNTINGS>`
      `       <xsl:for-each select="count">`
      `         <ZSRS_ZWSTI_LINE>`
      `           <MATNR></MATNR>`
      `           <EAN11><xsl:value-of select="@ean"></xsl:value-of></EAN11>`
      `           <MAKTX></MAKTX>`
      `           <MENGE><xsl:value-of select="@menge"></xsl:value-of></MENGE>`
      `           <MEINH></MEINH>`
      `           <UNAME></UNAME>`
      `           <EXVKW></EXVKW>`
      `           <WAERS></WAERS>`
      `           <FF></FF>`
      `           <GID><xsl:value-of select="@gid"></xsl:value-of></GID>`
      `           <RECNUM><xsl:value-of select="@recNum"></xsl:value-of></RECNUM>`
      `           <RECNUM_FROM><xsl:value-of select="@recNumFrom"></xsl:value-of></RECNUM_FROM>`
      `           <REF_RECNUM><xsl:value-of select="@refRecNum"></xsl:value-of></REF_RECNUM>`
      `         </ZSRS_ZWSTI_LINE>`
      `       </xsl:for-each>`
      `     </COUNTINGS>`
      `   </asx:values>`
      ` </asx:abap>`
      `</xsl:template>`
      `</xsl:transform>`
      into lv_s.
      co_trans = go_sf->create_istream_string( lv_s ).
    endform.                    "get_transformation
    Edited by: Rüdiger Plantiko on Jul 4, 2008 10:25 AM

  • XI / PI XSLT support

    Hi all,
    could you please be so kind and tell me, which XSLT Version is currently supported by PI7.0 and 7.1 ?
    If it's not XSLT2.0 is it possible to add external libraries for XSLT mapping which support XSLT 2.0 ?
    Cheers,
    Martin

    You can get libraries for XSLT 2.0 from Saxon (saxon.sourceforge.net), but I don't know if you can use them with XI.
    Best wishes,
    Jan

  • XSLT support in OSB10gR3

    Hi,
    I am using OSB10.3 and would like to know the support of XSLT Version 2.0 on it.
    Does it support XSLT 2.0 or not and which XSLT engine it uses?
    Thanks in advance
    Ananya
    Edited by: Ananya Bhushan on Apr 27, 2010 9:35 PM

    Hi Ananya,
    I do not think XSLT 2.0 is supported in current version of OSB and NOT sure but perhaps it uses Xalan processor for XSLT. Contact Oracle Support for formal confirmation.
    Regards,
    Anuj

  • Remove Special Character in XSLT

    Hi All,
    Could anyone please help me in removing the special characters  in the XSLT file.
    For Example, XSLT tag has like below code,
    <Name>
    <xsl:valule-of select="Payee/Name"/>
    </Name>
    where as Payee/name has value of "ORACLE%$ISGREAT".(I can have only A..Z and 0..9, no other than this)
    Could any one pls help me.
    Regards,
    Uva

    Which XSLT version are you able to use? 1.0 or 2.0 ?
    On 2.0, regular expressions support makes it easy :
    <xsl:value-of select="replace(Payee/Name, '[^0-9A-Z]', '')"/>
    On 1.0, it's just a bit more complicated, using the double translate trick :
    translate($str, translate($str, '0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ', ''), '')
    which you can turn into a named template for modularity :
      <xsl:template name="sanitize">
        <xsl:param name="str"/>
        <xsl:value-of select="translate($str, translate($str, '0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ', ''), '')"/>
      </xsl:template>
    and call it like this :
    <xsl:call-template name="sanitize">
      <xsl:with-param name="str" select="Payee/Name"/>
    </xsl:call-template>

  • XSLT Mapping Docs

    Hi,
    Can any one post me some good Documents on XSLT mapping?
    With kind regards,
    Joseph

    Hi,
    Each mapping has its own adavantages and disadvantages. XSLT is one type of mapping that Xi supports. XSLT mapping also do have certain advantages like if you need a formatted output like HTML in XSLT it would be easy to implement... XSLT is a W3C standard so if also works in any other integration s/w other than XI so it is portable
    prefer XSLT Mappings over Graphical mappings, since it's easier to use. One other big advantage of using XSLT mapping not mention, atleast I think, is that changes to XSD's loses all mappings with graphical mappings but with XSLT's you just add the field changed or added, instead of starting over(which you will have to do if you re-import your XSD)...
    XSLT is made for mapping XML to HTML or XML to XML. In the XI environment there are different mappings options availiable e.g: graphical (message) mapping, XSLT, Java , ABAP.
    XSLT is, compared to the other techniques, easy to learn and good to enhance. It has a worse performance than the other techniques.
    Usually it is the decision of the developer which mapping to choose looking at the different aspects of the requirement like message size, complexity of mapping and so on.
    For "An Overview of XSLT Mapping":
    https://www.sdn.sap.com/irj/sdn/developerareas/java?rid=/webcontent/uuid/110ff05d-0501-0010-a19d-958247c9f798
    Few other links that might help you to understand XSLT in better way :
    http://help.sap.com/saphelp_nw2004s/helpdata/en/73/f61eea1741453eb8f794e150067930/content.htm
    https://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-code-samples/generic%20xslt%20mapping%20in%20sap%20xi%2c%20part%20i.pdf
    File to Multiple IDocs (XSLT Mapping)
    And also Refer these links
    Creating XSLT Mapping using STYLUS studio Editor
    xpath functions in xslt mapping
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/006aa890-0201-0010-1eb1-afc5cbae3f15
    Hope this helps.
    Cheers,
    Suryanarayana

  • Current datetime in xslt

    Hi ,
    I want to get the current datetime during my xlst tranform. I used the below codes but can not get it .
    xslt 1.0
    <xsl:stylesheet ...
    xmlns:ex="http://exslt.org/dates-and-times" extension-element-prefixes="ex">
    <xsl:value-of select="ex:date-time()"/> ...
    </xsl:stylesheet>
    error i got: the function date-time() can not be found.
    xlst 2.0
    <xsl:value-of select="current-dateTime()"/>
    error i got : the function current-dateTime() can not be found.
    Does anyone know how i can solve this problem? Any example or suggestion is welcomed.
    Thanks in advance.
    Dennis

    If that piece of xslt has any chance to succeed, you have to do either one of the modification.
    [1] Either you change the version attribute to 2.0. Oracle xslt processor is one of the earliest to get xslt 2.0 support at the time it is still a working draft. I think current-dateTime() xslt 2.0 function should be supported.
    <xsl:stylesheet version="2.0"[2] There are quite a bit of oracle proprietary extensions there. Hence, if you understand the suggestion(s) all along, it should do the task without appealing to the other extensions which may have their own functions to get the current date-time. This is how you should do for a test, keeping the version="1.0" unchanged.
    <xsl:stylesheet version="1.0"
    xmlns:date="http://www.oracle.com/XSL/Transform/java/java.util.Date"
    xmlns:xref="http://www.oracle.com/XSL/Transform/java/oracle.tip.xref.xpath.XRefXPathFunctions"
    xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
    xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:ora="http://schemas.oracle.com/xpath/extension"
    xmlns:ehdr="http://www.oracle.com/XSL/Transform/java/oracle.tip.esb.server.headers.ESBHeaderFunctions"
    xmlns:ns0="http://www.example.org"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc"
    xmlns:ids="http://xmlns.oracle.com/bpel/services/IdentityService/xpath"
    xmlns:hwf="http://xmlns.oracle.com/bpel/workflow/xpath"
    exclude-result-prefixes="xsl xsd ns0 xref xp20 bpws ora ehdr orcl ids hwf date ">
    <xsl:template match="/">
    ...etc
    <TimeStamp><xsl:value-of select="date:toString(date:new())"/></TimeStamp>
    ...etc
    </xsl:template>

  • BI Admin Tool and XSLT transformation for XML data source - How it works ?

    Hello,
    There is a possibility to import data from XML data source using BI Admin Tool.
    In the import window we can point XSLT file. What is the purpose of that XSLT field?
    Why I am asking ?
    I thought it is smth like XSLT processor, but simply it doesnt work.
    What I did:
    - I pointed XML data source file
    - I pointed XSLT transformation file
    - Click OK, and still get the message that the XML file structure is not supported
    After that I transformed that XML file with some desktop XSLT processor using the same XSLT file, and I tried to connect that file directly using BI Admin tool.Then it works. So it means that the transformation is ok.
    So basically one question comes to my mind in that situation:
    What is the purpose of XSLT field in BI Admin Tool when it comes to XML data source ?
    (it doesnt look like XSLT processor)
    Greetings
    /Michal

    Hi Mariano
    Why you need to use XSLT for transforming XML file into ABAP table
    Code is a part of some ABAP report. Looks like it is reading a file from file system and updating table after transformation
    If you have requirement like you need to read XML file and then insert the data into a SAP table
    You can use
    File to RFC
    File to Proxy scenario using SAP PI.
    Please provide more inputs on requirement to help
    Thanks
    Gaurav

Maybe you are looking for