Documentation of XSLT Transformation

Hi all,
Is there any documentation for the XSLT Transformation? Please.
Thanks.

Check This article
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c5b0d190-0201-0010-11b8-aabe27015acf
For [E-learning Tutorial|https://www.sdn.sap.com/irj/sdn/advancedsearch?query=xslt&cat=sdn_all#] clcik on first link of the page

Similar Messages

Configuring the XSLT transformation service

I need to use XSL-T 2.0 in a service. The documentation for XSLT Transformation says that an alternate service provider can be used. It says I need to supply a string value that represents the fully qualified name of the Java class to use for performing the XSLT transformation, such as org.apache.xalan.xslt.XSLTProcessor. The Java class used must extend javax.xml.transform.TransformerFactory and must be available to the class loader of the LiveCycle ES server.
The Saxon XSL-T engine supports the required interface, but I have not been able to install it successfully. In theory, it is a component that can be installed from the Components panel, but when I try that I receive the message "An error occurred. Please check the Eclipse error log for details". I have not been able to locate the error log.
Any assistance greatly appreciated.
--RKW

Thanks for the assistance. That turns out to be the right advice. If you want to use the Saxon processor, you need to put the following jars in the server\all\lib folder:
saxon8.jar
saxon8-dom.jar
--RKW

Performance of XSLT transformation

Hello everybody,
I´m trying to do some in-database XML transformations from one XML format to another with a rather complex xsl stylesheet of about 9000 lines of code which performs this transformation. At first I tested the XDK XSLT functionality by simply doing a Transformation over the JAXP API outside the Database. It performed not bad, altough the memory consumption was a little bit higher then Saxon or Xalan. After that I read about the possibilities of in-database transformation, which should consume less memory because of oracle´s xml features like scalable DOM, XML Indexing and Query Rewriting when using object relational or binary storage. So we loaded our testdata into the db (we are using 11gR2 on a test system with Intel Core2Duo @ 3GhZ and 3GB RAM), in different XML storage options (XMLTYPE CLOB, Binary, OR) and tried to do a XSLT transformation on the columns. But it isn´t working.
The db seems not to be able to cope with the transformation although the parser and processor should be the same as the off-database transformation that was working well (or am I wrong?). After half an hour we aborted because the db hadn´t finished the transformation yet (the off-db transformation of this 100KB XML took less then a second). We tried indexing the columns with XMLIndex, didn´t work out, we tried both XMLTYPE´s XMLtransform() and dbms_xslprocessor.processxsl(), same problem, the DB is working and working with no result, after some time we have to terminate. With a simple teststylesheet the transformation is doing fine but our complex stylesheet seems to be the problem.
My question is, why is the xslt performance so poorly with the complex stylesheet and why can I use the XDK Parser and Processor in an off-db transformation very efficiently but when doing the same transformation in the db it´s not working.
Hope you can help me out a little bit I´m really running out of ideas.
Greetz dirac

Hi,
The db seems not to be able to cope with the transformation although the parser and processor should be the same as the off-database transformation that was working well (or am I wrong?). No, the database built-in XSLT processor (C-based) is not the same as the XDK's Java implementation.
There's also a C XSLT processor available for external transformation and working with compiled stylesheets, it should outperform the Java implementation.
See : http://docs.oracle.com/cd/E11882_01/appdev.112/e23582/adx_c_xslt.htm#i1020191
We tried indexing the columns with XMLIndex, didn´t work out, we tried both XMLTYPE´s XMLtransform() and dbms_xslprocessor.processxsl(), same problem, the DB is working and working with no result, after some time we have to terminate. With a simple teststylesheet the transformation is doing fine but our complex stylesheet seems to be the problem.XMLIndexes won't help at all in this situation.
In my experience so far with the built-in engine, I've seen the best result when the XML document we want transform is stored as binary XML.
I don't know about the scalable DOM (or "lazy" DOM loading) feature described in the documentation, seems it doesn't support complex transformations, much like functional vs. streaming evaluation for XQuery.
Hope you can help me out a little bit I´m really running out of ideas.I'd be interested in a test case if you have the possibility (stylesheet + sample input XML). You can mail me at this address : mb[dot]perso[at]wanadoo[dot]fr
If you can't, could you describe what kind of transformation you're performing and how can I reproduce that behaviour?
Thanks.
Marc.

Problem getting xslt transform to work

I have the following ABAP Xslt transformation
<xsl:transform
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:sap="http://www.sap.com/sapxsl" version="1.0"
>
<xsl:strip-space elements="*"/>
     <xsl:template match="/">
          <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
               <asx:values>
                    <ALLIR_REIKNINGAR>
                         <xsl:apply-templates select="//Invoice"/>
                    </ALLIR_REIKNINGAR>
               </asx:values>
          </asx:abap>
     </xsl:template>
    <xsl:template match="Invoice">
    <REIKNINGUR>
        <REIKN_NUMER>
            <xsl:value-of select="cbc:ID"/>
        </REIKN_NUMER>
        <REIKN_AFRIT>
            <xsl:value-of select="cbc:CopyIndicator"/>
        </REIKN_AFRIT>
        <REIKN_UTGAFUDAGS>
            <xsl:value-of select="cbc:IssueDate"/>
        </REIKN_UTGAFUDAGS>
        <REIKN_MYNT>
            <xsl:value-of select="cbc:DocumentCurrencyCode"/>
        </REIKN_MYNT>
        <REIKN_TIMABIL_FRA>
            <xsl:value-of select="cac:InvoicePeriod/cbc:StartDate"/>
        </REIKN_TIMABIL_FRA>
        <REIKN_TIMABIL_TIL>
            <xsl:value-of select="cac:InvoicePeriod/cbc:EndDate"/>
        </REIKN_TIMABIL_TIL>
    </REIKNINGUR>
    </xsl:template>
</xsl:transform>
And the following XML input file
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="vodafone_xslt_namespace.xslt"?>
<Invoice
xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
xmlns:ext="urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2"
xmlns:qdt="urn:oasis:names:specification:ubl:schema:xsd:QualifiedDatatypes-2"
xmlns:udt="urn:un:unece:uncefact:data:specification:UnqualifiedDataTypesSchemaModule:2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ccts="urn:un:unece:uncefact:documentation:2"
xmlns:stat="urn:oasis:names:specification:ubl:schema:xsd:DocumentStatusCode-1.0"
xmlns:clm5639="urn:un:unece:uncefact:codelist:specification:5639:1988"
xmlns:clm54217="urn:un:unece:uncefact:codelist:specification:54217:2001"
xmlns:clm66411="urn:un:unece:uncefact:codelist:specification:66411:2001"
xmlns:clmIANAMIMEMediaType="urn:un:unece:uncefact:codelist:specification:IANAMIMEMediaType:2003"
>
     <cbc:UBLVersionID>2.0</cbc:UBLVersionID>
     <cbc:CustomizationID>NES</cbc:CustomizationID>
     <cbc:ProfileID schemeID="Profile"
     schemeAgencyID="NES">urn:www.nesubl.eu:profiles:profile4:ver1.1</cbc:ProfileID>
     <cbc:ID>PB1554421</cbc:ID>
     <cbc:CopyIndicator>false</cbc:CopyIndicator>
     <cbc:IssueDate>2011-12-31</cbc:IssueDate>
     <cbc:InvoiceTypeCode listID="UN/ECE 1001 Restricted" listAgencyID="NES">380</cbc:InvoiceTypeCode>
     <cbc:Note languageID="IS">Company name</cbc:Note>
     <cbc:DocumentCurrencyCode listID="ISO 4217 Alpha">ISK</cbc:DocumentCurrencyCode>
     <cbc:AccountingCost>2001523</cbc:AccountingCost>
     <cac:InvoicePeriod>
          <cbc:StartDate>2011-12-01</cbc:StartDate>
          <cbc:EndDate>2011-12-31</cbc:EndDate>
     </cac:InvoicePeriod>
</Invoice>
My problem is that this transformation does not work unless I completly strip out the namespace parts i.e. cbc:
How can I get the parser to read the tags with namespace part. And if the parser can not handle namespace in XML how can I go about reding the data into sap ?

I think you are trying convert the xml to an internal table because of // in apply-templates, then you need to change last XSLT program and include <item> tag inside the <xsl:template match="inv:Invoice"> template, see updated XSLT bellow.
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:inv="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
xmlns:ext="urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2"
xmlns:qdt="urn:oasis:names:specification:ubl:schema:xsd:QualifiedDatatypes-2"
xmlns:udt="urn:un:unece:uncefact:data:specification:UnqualifiedDataTypesSchemaModule:2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ccts="urn:un:unece:uncefact:documentation:2"
xmlns:stat="urn:oasis:names:specification:ubl:schema:xsd:DocumentStatusCode-1.0"
xmlns:clm5639="urn:un:unece:uncefact:codelist:specification:5639:1988"
xmlns:clm54217="urn:un:unece:uncefact:codelist:specification:54217:2001"
xmlns:clm66411="urn:un:unece:uncefact:codelist:specification:66411:2001"
xmlns:clmIANAMIMEMediaType="urn:un:unece:uncefact:codelist:specification:IANAMIMEMediaType:2003"
xmlns:sapxsl="http://www.sap.com/sapxsl"
version="1.0">
<xsl:strip-space elements="*"/>
<xsl:strip-space elements="*"/>
<xsl:template match="/">
    <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
      <asx:values>
        <ALLIR_REIKNINGAR>
          <xsl:apply-templates select="//inv:Invoice"/>
        </ALLIR_REIKNINGAR>
      </asx:values>
    </asx:abap>
</xsl:template>
<xsl:template match="inv:Invoice">
    <item>
    <REIKNINGUR>
      <REIKN_NUMER>
        <xsl:value-of select="cbc:ID"/>
      </REIKN_NUMER>
      <REIKN_AFRIT>
        <xsl:value-of select="cbc:CopyIndicator"/>
      </REIKN_AFRIT>
      <REIKN_UTGAFUDAGS>
        <xsl:value-of select="cbc:IssueDate"/>
      </REIKN_UTGAFUDAGS>
      <REIKN_MYNT>
        <xsl:value-of select="cbc:DocumentCurrencyCode"/>
      </REIKN_MYNT>
      <REIKN_TIMABIL_FRA>
        <xsl:value-of select="cac:InvoicePeriod/cbc:StartDate"/>
      </REIKN_TIMABIL_FRA>
      <REIKN_TIMABIL_TIL>
        <xsl:value-of select="cac:InvoicePeriod/cbc:EndDate"/>
      </REIKN_TIMABIL_TIL>
    </REIKNINGUR>
   </item>
</xsl:template>
</xsl:transform>
According to the XSLT program you need dclare an itab like this:
DATA: BEGIN OF ls_reikningur,
      reikn_numer(10) TYPE c,
      END OF ls_reikningur.
DATA: BEGIN OF ls_invoice,
      reikningur LIKE ls_reikningur,
      END OF ls_invoice.
DATA: lt_invoice LIKE TABLE OF ls_invoice.
And finally you need a call transformation in your abap code like this:
DATA: root_error TYPE REF TO cx_root.
DATA: lv_mess TYPE string.
TRY.
    CALL TRANSFORMATION zinvoice
       SOURCE XML lv_xml
       RESULT allir_reikningar = lt_invoice.
CATCH cx_root INTO root_error.
    lv_mess = root_error->if_message~get_text( ).
    WRITE lv_mess.
ENDTRY.

Oraxsl command line utility - xslt transform difficulty

I am having trouble understanding the documentation for the ORAXSL command line utility interface, as follows:
I have two sheets [XSLT transformation sheets], token.xsl and loop.xsl, which I am trying to transform into a single xsl sheet using ORAXSL command line.
token.xsl transforms a string of comma-separated values into single tokens (<value> elements, each of them contains one value).
loop.xsl expands special iteration elements (<loop:for> and <loop:while>) into recursive template calls.
Used together, I can parse a node containing comma separated values into an xml document with each value in its own node.

Hi
This is very simple (to the best of my knowledge)
sqlplus userid/password@hoststring @pl_sql_file_name.ext [arg1] [arg2] [arg3]
sqlplus - to invoke oracle
userid - is the login id into oracle db
password - is the password
hoststring - is the ORACLE_SID
pl_sql_file_name.ext - is the pl_sql file you wish to run
arg1, arg2, arg3 - the arguments that you may be refering in the pl_sql script. arg1 refers to &1 in your script and arg2 refers to &2 in your script and arg3 refers to &3 in your script.
Have fun!
Good Luck
null

Error in ABAP XSLT transformation

Hi,
Im trying to upload some data from XML to abap. But Im getting an error while transforming xml data to internal table.
Here are the details.
XML:
<?xml version="1.0" encoding="ISO-8859-1" ?>

<?xml-stylesheet type="text/xsl" href="ABAP1.xsl"?>
<conceptRevDecisionXml>
<projectInfo>
<projectId>P000755</projectId>
<stage>CON</stage>
<country>Ethiopia</country>
<region>AFRICA</region>
<teamleader>Priya Agarwal</teamleader>
<teamleaderfirstname>Priya</teamleaderfirstname>
<teamleaderlastname>Agarwal</teamleaderlastname>
<actionType>X</actionType>
</projectInfo>
</conceptRevDecisionXml>
XSLT: Transformation
<xsl:transform version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:sapxsl="http://www.sap.com/sapxsl"
>
<xsl:strip-space elements="*"></xsl:strip-space>
<xsl:template match="/">
    <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
      <asx:values>
        <PROJID>
          <xsl:apply-templates select="//conceptRevDecisionXml"></xsl:apply-templates>
        </PROJID>
      </asx:values>
    </asx:abap>
</xsl:template>
<xsl:template match="conceptRevDecisionXml">
      <xsl:for-each select="projectInfo">
       <xsl:value-of select="projectId"></xsl:value-of>
       <xsl:value-of select="stage"></xsl:value-of>
       <xsl:value-of select="country "></xsl:value-of>
       <xsl:value-of select="region"></xsl:value-of>
       <xsl:value-of select="teamleader"></xsl:value-of>
       <xsl:value-of select="teamleaderfirstname"></xsl:value-of>
       <xsl:value-of select="teamleaderlastname"></xsl:value-of>
        <xsl:value-of select="actionType"></xsl:value-of>
        </xsl:for-each>
    </xsl:template>
</xsl:transform>
Once I run the program...Im getting an error saying...ABAP XML Formatting error in XML node..
Im new to ABAP-XML parsing..Pls help me where Im going wrong..
Thanks in advance.
Regards,
Priya

Hi Priya,
you can try with the below,
1) Create a local ITAB with the structure of the XML,
TYPES: BEGIN OF t_data,
        projectid           TYPE char30,
        stage               TYPE char30,
        country             TYPE char30,
        region              TYPE char30,
        teamleader          TYPE char30,
        teamleaderfirstname TYPE char30,
        teamleaderlastname TYPE char30,
        actiontype          TYPE char30,
       END OF t_data.
2) Create an XSLT prog in "STRANS" with the below code,
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:sap="http://www.sap.com/sapxsl" version="1.0">
<xsl:strip-space elements="*"/>
<xsl:template match="/">
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
<asx:values>
<L_DATA>
<xsl:apply-templates select="//projectInfo"/>
</L_DATA>
</asx:values>
</asx:abap>
</xsl:template>
<xsl:template match="projectInfo">
<conceptRevDecisionXml>
<PROJECTID>
<xsl:value-of select="projectId"/>
</PROJECTID>
<STAGE>
<xsl:value-of select="stage"/>
</STAGE>
<COUNTRY>
<xsl:value-of select="country"/>
</COUNTRY>
<REGION>
<xsl:value-of select="region"/>
</REGION>
<TEAMLEADER>
<xsl:value-of select="teamleader"/>
</TEAMLEADER>
<TEAMLEADERFIRSTNAME>
<xsl:value-of select="teamleaderfirstname"/>
</TEAMLEADERFIRSTNAME>
<TEAMLEADERLASTNAME>
<xsl:value-of select="teamleaderlastname"/>
</TEAMLEADERLASTNAME>
<ACTIONTYPE>
<xsl:value-of select="actionType"/>
</ACTIONTYPE>
</conceptRevDecisionXml>
</xsl:template>
</xsl:transform>
3) Call the transformation as shown below,
CALL TRANSFORMATION zxslt_project ---> "Name of the XSLT prog created above
SOURCE XML l_xml_str                           ---> Source XML string
RESULT l_data = l_data.                          ---> ITAB as in step 1 above
Regards,
Chen

Error when applying a XSLT transformation: No valid XSLT pro

Dear All,
I am getting following error when opening the "General Supplier Data" from Pre-Select Supplier.
Error Message: "Error message: Error when applying a XSLT transformation: No valid XSLT program supplied"
I have already read the related threads on SDN and checked the SAP Note 883896 and others. Even tried running the program UXS_DEL_NAVIGATION_NODE and UXS_ADD_MISSING_XSLT_NAME. But not able to solve the issue.
Kindly Help.
Regards,
Sagar

Hi Masa,
Thanks for reply. I have checked this note. As note suggests, S_DEVELOP auth object is assigned to the user. and it has value *.
Do I need to check anything else?
Regards,
Sagar

Error when applying a XSLT transformation

central instance
transaction SURVEY
Extras->Target Group Hierarchy-> Import from file
select file
Error when applying a XSLT transformation
dialog instance working

Hello Andrey Kuryanov,
Could make sure you describe the problem more clear as much as you can so that community can help you better.
Please provide more details with more detailed steps and actual error messge.
Thanks
Raja Pamireddy
Moderator

UTF-8 encoding in XSLT transformation

Hello,
I have a problem with a transformation of an ABAP structure into XML. I use the XSLT transformation for this.
My XSLT starts like this:
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:strip-space elements="*"/>
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
    <asx:values>
I tried many settings I could find posted on the internet, but I did not find one that would allow encoding to UTF-8.
It always encodes to iso-8859-1 which my interface partner cannot read.
Does anyone know a way to force encoding to UTF-8?
Adding a command like <xsl:output encoding="utf-8"/> did not help.
Thanks a lot!
       J. Euler

Hello!
I think I just solved the problem taking a different approach.
In a note here on SDN, a guy from SAP wrote, that the SAP XSLT processor is not able to code anything but the system's default to a string, BUT that it is able to code it to an xstring.
All I did now is add the tag
<xsl:output encoding="utf-8" indent="yes" method="xml"/>
to my xslt program and change the coding in the program accordingly.
The program code is now:
DATA: tempxstring TYPE xstring,
        temp_length TYPE i,
        conv      TYPE REF TO cl_abap_conv_in_ce.
CLEAR tempxstring.
TRY.
      CALL TRANSFORMATION
          zxxje_tst_xslt
        SOURCE omsregdatawebservice = wa_data
        RESULT XML tempxstring.
    CATCH cx_sy_conversion_base64.
    CATCH cx_sy_conv_illegal_date_time.
ENDTRY.
IF tempxstring IS NOT INITIAL.
    CLEAR: conv, temp_length, string_xml_result.
    conv = cl_abap_conv_in_ce=>create( input = tempxstring ).
    conv->read( IMPORTING data = string_xml_result len = temp_length ).
ENDIF.
Thanks anyways for all your help!
regards,
      Johannes Euler

ABAP XSLT transformation - XML to deep structure/nested standard table

Hi all,
I was struggling with this topic recently and couldn't find a single working example or description of a possible solution. So now that I've sorted it out, I did a quick example to elustrate how it works. Here is the code with XML embeded in it and the XSLT follows:
<HR>
<PRE>
*& Report Z_XML2ABAP
*& Author: Jayanta Roy
*& Date: 03/02/2010
REPORT z_xml2abap.
DATA input_xml TYPE string.
TYPES: BEGIN OF t_address,
        house_no TYPE string,
        street_name TYPE string,
        city_name TYPE string,
        phone_no TYPE string,
      END OF t_address.
TYPES: t_addresses TYPE STANDARD TABLE OF t_address with NON-UNIQUE KEY house_no.
TYPES: BEGIN OF t_person,
        firstname TYPE string,
        surname TYPE string,
        addresses TYPE t_addresses,
      END OF t_person.
input_xml = '<Friends>' &&
'<People>' &&
    '<FirstName>Homer</FirstName>' &&
    '<Surname>Simpson</Surname>' &&
      '<Address>' &&
        '<HouseNo>123</HouseNo>' &&
        '<Street>Evergreen Terrace</Street>' &&
        '<City>Springfield</City>' &&
        '<PhoneNo>011212321</PhoneNo>' &&
      '</Address>' &&
      '<Address>' &&
        '<HouseNo>7G</HouseNo>' &&
        '<Street>Neuclear Power Plant</Street>' &&
        '<City>Spring Field</City>' &&
        '<PhoneNo>911</PhoneNo>' &&
      '</Address>' &&
'</People>' &&
'<People>' &&
     '<FirstName>Bart</FirstName>' &&
     '<Surname>Simpson</Surname>' &&
       '<Address>' &&
         '<HouseNo>123x</HouseNo>' &&
         '<Street>Evergreen Terracex</Street>' &&
         '<City>Springfieldx</City>' &&
         '<PhoneNo>011212321x</PhoneNo>' &&
       '</Address>' &&
   '</People>' &&
'</Friends>' .
DATA lt_person TYPE STANDARD TABLE OF t_person.
TRY.
    CALL TRANSFORMATION xslt_person
    SOURCE XML input_xml
    RESULT all_people = lt_person.
CATCH cx_root.
    WRITE 'Problemo!'.
ENDTRY.
WRITE 'Now, debug the program to see the values read from the XML'.
</PRE>
<HR>
and here is the XSLT Transformation program (xslt_person):
<HR>
<PRE>
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                    xmlns:sap="http://www.sap.com/sapxsl" version="1.0">
<xsl:strip-space elements="*"/>
<xsl:template match="/">
    <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
      <asx:values>
        <ALL_PEOPLE>
          <xsl:apply-templates select="//People"/>
        </ALL_PEOPLE>
      </asx:values>
    </asx:abap>
</xsl:template>
<xsl:template match="People">
    <ALLMYFRIENDS> <!This element name is not relevent... needed to just group the loop>
      <FIRSTNAME>
        <xsl:value-of select="FirstName"/>
      </FIRSTNAME>
      <SURNAME>
        <xsl:value-of select="Surname"/>
      </SURNAME>
      <ADDRESSES>
        <xsl:for-each select="Address">
          <ADDRESS> <!This element name is not relevent... needed to just group the loop>
            <HOUSE_NO>
              <xsl:value-of select="HouseNo"/>
            </HOUSE_NO>
            <STREET_NAME>
              <xsl:value-of select="Street"/>
            </STREET_NAME>
            <CITY_NAME>
              <xsl:value-of select="City"/>
            </CITY_NAME>
            <PHONE_NO>
              <xsl:value-of select="PhoneNo"/>
            </PHONE_NO>
          </ADDRESS>
        </xsl:for-each>
      </ADDRESSES>
    </ALLMYFRIENDS>
</xsl:template>
</xsl:transform>
</PRE>
<HR>
HTH,
Jayanta.

thanks a LOT Jayanta..
I was looking for an XSLT example for some time.. this one atleast got me started in the right direction..
THANKS

XSLT transformation in XML to ABAP: special characters issue

Hi,
I am parsing well-formed XML file that has the following data (:
<projects><project><name>Wallis & Futuna</name></project></projects>
I use XSLT transformation:
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sap="http://www.sap.com/sapxsl" version="1.0">
<xsl:strip-space elements="*"/>
<xsl:template match="projects">
    <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
        <PROJECTS>
          <xsl:for-each select="project">
            <PROJECT>
              <NAME>
                <xsl:value-of select="name"/>
              </NAME>
            </PROJECT>
          </xsl:for-each>
        </PROJECTS>
      </asx:values>
    </asx:abap>
</xsl:template>
</xsl:transform>
If I use the above example without &amp; everything works fine, but the original XML fails with exception CX_XSLT_DESERIALIZATION_ERROR and message "Error during deserialization". Googling around did not give an answer.
Any words of wisdom?
Edited by: Alexei Isaev on Apr 26, 2011 5:04 AM
Edited by: Alexei Isaev on Apr 26, 2011 5:05 AM

Hi,
Please visit the following link for reference.
http://help.sap.com/abapdocu_70/en/ABAPCALL_TRANSFORMATION.htm
Thanks & Regards,
Harish

XSLT Transformation problem

Hi,
hope anybody can help.
I try to transform a object to another object via XSLT transformation.
Here is my coding :
DATA: wa_transformation TYPE y0dpl_structures.
DATA: obj_import TYPE abap_trans_srcbind_tab,
        wa_import TYPE abap_trans_srcbind.
DATA: obj_export TYPE abap_trans_resbind_tab,
        wa_export TYPE abap_trans_resbind.
DATA: obj_data TYPE REF TO data.
* Get transformation data
SELECT SINGLE *
INTO wa_transformation
FROM y0dpl_structures
WHERE filetype = i_file_type.
* Create table with internal structure
CREATE DATA e_data TYPE (wa_transformation-structure_name).
wa_import-name = 'IMPORT'.
GET REFERENCE OF i_data INTO wa_import-value.
APPEND wa_import TO obj_import.
* Call transformation
CALL TRANSFORMATION (wa_transformation-transformation)
SOURCE (obj_import)
RESULT (obj_export).
i_data is a import parameter from type "ref to data".
My problem is, that "Call transformation" makes a shortdump when calling them.
Regards,
Anton

Found a solution for my problem. Now it works!
DATA: wa_transformation TYPE y0dpl_structures.
DATA: obj_import TYPE abap_trans_srcbind_tab,
        wa_import TYPE abap_trans_srcbind.
DATA: obj_data TYPE REF TO data.
DATA: wa_return TYPE bapiret2.
FIELD-SYMBOLS: <data> TYPE ANY TABLE.
* Get transformation data
SELECT SINGLE *
INTO wa_transformation
FROM y0dpl_structures
WHERE filetype = i_file_type.
IF sy-subrc IS INITIAL.
* Create table with internal structure
    CREATE DATA e_data TYPE STANDARD TABLE OF (wa_transformation-structure_name).
    ASSIGN i_data->* TO <data>.
    wa_import-name = 'IMPORT'.
    GET REFERENCE OF <data> INTO wa_import-value.
    APPEND wa_import TO obj_import.
* Call transformation
    CALL TRANSFORMATION (wa_transformation-transformation)
    SOURCE (obj_import)
    RESULT export_data = e_data.
ELSE.
    MOVE: 'Y0_DPL' TO wa_return-id,
           'E'      TO wa_return-type,
           '108'    TO wa_return-number.
    APPEND wa_return TO e_return.
    CLEAR: wa_return.
ENDIF.

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

XSLT transformation for XML to ABAP internal table

Hi, can anyone please tell me how it should be the xslt tranformation to conver this xml
<Embargos_ARBA_DOC>
     <ns:Embargos_ARBA_MT
          xmlns:ns="un:swissmedical:sap:proxy:embargos_arba:file">
          <Embargos_ARBA_MT>
               <FECHA>20081101</FECHA>
               <CUIT>50000002124</CUIT>
               <MONTO>0000013794090</MONTO>
               <RAZON_SOCIAL>RAUL ARMANDO CUNQUEIRO S.A.C.I.</RAZON_SOCIAL>
          </Embargos_ARBA_MT>
          <Embargos_ARBA_MT>
               <FECHA>20081101</FECHA>
               <CUIT>55000001456</CUIT>
               <MONTO>0000001144410</MONTO>
               <RAZON_SOCIAL>PARODI ESTEBAN ARMANDO</RAZON_SOCIAL>
          </Embargos_ARBA_MT>
     </ns:Embargos_ARBA_MT>
</Embargos_ARBA_DOC>
to this abap Table....
DATA: BEGIN OF i_embargos_arba_doc occurs 0,
          fecha TYPE d,
          cuit TYPE char11,
          monto TYPE char13,
          razon_social(120),
        END OF i_embargos_arba_mt.
so i can transform it with this sentence
      CALL TRANSFORMATION ('embargos_transformation')
        SOURCE XML source
        RESULT Embargos_ARBA_DOC = embargos.
pls i need help because i am unable to create this xslt transformation...
I will give the highest rewards points to the one who can help me.
thanks!
mariano

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

XSLT Transformation

Hi,
I am trying to upload one xml file and filling an internal table with the content and a XSLT transformation. After uploading the file and make the first transformation i obtein one string with all the fields without tags and separated by #. so when i try to call transformation for filling the internal table i obtein the exception cx_xslt_exception with the message 'No valid source context supplied'.
I would like to know if i am having poroblems with unicode characters. Is there any example made in sap that i can test or does anybody have had any similar problem?.
My string
<?xml version="1.0" encoding="utf-16"?>#######S####L####08##2######
Thanks in advance
regards

Hi Verma,
You're not transforming anything from your input to the output shown. You're actually constructing a new Output. I don't see anything being transformed from input to output.
Anyway, if you need a XSLT to be used to get the above Output in map, following XSLT shall help you:
<?xml version="1.0" encoding="UTF-16"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:msxsl="urn:schemas-microsoft-com:xslt" xmlns:var="http://schemas.microsoft.com/BizTalk/2003/var" exclude-result-prefixes="msxsl var s0" version="1.0" xmlns:s0="http://xmlns.service/1" xmlns:ns1="http://xmlns.types/1.0" xmlns:ns0="http://xmlns.OutService/2">
<xsl:output omit-xml-declaration="yes" method="xml" version="1.0" />
<xsl:template match="/">
<xsl:apply-templates select="/s0:Request" />
</xsl:template>
<xsl:template match="/s0:Request">
<Output xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://xmlns.OutService/2">
<outContext xmlns:ns0="http://xmlns.OutService/2" xsi:type="ns0:ReferenceContext" xmlns="http://xmlns.types/1.0" />
</Output>
</xsl:template>
</xsl:stylesheet>
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Documentation of XSLT Transformation

Similar Messages

Maybe you are looking for