XSLT transformation format-number into strange characters

Hi, Experts,
    When I excute following code to translate a string number DEBIT TYPE C(60) into xml, the result has strange characters.
<xsl:value-of select="format-number(sap:if(string(number(DEBIT))!='NaN',DEBIT,0),'0.0000000000')" />
    If DEBIT is empty, the correct result should be:
0x3000 0x2E00 (0x3000)*10       = 0.0000000000
    but actually, the result will be following in some cases:
0x3000 0x2E00 (0x0F77)*10
    in some cases the result will be
0x3000 0x2E00 (0x2600 0x2300 0x3000 0x3B00)*10
    What I mean in some cases, I ran the same code on different NW system. I also changed the user profile by NW menu System->User Profile->Own Data, the result won't change whether I use American Comma-Dot or European Dot-Comma.
    Can anyone give some advice on the code? Or there is some patch to solve it?
    Thanks and Regards
Davin
Edited by: Davin Wang on Jul 17, 2008 3:15 PM

Hi Davin,
do chk the condition it is not correct
<xsl:value-of select="format-number(sap:if(string(number(DEBIT))!='NaN',DEBIT,0),'0.0000000000')" />
do chk it
Thanx
Sampath

Similar Messages

  • Letters transform into strange characters

    We use an editable pdf-document for testing students for legal spelling exam. However, when using the danish letters æ, ø and å in form fields, these letters look fine when typing them, but as soon as one leaves one field to edit others the characters change to some strange ones. Have anyone a suggestion for a solution of this problem? Thank you in advance.
    Version Adobe Reader version XI, version 11.0.06. Language setting is Danish

    Does the same thing happen when you test the forms in Acrobat, when you design the form? Or, is it fine in Acrobat and only wrong in Reader?

  • Need to format month into three characters in SSRS Expression

    I am using the following expression to place the month in the heading of a column.
    =MonthName(Month(DateAdd("M",-1,Now)))
    The expression above gives me the previous month, but I need to have it as "Jan", not "January".
    Can someone help me with an expression that will give me the three character month name instead of the full month.  I've tried substituting the "M" with "MMM", but get an error.  I've also tried "Mon", but again, I
    get an error.
    Help?  Many thanks in advance.

    Hi Guoxiong,
    Above expression is not working, its need some correction.
    In above expression you are getting month number then doing formatting.
    Always one rule of format is its format on date., so just remove the Month like I did below:-
    =format(DateAdd("M",-1,Now()),"MMM")
    Thanks
    Prasad

  • Is there some place where I can submit a ticket ? Seems like FF limits DOM elements' width and height to 10,000,000px since it transforms this number into scientific notation. e.g. 10,000,000px becomes 1e+7px which obviously can't be interpreted. Cheers

    I've reproduced this issue from FF 3.6.13 on windows XP and mac osx 10.6.8.
    On FF 3.6.13 the number of pixels limit seems lower with exactly 8,388,607.

    The 12" PB internals are a bit more complex, for PB's. If you don't want to replace the hard drive yourself or pay someone to install it, you could always get an external firewire hard drive, and use it to boot from and for general usage. Would have to be firewire, since the PB won't book from a USB device. One example of what you could get is a 160GB external hard drive: http://eshop.macsales.com/item/Other%20World%20Computing/MS4U5160GB8/ . All the choices with that case are listed here: http://eshop.macsales.com/shop/firewire/on-the-go
    Have you called any Apple Authorized Service Providers to see what they would charge to install a drive for you? Whether you bought it or they supplied it? You can find a local one in the US at http://www.apple.com/buy/locator/service/

  • Adobe Reader displaying strange characters

    Hello! I am writing my uni task. For that I downloaded a .pdf document from my university, which has text boxes for me to fill in. I do not know how/with which program this file was created. I first tried dealing with it using the Windows 8 Reader app. Several times, when I switched from the document to the Desktop and back, all my text was converted into strange characters. I started saving the document before switching, and this seemed to solve the problem at first. But then at some point I saved and closed it, and when I opened it the next time, only the box I modified last (with an essay) was converted into strange characters. When I copy it somewhere, the text does not appear. I tried opening the thing with Adobe Reader. It does not convert anything into weird symbols, but the ones from the previous time remain. Is there any way I can get the information back?
    Here's the whole 'strange character' bit:
    ý«†z´y,o/>§™I$2ž|‘M¥8"Žb2;¸[áÔeìb⁄æÉ÷ײݵßScÄ−¹<¹˚ëÞG+VW5²!1°%ZÔ;‘ƒÀ¤|ªł.W‚nb·Ü`ø}=†mû⁄À¦• ¸ßÁºþÜ”ãØˇÂ²ÑrŸ–)·ô†+Ù˘¬ì¶4<Àqc.®ªSG”˛¹„+ö:@€‚Å˝å²M«ÚŸ/E¼¿flüUÌÈü…qªÉ³pÉ2ôù$fiÍævflÓrîsƒ[email protected]_ 8;¢DîuAÑ˙Ô¨ÿ,s<“Ñ·Ü䙟tàZ,Ö½¨#ee˚˛üBwê!MŠU¸Ÿ€¹*øƒN‰×{hø?;Ô·Î'k$;Í÷Qýw~&—ł„Aå”MTì¹⁄¿tË@˘/J ÿóS˝
    ý_l'Di
    õ#J³ß0O8Á@žöÃfB%Ôî{
    Ûõz8Á&´ØëU^¤mDèüV½â~žË@ØÀ*Ý−›D‘–[email protected]šTÁ–U-§þR˘
    çU ió¦(fH€RBRK%nÁ0þ$½Œ‰¢@˛x§{±'QRÕéKŵ«uÌ2>å΂úëoNH¢-c|d‰AOÓÎgS×eGzł⁄Dd¢&łEyþ•½w;;"÷+B‰
    Á ‹rn+8‰|JeÐ˙Š6Âî÷;x^¯~j⁄TÓa¦O˙qé=:*v¬à^!·þá¡®SL=Ìáh)¬øxthj™ŽÁ–½…¬Ü‚łþ ÇÌÌ„¶"KÉ4$ô‰'š−°íŽùÜÑHÜ>o¶y%˛U(Í÷f–wøÙ±⁄[¢ý [Å‚Œ‘ß?˛−dĹ–ï4¾&ôzÚÃSåÁ¡Ëä¡¡DG¡ŁøO7øã|ò‹áï…Q³Ê;˚@w|¤C¡¨ÝôÏŽ´ÎgÙ¿ö—‡óÊ—F¼ñ}¢¡ù¹ê˜Š˜Û›·«íÿ `Qùж×g”˛Ï;–úÍ‹OU'†ah„y’‹èa´ŸÏ°èwP׃—‚
    üp˝qŸ±æŸøŒ¼ýìł˝‡u‚dSf0ùÉ\FŽ˛¤mW;ôͤäühUÙv˛˛¯aˆý1Ø`âÇ˝òX>&
    éÝߊɉ˛>á–·ÈýùÒ…ªŁ =fi‡llv¸èøÜ÷~ûº÷0flÁMndejŽf-&°H.¥æµÁ⁄'¤zJÚª6•ç9¿öÝd-iðcÐöz›
    »}g¤ł)4¡PŽXüª¤ÌT«¦Èl©œºG£§3êêH˜-]ûß˝%ëÐh›WÔ˘˜B–Ùî!)CÃäÁ?P–»˝Û¥¬|T‰ÆÈà⁄A*(é2QÓJx™K?ÔöGwìŒÝz HèÓT•²‹ÿf~SzúúDQ]ü“¥‘fitú¸E_afN"³~/flõ˘§˚Þ§²UÉùtN&º¬tÆ#uzMP=<÷û‹˜¸ù−HùS>šˆ]1]¨—˜ÖhÌŁ\°rv˘þ
    ‚ãÓ»¬‘ŽVÏ°ÕL0H90chÃM®yb¶§J•V"çµÅ/”€Ðk⁄iÑNÚ[email protected]£|ös‚÷Þ‚´k§)äoıÃLöÒ5ɺ°›îEÀ‚Ä–ç±]ꚧýE›=q¸÷ÿü žDe¾xüı¡:&˚B¢‰jÈMö6»ł¬6 /å•‚ÚÿÊ Ó±t'ùT㓵ëS
    ~J[DÜiîœ[þpéjDævø@ÊäsߎÈØïÅàUÛÏwå&¼t−©•ır
    —õ¹íOòꤥ²`÷LZKrd€J6ÄÎÛÅ−|W0Nš¸@…r«qt’liÑçÌY’æÙ!“Sâ<†Æh‡z|4Aš*£fl˜ôñsÁʘl±W²
    ï¦ncÓ,»ÒùYµÛ™'T©Ì727˝^2?rNË˚Ç¡¿¢+ßu–H2e¸©CB#˚ÁºƒâÇÅÖK−"2ÍiŸRO0 ›^"˛"−âÉ×íôòCBí[aõãÑ,¶^³Nh–S¨íï?Øł9r\¦7
    kg‚Á¤0?t Éà(Ô$>x·k(™Š°µ˘Xòþ÷£−»á€IâyòLl3DõËò0TËÌåk–fi¶åA3Õ¨gˇÿüf‘±yùÈ{¦›—šÃ§®ãI;ûwhȘ4ZUdv-y‚t|jrÆÛ +/ÞŁ(kł¬<¡e:˙O[Ê'–6ö¨M¦«ïæÈž§$4Nœ9Ú¢½òìóvàfl˜÷§Ñflgd¦³N³í[´Ì%Q5r˜Ýl
    ÛpXøïåwü—Ö²¯ê⁄ûiıÎÖ„&´ø¥º¾¬(m‘iAŽéü_œé°&LøÊhÚü³œcÞ÷hR™ÌIª3U7áõüXT¡`s¥˚“ˇÂŽ
    Î@ÔrÞ+dµ˝LA>]t;pˆZע—Øi'çÞŠ¿
    kª"~ýl5fi,ÿ6uP&‹ã+‚¨(̯K_è“å$ÍÁº#F¤Ö¦ø˝ÿµuX6_−
    Ëp¼Me‹¿ùöÖ°bS<¯¥P©ú½éÀ
    î e½íšND¿“N®”Z(ß(j%;=Há–®† A.fl*
    9Ï−²È§™,ÐS2AÒÀ!ÇÜMRœê‰G£þÜàOB˙_⁄˚7‡¶»²j÷ÅÚe½*x¢˝¸‚©nSŸ!ÃùGtÕP7&ł½R7(ýñ‹ÿAæ¦?|uÐWƒ˜¯¬BHj`êf Ì]3Ýßäîe˛
    qË}óÉSŁ¢S“†#å*‹[email protected]†®ï#eVç>0×sI›åRþPuÙ'sèf§È'™BV͵ƒ˘vÅ¢ùÁÍu/¬A¬3`¶¥ô*®ŽùÕ”£‡a7ˇlˇoÜ−
    zÂÏBÁËmC˘ß×z{#lfl⁄õmł?íTM¥u¸š\L†áFı!-½šÀ‚ž¦AÅŽdZqê‰)Iü"˘š™Ñظ¸<Šıv¢U',)åX#−ßÅ\YƒÿŒ¶¥}ÏÄÚ£ØÍ ökC›fìLJ¶u÷¹öØêX9XWtùã,š"ÓxòÇô„¼N!ó:[ªˆ³ï•Łõ±^çx#δsLe¤bY‡#Y׸©åFÌîlËCdàåºT-)K¸È>H9”Ñå|nå $fi°ûÄ$å4k’#˚r›Äîæ²è§fi:ZJEëä´ ý‘byŠ+w
    þz“Ç
    Éúñõ˘iMS¦C˘¸«.¶ÄµÚž431üPÐ¥{yŽó¯*O
    +ºiÝ7'òM€Fzä^GçÖºJ²™#E⁄Øwý˘P0-\»ˆêvhǪœ>Ð˘m˝íÜëŸG½#«?ÊÕeqIñ¬c`e
    [ŁHD˘W‘»˝žŸûøJÍŽ+UVÿGJ²îs~ƒ´õc”{úoL‹
    3„XŁ?`•ïâ—ıaDJ?¥cå2)Ï8^žVA"?MÀ0z±¼ä[°CwP%µ™8;kŠ/IÍ:2/_kNË˚Žþ"Ö²äÕºÒg£WjÆd$ÄMÑõe•;?ò[hÏ+PD˚ à×Óô¦¨àÚÄN†YPcЫ)#×ÈÔÙL˜7]ë%PÞÏ:p2ªıÚô;fl·¤˘íBŒP¬q_öx¤‡d™flйzCŽ7ÿbò×iqó ´!ø¡Šzh¯1Úr„£ı˛A1>=/õ#w㮈
    üqß]‚˘a¤óßäUÌå*[:/@†yóBÀ˙ŸÒtx1®PŒ!Ïóc?›‰‚ÉÀkt[§m§a7z¾ˇö¤¥ë/è€1˛,JlQ…¼S;h(§[email protected]Ð,ûÈ(−ön.Hq« ÍØ−¶ÞÁNØÔ_T”êDœwü˚Û.²\>—NŽr(Q¡OÌ¿¬?-kÓDO!ps˚¹Š?¥«T¦¾ø:õ+¬!˚G−×&¡pãÅ°-|Ê??ŁÂèÇžÉÄ¢m¥\a˛ME5c Q_&Ÿ.#/ÊKq:’HZb%\Òµ3ÀÌv˜stÆé@ͤCžzjú4Þ¢f ðH'g6¯¨ßËžÿ®tŸ}4:h\$‚lå3E_.¨%Ùx3FxGJF†ı˘~Gþłû[email protected]¦é9ÓÉi€çÊ ›µÖÔZúO~Ì×Ж;vÔáwQÖ1Ãì⁄†ÿ>i˚“ò0þ(ÖıƒN)xæA§©¾

    The document: https://files.acrobat.com/a/preview/71fb561e-78a2-44ae-8bd6-9df6520e9d1b
    The box I was talking about is the very last one.
    The Adobe ReaderI started using recently is version XI; the one I used when I started editing the document was Windows 8 Reader app by Microsoft, version 6.2.8516.0.

  • Is the XSLT format-number function supported by XMLType.transform()

    I am trying to use the XSLT format-number function in a stylesheet via myXMLType.transform(myXSL) without any luck. For example, <xsl:value-of select="format-number($myNum,'#,###.00')/>. This works ok under the java based XSLT engine.
    Is format-number supported by XML DB?
    I am running 9.2.0.5.
    Cheers
    Anthony

    I have upgraded to 10g and found that this now works.
    Cheers
    Anthony

  • XSLT Processor Bug? format-number() on large numbers

    For numbers 100,000,000.00 and higher, I'm getting extra digits and rounding errors.
    How can I use some custom Java code in the XSL stylesheet so the correct value is displayed (i.e. w/o rounding)? I'm getting a value of 100000000.00 and I need to insert the commas. Sometimes the correct value is displayed, other times, additional numbers are appended and the amount is rounded.

    The XSLT processor uses java.text.DecimalFormat under the covers as the XSLT 1.0 specification suggests. I would imagine any problems with format-number() actually boil down to problems with java.text.DecimalFormat.
    You can use Java Extension functions to perform custom Java in your stylesheet.
    See the file .\extfunc.html in the root directory of the XML Parser for Java V2
    distribution.

  • 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 &amp; 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;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

  • Strange characters when copy/paste from Word

    Hi,
    I have in Word u2018hellou2019 and when I paste it in the Notes of IR and save it, it turns into  018hello 019 so the apostrophes transform into these strange characters.
    I checked with Notepad, Excel and Wordpad and this issue does not occur, only for Word.
    Do you know why this happens ?
    It should be a Word/IE setting as this issue does not occur on a Terminal Server. Only on usersu2019
    workstations.
    Thank you
    Edited by: Mihai Olaru on Nov 1, 2008 2:43 AM

    Hi Shiva,
    Some styles for font of rich text aren't be kept when I copy the content from Word 2013 and paste into a wiki page from SharePoint 2010/2013(even SharePoint 2007 like this
    post) site as same as yours, it looks like a limitation.
    As a workaround, we can publish the Word content as a Blog article in SharePoint site, then copy the content from the blog page to the needed SharePoint page, it will keep the rich text content format, you can have a try.
    http://plexhosted.com/billing/knowledgebase/274/How-to-publish-a-SharePoint-blog-article-via-Microsoft-Word-2013-SharePoint-2013.html
    Thanks
    Daniel Yang
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Pages document turned to gibberish-strange characters in rectangles. Can't read underlying text (still there)

    I use a Pages document (password protected) as a frequent reference. It is 22 pages of text. Suddenly most text was replaced with strange characters, each encased in a little rectangle, so document was unreadable. Selecting a section of text, I could right-click and see that underlying text was still there, just not readable onscreen. Style was "Normal*." I don't know what the " * " means. I selected all and changed style to "Heading 9" on the list. All text reappeared, so my data is ok - for now (though not formatted as I want it). I can't trust Pages, however, and don't know what caused the problem or how to avoid it.
    Note that the style now shows "Heading 9*". I don't know why the " * ". I tried selecting all and making "Normal" the global style, but the strange characters wouldn't budge. Switching back to Normal brings back gibberish.
    Some text is Verdana; I just noticed that changing font also got rid of gibberish. Changing back to Verdana brought back gibberish.
    Note that not every line of text was changed to gibberish; some were just fine.
    Other Pages documents are fine - right now. I notice that there are asterisks in Style in other text documents.
    I'm an experienced computer user, new to Pages in the fall when it came with my MacBook Air. In this document, format isn't all that important, but I can imagine where this would be a huge disaster for other types of documents.
    Any help in figuring out what's going on most appreciated.

    Tom -
    "That sounds like Apple's Last Resort font, which gets used when for some reason the app forgets about the font being used.  Use Fontbook to make sure you don't have duplicate Verdanas on your machine.  Also try cleaning your font caches with Onyx or by doing a safe boot"
    Wow! Who would have guessed! Thank you for the advice; Fontbook revealed a number of duplicate fonts - ot Verdana, interestingly enough -  which I have now resolved. I then switched all text to Trebuchet MS, and everything reverted to normal. I can live with Trebuchet.
    This problem appeared on the same day (before or after I wasn't sure) I installed MS Office. Could this have caused the problem?
    Thanks for your prompt reply, explanation and solutions.

  • 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.

  • Format-number doesn't work with XSL and DW preview

    Hi All
    I'm creating XSL files to transform XML into HTML. However,
    the number formatting doesn;t seem to work in Dreamweaver. For
    example, if I specifiy:
    format-number(price,'$###,###.00'), I should get $7596.99. I
    actually get 7596.990000000001 in my Preview (no currency symbol,
    too many decimal places). If I do the same thing in another XSL
    editor (Xseleerator) I get: $7,596.99.
    This is REAL PAIN, as every time I do anything with number
    formatting, I need to open the XML and XSL in another product just
    to check the formattng.
    Can anyone shed any light on this?
    Thnaks
    Mark

    Try to declare the variable out side of the region
    <script> var tp1;</script>
    <div spry region ... >
    tab panel stuff
    <script type="text/javascript">
    tp1 = new Spry.Widget.TabbedPanels("tp1");
    </script>
    </div>

  • XSLT transformation: tamplate match="*" problem

    Hi everybody,
    I have some stupid problem with XSLT transformations. I use XALAN-J 2.7 to transform xml files. My xslt transformation can be downloaded from http://tesla.rcub.bg.ac.yu/~sing/xsd2rdf.xslt
    Problem is when I have in xslt file template defined with (match="*") it does not work. Transformation does not throw any exceptions; it just does not match nodes very well.
    Next XML schema can be used as test. So, if you transform this file(schema below) using e.g. XML Spy it will work fine, but if you transform it using JAVA it does not match all nodes. Any suggestions are welcome. Is it problem with XPath standard and XALAN implementation or what???
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema targetNamespace="http://www.openapplications.org/oagis/CoreComponents/1.90/Types" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cct="http://www.openapplications.org/oagis/CoreComponents/1.90/Types" elementFormDefault="qualified" attributeFormDefault="unqualified">
         <xs:simpleType name="Simple">
              <xs:restriction base="xs:integer"/>
         </xs:simpleType>
         <xs:complexType name="AmountType">
              <xs:simpleContent>
                   <xs:extension base="cct:Simple">
                        <xs:attribute name="currencyID" type="xs:integer" use="required"/>
                        <xs:attribute name="codeListVersionID" type="xs:float" use="optional"/>
                   </xs:extension>
              </xs:simpleContent>
         </xs:complexType>
    </xs:schema>
    Thanks,
    Igor.

    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.

  • XSLT transformation error when importing target group in CRM Survey cockpit

    Hi,
    I created a target group using the segment builder and exported that to a local file. Then when creating a survey using CRM survey cockpit (tcode: SURVEY) and trying to import the same target group from the local file; I get an error :
    "Error when applying a XSLT transformation"
    System Response
    Data transformation cannot be executed. Application functions that depend on the transformation cannot be executed
    I tried various file formats : RTF, TXT, XLS, HTML but still I get the same error. Export to XML option is neither available while exporting from segment builder nor while importing into Survey cockpit. The target group is not empty.
    Are there any settings to be maintained to resolve the error ?????
    Dhaval.

    Hi Suhel,
    Thanks for the response... as far as my understanding goes, the crm survey suite can be used for maintaining questoinnaires that are transaction specific. also the functionality of question tables and rows is not available in the survey suite but is available in the survey cockpit (tcode: SURVEY).
    However the same does not allow me to refer to the target groups created using the segment builder.... Is there a way I can use the target group created through the segment builder in the survey cockpit ????
    Dhaval.

  • 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.

Maybe you are looking for