Transforming values in XSLT

Hi,
I needed some help with XSLT.
I have a table which is returning me values in the following way 1,2,3,4,5,6 and I am suppose to put it in my element in the following way
<root>
<e1>1</e1>
<e1>2</e1>
<e1>3</e1>
<e1>4</e1>
<e1>5</e1>
<e1>6</e1>
</root>
Is there a good way in XSLT that I can do this?
Thanks

Hi,
I'm assuming you have a string like"1,2,3,4,5,6", with comma separated values and you want to translate that into xml...
It would be pretty easy to do it in XSLT, but the problem is Oracle XSLT does NOT implement xpath tokenize function... :(
So alternatively, you can do it in BPEL using the following approach...
http://soawork.blogspot.com.au/2012/08/delimited-string-to-xml-in-soa-11g.html
If you strictly need that into a XSLT, you can create a template combining string manipulation with some recursiveness...
Cheers,
Vlad

Similar Messages

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

How to get Final Transform value for a 3DLayer after Camera is applied?

Hi,
I need to export final transform values (position, rotation, scale, etc) from a Layer. I used ProjDumper example to extract the values. But I'm having trouble if the Layer is a 3D Layer and there is a Camera, because the Camera will affect the 3D Layer and hence transform it.
For example, the initial position of a Layer is in the centre of the screen (let say position 100,100). But after I adds a Camera and change the Camera properties, the Layer is seen on the top left on the screen (0,0).
So given a Layer and a Camera, how can I get the final transform values of the Layer? In other words, how can I transform from Composition coordinate to Camera coordinate?
Thanks,
Klarinda

Hi Brooce,
Given the Footage-type 3D Layer A & time T, I've tried the following combinations:
AEGP_GetLayerToWorldXformFromView(A, T, T, transformMatrix)
AEGP_GetLayerToWorldXformFromView(A, 0, T, transformMatrix)
AEGP_GetLayerToWorldXformFromView(A, T, 0, transformMatrix)
but they are all giving the same value as
AEGP_GetLayerToWorldXform(A, T, transformMatrix).
I've tried to change the Camera properties (focal length, zoom, etc) but AEGP_GetLayerToWorldXformFromView always gives the same value regardless of the Camera properties.
I also tried to put in the Camera Layer instead of footage-type Layer to the function, but the result of AEGP_GetLayerToWorldXformFromView is always the same as GetLayerToWorldXform, and the Camera properties doesn't affect the AEGP_GetLayerToWorldXformFromView function.
So my question is, why the AEGP_GetLayerToWorldXformFromView is not affected by Camera and why does it always give same result as AEGP_GetLayerToWorldXform?
Thanks.

Change a attribute value with XSLT before importing an XML

I need change the attribute value with XSLT before importing an XML
<table class="x" style="width="50pt">...
I have to divide by 200 the value of "width", and the result multiplied by 100:
(50/200) * 100
It's possible with a XLST?

Hi,
Yes you can do this via XSLT.
You can try similar to the one below:
<table>
   <xsl:attribute name="width">
     <xsl:value-of select="((./width) div 200)*(100)" />
   </xsl:attribute>
</table>
I have not tested yet... Try it....
Green4ever
(I am back after long time)....

Fonts changed to Arabic in the Transformation Values of Smart Cursors

Something wierd has happened in my InDesign CS5. The fonts in the Transformation Values of Smart Cursors have changed to Arabic!!! How to I get them back in English? And can I choose the font?

Gents, no wild goose chasing please
The default font for your documents has nothing to do with the interface font.
The interface font is a modified Myriad Pro, or perhaps its source was Myriad Web, the screen-optimized nephew -- and it's "modified" because it also contains characters for space, en-space, hard return, tab, etc., as well as tons of extra characters to display in the Find and Change box (you may never have noticed this before but the Find/Change edit fields can display an enourmous amount of characters). It probably contains some of the interface graphics as well.
Daniel, why do you think this is Lucida Grande? I can't tell the difference, but here is how the Arabic numerals 0 to 9 appear in my Find/Change dialog:
displayed with ID's "native" font, independent of any selection in the document. Do these match the ones on your screen exactly? If so, ID itself is confused. If not, there must have gone something wrong with your native font in ID. Either way: re-installing InDesign ought to fix it. Peter Spier can point you to the required steps to ensure a clean install, and how to safeguard your personal preferences first.

Get Node Value in XSLT

Hi all.
Maybe a simple question but, I haven't done yet.
In BPEL, when I need to get a node, I use getVariableData XPath function, for example:
count(bpws:getVariableData('MtlSystemItemsBESB_OutputVariable','MtlSystemItemsBCollection','/ns7:MtlSystemItemsBCollection/ns7:MtlSystemItemsB')) to get the number of lines returned from the service call.
Now, when I use XSLT transformation in ESB, I don't have a variable to extract the value from. So, how do I use XPath expressions that involve node-set return values?
I tried something like count('/ns7:MtlSystemItemsBCollection/ns7:MtlSystemItemsB') but it does not seem to work.
Thanks
Denis

Hi Denis,
count('/ns7:MtlSystemItemsBCollection/ns7:MtlSystemItemsB') should work as expected. Have you double checked your XPath (namespace, elementnames, etc.)?

Using transform api with xslt and DOM Nodes

Hi,
when trying to transform a xml document with xslt using the javax.xml.transform api
providing an element node of a previously parsed document, I find that absolute
paths are not recognized.
The following program shows what I am basically doing (the class can be executed
on the command line providing a stylesheet and xml instance):
import java.io.*;
import org.w3c.dom.*;
import javax.xml.transform.*;
import javax.xml.transform.dom.*;
import javax.xml.transform.stream.*;
import javax.xml.parsers.*;
class Transform {
public static void main(String [] args) throws Exception {
     TransformerFactory tfactory = TransformerFactory.newInstance();
     Transformer transformer = tfactory.newTransformer(new StreamSource(args[0]));
     DocumentBuilderFactory dfactory = DocumentBuilderFactory.newInstance();
     DocumentBuilder parser = dfactory.newDocumentBuilder();
     Document doc = parser.parse(args[1]);
     Element domElem = doc.getDocumentElement();
     // workaround
//     StringWriter out = new StringWriter();
//     Transformer id = tfactory.newTransformer();
//     id.transform(new DOMSource(domElem),new StreamResult(out));
//     String xml = out.toString();
//     transformer.transform(new StreamSource(new StringReader(xml)), new StreamResult(System.out));
     transformer.transform(new DOMSource(domElem), new StreamResult(System.out));
transformer.clearParameters();
If I use this on e.g.
xsl:
<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output indent="yes" encoding="ISO-8859-1" method="xml"/>
<xsl:template match="/">
<xsl:value-of select="/foo/bar"/>
</xsl:template>
</xsl:stylesheet>
xml:
<foo>abc<bar>def</bar></foo>
I get
<?xml version="1.0" encoding="ISO-8859-1"?>
abcdef
instead of
<?xml version="1.0" encoding="ISO-8859-1"?>
def
I think this is due to the fact, that the transformation does not recognize
any absolutely adressed xpath correctly.
From what I read in the API docs, I think what I'm doing should be ok.
So: did I misunderstand something or is this a bug in the java libraries?
I'm using j2sdk 1.4.1_01 on i386 linux.
If I use the commented code (serializing the xml and doing the transformation
with a StreamSource, that has to be parsed again), everything's fine.
Of course it would be easier to parse the file directly in the example but in the
real program, I already have a dom tree and want to transform a part of it.
Any help appreciated.
Thanks, Morus

why?
that's all the point of XSL: define what part of your
XML you want in your XSL templates, there is no need
to prepare a sub-DOM of your DOM.
Ok. Right. That's an alternative.
The problem remains, that there are some stylesheets originally written
for the current solution and though they should work with the whole document
as well, it's not certain.
Actually I don't know if this ever worked. I did neither write this code nor maintained the system so far.
btw. you would be faster by giving a StreamSource to
your transformation.Probably yes. But that would imply to rewrite a lot of code.
What is happening is:
there is a SOAP answser containing a xml document as the result parameter.
The SOAP answer is parsed (I guess by the soap classes already) and the
result xml is extracted. That's where the element node I'm trying to transform
stems from.
Besides, I still don't see why DOMSource takes any node if only document nodes
work.
Thanks, Morus

Transforming XML using XSLT more than once

Hi,
I am trying to transform an XML Document object in Java. However, it requires 2 transforms as each of them is complicated and needs to be generic enough for use by different XML strings. So I have a single XML string and two XSLT files.
Currently, I am using the Java transformer to perform both the transforms one after another. However, I was wondering if there is a function within XSLT or Java that would allow performing the second transform on the result of the first transform without having to resort to multiple calls from within Java.
Thanks a lot.
Jay Badiyani

http://xml.apache.org/xalan-j/samples.html#usexmlfilters

Error in generating a new XSL Transformer from large xslt File

Good day to all,
Currently I am facing a problem that whenever i try generating a Transformer object from TransformerFactory, I will have a TransformerConfigurationException threw. I have did some research from the net and understand that it is due to a bug that JVM memory limit of 64kb. However is there any external package or project that has already addressed to this problem? I have checked apache but they already patch the problem in Xalan 2.7.1. However I couldn't find any release of 2.7.1
Please help
Regards
RollinMao

If you have the transformation rules in a separate XSLT file, then, you can use com.icl.saxon package to get XML files transformed. I have used this package with large XSL files and has worked well.

How to call a preference value in XSLT

Hi ALL,
how to call a preference value(which is defined in bpel already) in XSLT??
Can any one help me plz
Regards,
Venkat Ch

Function to retrieve the preference :
http://www.xenta.nl/blog/2009/10/28/oracle-soa-suite-11g-setting-and-getting-preferences/
Create a new xsl mapping and let the 'first' parameter be some messageType variable (for example the inputVariable, or some other variable you use for your main input).
In the xslt add between the "<xsl:stylesheet>"-tag and the "<xsl:template match=".">"-tag something like "<xsl:param name="myPref" />"
Your xsl is ready to receive the extra input parameter.
Now in your bpel process do something like this
      <copy>
        <from expression="ora:doXSLTransformForDoc('xsl/myxslt.xsl', $inputVariable.input, 'myPref', ora:getPreference(myPref))"/>
        <to variable="myresult"/>
      </copy>
or first assign ora:getPreference(myPref) to myPrefVar (xsd:string) and then use
      <copy>
        <from expression="ora:doXSLTransformForDoc('xsl/myxslt.xsl', $inputVariable.input, 'myPref', $myPrefVar)"/>
        <to variable="myresult"/>
      </copy>

Transforming XML through XSLT

Hi Folks,
I just need to transform a basic xml using xslt. I have built and xsl file which works fine on the given xml input. I have test through AltovaXMLSpy tool.
Now I want to do the same through my java class with xml as input string and xsl file.
I have seen this example:
package com.ibn.util;
import java.io.*;
import java.net.MalformedURLException;
import java.net.URL;
import org.xml.sax.SAXException;
import org.apache.xalan.*;
* A simple demo of Xalan 1. This code was originally written using
* Xalan 1.2.2. It will not work with Xalan 2.
public class SimpleXalan1 {
     * Accept two command line arguments: the name of an XML file, and
     * the name of an XSLT stylesheet. The result of the transformation
     * is written to stdout.
    public static void main(String[] args)
            throws MalformedURLException, SAXException {
        if (args.length != 2) {
            System.err.println("Usage:");
            System.err.println(" java " + SimpleXalan1.class.getName( )
                    + " xmlFileName xsltFileName");
            System.exit(1);
        String xmlFileName = args[0];
        String xsltFileName = args[1];
        String xmlSystemId = new File(xmlFileName).toURL().toExternalForm( );
        String xsltSystemId = new File(xsltFileName).toURL().toExternalForm( );
        org.apache.xalan.xslt.XSLTProcessor processor = org.apache.xalan.xslt.XSLTProcessorFactory.getProcessor();
        org.apache.xalan.xslt.XSLTInputSource xmlInputSource =
                new org.apache.xalan.xslt.XSLTInputSource(xmlSystemId);
        org.apache.xalan.xslt.XSLTInputSource xsltInputSource =
                new org.apache.xalan.xslt.XSLTInputSource(xsltSystemId);
        org.apache.xalan.xslt.XSLTResultTarget resultTree =
                new org.apache.xalan.xslt.XSLTResultTarget(System.out);
        processor.process(xmlInputSource, xsltInputSource, resultTree);
}but on compilation it gives errors as org.apache.xalan.xslt is not in the class path. Could anybody suggest which jars i need to resolve this problem and where I can get that? or is there any other better solution provided by the core java api?
Thanks.

thanks dude.
Did it the following was as i wanted to read the transformation output as well.
public String doTransform(String xmlString){
    ByteArrayOutputStream result = new ByteArrayOutputStream();
    //Result output = new StreamResult(result);
    try{
      DocumentBuilder parser = DocumentBuilderFactory.newInstance().newDocumentBuilder();
      Document document = parser.parse(new InputSource(new StringReader(xmlString)));
      Transformer transformer = TransformerFactory.newInstance().newTransformer(new StreamSource(new FileInputStream("/IBNSubscriberServlet/src/com/ibn/util/g7.xsl")));
      Source source = new DOMSource(document);
      //output = new StreamResult(System.out);
      transformer.transform(source, new StreamResult(result));
      return result.toString();
    }catch (Exception e){
      System.out.println(e.getMessage());
    return result.toString();
}Edited by: buttsp on Sep 16, 2009 4:18 AM
Edited by: buttsp on Sep 16, 2009 4:18 AM

Transforming webtemplates via xslt?

Hello Experts,
a customer has a Backupsystem to save webtemplates out of BW7.
Those Webtemplates are saved as rawd ata (XML) and NOT as pdf-files.
Is there any chance to use the rawdata via XSLT or any other technology to convert them into HTML or PDF-format?
It would be very sad if i had to tell the customer that the raw data and his backupsystem is nearly useless

Here a file of the testsystem.
(xml.sap.com does not exist)
(repace ] and [ with < and >)
[bi:bisp xmlns:bi="http://xml.sap.com/2005/01/bi/wad/bisp" xmlns:jsp="http://java.sun.com/JSP/Page" xmlns="http://www.w3.org/TR/REC-html40" xmlns:h="http://www.w3.org/TR/REC-html40"]
[html]
    [head]
      [title]Netweaver BI Web Application[/title]
      [meta http-equiv="Content-Type" content="text/html; charset=utf-8"]
      [/meta]
    [/head]
    [body]
      [bi:item name="TEMPLATE_PARAMETERS" type="TEMPLATE_PARAMETERS" xmlns:B="http://xml.sap.com/2005/01/bi/wad/bisp"]
      [/bi:item]
      [bi:data_provider name="DP_1" type="QUERY_VIEW_DATA_PROVIDER" xmlns:B="http://xml.sap.com/2005/01/bi/wad/bisp"]
        [bi:param name="INITIAL_STATE" type="CHOICE" value="QUERY"]
          [bi:param name="QUERY" value="PM_ITELO_MARKET" text="Type"]
          [/bi:param]
        [/bi:param]
      [/bi:data_provider]
      [bi:item name="CHART_ITEM_1" type="CHART_ITEM" designheight="200" designwidth="600" xmlns:B="http://xml.sap.com/2005/01/bi/wad/bisp"]
        [bi:param name="DATA_PROVIDER_REF" value="DP_1"]
        [/bi:param]
        [bi:param name="AXES_SWAPPED" value="X"]
        [/bi:param]
        [bi:param name="LEGEND_TYPE" value="LEGEND_POSITION"]
          [bi:param name="LEGEND_POSITION" value="S"]
          [/bi:param]
        [/bi:param]
        [bi:param name="CHART_CUSTOMIZING"]
          [cc:SAPChartCustomizing xmlns="http://xml.sap.com/2005/01/graphics/chartengine/cu" version="1.1" xmlns:cc="http://xml.sap.com/2005/01/graphics/chartengine/cu"]
            [cc:GlobalSettings]
              [cc:Dimension]Two[/cc:Dimension]
              [cc:TransparentColor]RGB(255,0,255)[/cc:TransparentColor]
              [cc:CanvasColor]RGB(255,0,255)[/cc:CanvasColor]
              [cc:ColorPalette]Streamline[/cc:ColorPalette]
              [cc:ColorOrder]Default[/cc:ColorOrder]
              [cc:Gaps]Void[/cc:Gaps]
              [cc:EqualizeValueAxes]false[/cc:EqualizeValueAxes]
              [cc:Defaults]
                [cc:ChartType]Lines[/cc:ChartType]
                [cc:FontFamily]Microsoft Sans Serif[/cc:FontFamily]
              [/cc:Defaults]
              [cc:Colors]
                [cc:Color id="1"]RGB(213,200,255)[/cc:Color]
                [cc:Color id="2"]RGB(183,162,253)[/cc:Color]
                [cc:Color id="3"]RGB(164,136,255)[/cc:Color]
                [cc:Color id="4"]RGB(146,112,255)[/cc:Color]
                [cc:Color id="5"]RGB(125,85,255)[/cc:Color]
              [/cc:Colors]
            [/cc:GlobalSettings]
             [cc:Elements]
              [cc:ChartElements]
                [cc:Background]
                  [cc:Visibility]true[/cc:Visibility]
                  [cc:Extension /]
                  [cc:Insets]3[/cc:Insets]
                  [cc:Color]RGB(255,255,255)[/cc:Color]
                  [cc:SecondaryColor]RGB(0,0,0)[/cc:SecondaryColor]
                  [cc:Pattern]None[/cc:Pattern]
                  [cc:Gradient]None[/cc:Gradient]
                  [cc:Texture]None[/cc:Texture]
                  [cc:TextureMode]Tile[/cc:TextureMode]
                  [cc:Transparency]0[/cc:Transparency]
                  [cc:BorderColor]None[/cc:BorderColor]
                  [cc:BorderStyle]Solid[/cc:BorderStyle]
                  [cc:BorderWidth]1[/cc:BorderWidth]
                [/cc:Background]
                [cc:PlotArea]
                  [cc:Visibility]true[/cc:Visibility]
                  [cc:Extension /]
                  [cc:Color]RGB(240,245,240)[/cc:Color]
                  [cc:SecondaryColor]RGB(0,0,0)[/cc:SecondaryColor]
                  [cc:Pattern]None[/cc:Pattern]
                  [cc:Gradient]None[/cc:Gradient]
                  [cc:Texture]None[/cc:Texture]
                  [cc:TextureMode]Tile[/cc:TextureMode]
                  [cc:Transparency]0[/cc:Transparency]
                  [cc:BorderColor]RGB(0,0,0)[/cc:BorderColor]
                  [cc:BorderStyle]Solid[/cc:BorderStyle]
                  [cc:BorderWidth]1[/cc:BorderWidth]
                [/cc:PlotArea]
                [cc:Title]
                  [cc:Visibility]true[/cc:Visibility]
                  [cc:Extension /]
                  [cc:Caption]US Flatscreen Monitor Market[/cc:Caption]
                  [cc:Alignment]North[/cc:Alignment]
                  [cc:AlignToPlot]false[/cc:AlignToPlot]
                  [cc:Insets]4[/cc:Insets]
              [/cc:ChartElements]
              [cc:ChartTypes]
                [cc:Lines]
                  [cc:Visibility]true[/cc:Visibility]
                  [cc:Extension /]
                  [cc:CenteredPointCu]true[/cc:CenteredPointCu]
                [/cc:Lines]
              [/cc:ChartTypes]
            [/cc:Elements]
          [cc:Images /]
          [/cc:SAPChartCustomizing]
        [/bi:param]
        [bi:param name="TITLE" value="US Flatscreen Monitor Market"]
        [/bi:param]
        [bi:param name="CHART_TYPE" value="LINES"]
        [/bi:param]
        [bi:param name="LEGEND_ONLY" value=" "]
        [/bi:param]
        [bi:param name="WIDTH" value="600"]
        [/bi:param]
      [/bi:item]
      [bi:item type="ANALYSIS_ITEM" name="ANALYSIS_ITEM_1" designwidth="400" designheight="200" xmlns:B="http://xml.sap.com/2005/01/bi/wad/bisp"]
        [bi:param name="DATA_PROVIDER_REF" value="DP_1"]
        [/bi:param]
      [/bi:item]
      [!-- insert data providers, items and other template content here --]
    [/body]
[/html]
[/bi:bisp]
Edited by: Daniel Scherban on Jan 7, 2009 1:56 PM
Edited by: Daniel Scherban on Jan 7, 2009 1:57 PM

Bringing back transform value inputs in Adobe After Effects?

Last night I opened up After Effects CS4 to rotate and scale an image. But when I click on the layer and twirl down the Transform tab, the yellow numbers that often are on the right side of the values are missing! And I don't know how to get the back.
So if this has happened to anyone before could you please tell me how to get the yellow value input numbers to come back? I looked through preferences to see if there is a way to reset all of AE's settings but I can't find anything that looks helpful.
Please help!
PS. These inputs I think are also known as the X and Y value. I can still manipulate them if I, for example, right click on "rotation" and select 'edit value' but this is slow and time consuming and disallows me the ability to manipulate values on multiple layers. I need those yellow numbers back.

It's likely that you unknowingly hit the "F4" key, and swapped the "Switches" panel, for the "Modes" panel.
Try hitting F4 again to toggle back to the switches panel.
If that doesn't work, right-click on the panel title bar area:
And, in the Columns fly-out, make sure Switches is checked on:

LDAPMAP Function to Transform Value to UPPERCASE

Hello,
In t-code LDAPMAP, is there a function module (linking type), I may use to transform the value into UPPERCASE? I have tried function "SWA_STRING_TO_UPPERCASE", but I don't think it's returning a value, as running the sync program (RSLDAPSYNC_USER) returns "Warning: Data missing for field COMPANY of structure COMPANY", and is not updated.
For example:
Active Directory has an attribute for office, "physicalDeliveryOfficeName", with value "Tulsa, OK" for a user. I think this value comes into AD from HR, and it would be difficult to change the value to UPPER. In t-code SUCOMP, we have a company location with a key of "TULSA, OK" (This cannot be changed to lower -- SAP transforms it to UPPER when saving). It even appears as "TULSA, OK" in table USCOMPANY.
However, as mentioned above, this isn't working.
What function module, if any, may I use to transform the AD attribute "physicalDeliveryOfficeName" in LDAPMAP to UPPERCASE?
Also, if you have any other function modules to share besides those already mentioned below (such as MAP_DEFAULT,
MAP_CONCAT_CHAR, MAP_SPLIT_CHAR, or MAP_UNION) which can be used in LDAPMAP, I'd be grateful!
http://help.sap.com/saphelp_470/helpdata/en/8d/49e13b6e429a72e10000000a114084/content.htm
Thanks!
Shawn

Hi,
Create your own module.
Copy MAP_DEFAULT to create UPPER CASE action on both Inbound and OutBound transformation.
Taryck.

Transform value into variable

Hi all. I need to clear a field in a structure, but the problem is that this field is known only during runtime and is contained as a value of another field (lv_need_clear). How can the value be into transformed into variable?
CONCATENATE 'ls_bapi_' <ls_matdata>-tabname 'x' '-'
<ls_dd03p>-deffdname INTO lv_need_clear.
CLEAR "...???

u can assign structure too.
FIELD-SYMBOLS <fs_struc> TYPE ANY.
ASSIGN (structure_name) TO <fs_struc>.
check sy-subrc EQ 0.
then.
ASSIGN COMPONENT (field_name) OF structure <fs_struct> TO <fs>.

Transforming values in XSLT

Similar Messages

Maybe you are looking for