Xslt transformation - single tag to unbounded element in target schema

I am trying xslt in JDev11g. My source has tags like soldTo, shipTo and BillTo customer details. I need to map these in the target schema <PARTIES> unbounded element in the 2nd, 4th and 5th iteration. I am unable to map multiple times into the target. Can this be done? Target example is below:
<PARTNERS/>
<PARTNERS>
<PARTYTYPE>ShipTo</PARTYTYPE>
<PARTNRNDX>BMW1702</PARTNRNDX>
</PARTNERS>
<PARTNERS/>
<PARTNERS>
<PARTYTYPE>SoldTo</PARTYTYPE>
<PARTNRNDX>BMW2521</PARTNRNDX>
</PARTNERS> ....
Thanks
Shanthi

Hello Folks,
I have a similar issue. I have a particular unbounded element which i have to display multiple times ( mapping it to different source tags from the source schema) . I am able to do it in the source view and my transformation works fine when i test it. I am able to get the XML what i need. How ever when i switch to the design view, i get this error
Transformation_1.xsl
Error: This node is already mapped, repeating nodes not supported : "/mstns:OrderCreate/mstns:OrderCreateProperties/mstns:PartnerInformation/@partnerRoleIndicator"
Error: This node is already mapped, repeating nodes not supported : "/mstns:OrderCreate/mstns:OrderCreateProperties/mstns:PartnerInformation/mstns:PartnerIdentifier/@partnerIdentifierIndicator"
Is it ok to proceed and deploy with the current code? Or should i modify my source schema (which is in my control) to fetch multiple rows, use a for-each to achieve this functionality?
Thanks

Similar Messages

Xslt transformation - series of tags to unbounded element in target schema

I am fairly new to xslt. I am trying to do this xsl transformation in JDev in my BPEL process. Any pointers to similar samples would help as well. Can you please help me achieve the below:
I have a source xml as below:
<calloffs>
<calloff_dt1>100520</calloff_dt1>
<calloff_qty1>20</calloff_qty1>
<calloff_dt2>100625</calloff_dt2>
<calloff_qty2>10</calloff_qty2>
<calloff_dt3>100710</calloff_dt3>
<calloff_qty3>1</calloff_qty3>
</calloffs>
I need to create a target xml as below:
<schedulelist>
<schedule>
<schqty>20 </schqty>
<schdate>100520 </schdate>
</schedule>
<schedule>
<schqty>10 </schqty>
<schdate>100625 </schdate>
</schedule>
<schedule>
<schqty>1 </schqty>
<schdate>100710 </schdate>
</schedule>
</schedulelist>

Hello Folks,
I have a similar issue. I have a particular unbounded element which i have to display multiple times ( mapping it to different source tags from the source schema) . I am able to do it in the source view and my transformation works fine when i test it. I am able to get the XML what i need. How ever when i switch to the design view, i get this error
Transformation_1.xsl
Error: This node is already mapped, repeating nodes not supported : "/mstns:OrderCreate/mstns:OrderCreateProperties/mstns:PartnerInformation/@partnerRoleIndicator"
Error: This node is already mapped, repeating nodes not supported : "/mstns:OrderCreate/mstns:OrderCreateProperties/mstns:PartnerInformation/mstns:PartnerIdentifier/@partnerIdentifierIndicator"
Is it ok to proceed and deploy with the current code? Or should i modify my source schema (which is in my control) to fetch multiple rows, use a for-each to achieve this functionality?
Thanks

XSLT transformation help

Hi ,
Source data :-
<root xmlns="http://TargetNamespace.com/">
<header>
        <C2> </C2>
         <C3></C3>
        <C4></C4>
        <C5></C5>
</header>
<body>
    <a></a>
    <b></b>
</body>
<body>
    <a></a>
    <b></b>
</body>
<body>
    <a></a>
    <b></b>
</body>
<header>
        <C2> </C2>
         <C3></C3>
        <C4></C4>
        <C5></C5>
</header>
<body>
    <a></a>
    <b></b>
</body>
<body>
    <a></a>
    <b></b>
</body>
the above input needs to be transformed to
<Root>
     <child>
            <header> ..... </header>
             <body>   .. </body>
             <body>   .. </body>
             <body>   .. </body>
     </child>
     <child>
         <header>.......</header>
          <body>........</body>
           <body>........</body>
      </child>
</Root>
(... ) here are the actual elements I jus represented them as ( .... )
can some one tell me how can we write xslt for the above transformation ..

You need to create a target schema with below heirarchy.
Root
     Child(unbounded)
            body.(unbounded)
In .xsl file from source to target,
use mapping this way:
<Root>
for each on <Child>
for each on < body>
thanks

XSLT Transformation error: Non-canonical structure of element name

Good day experts,
I have recently started using xslt, and came upon the following demo in the sdn.
http://wiki.sdn.sap.com/wiki/display/ABAP/XMLXSLTwith+ABAP
I have retrieved the example xml files from airplus.com, as per the instructions, and implemented the code.
When I test the xslt transformation in se80, it transforms correctly.
However, when I run the program, I get the following error.
CX_XSLT_FORMAT_ERROR
Transformation error: Non-canonical structure of element name XML_OUTPUT
Is there an error in the example that I am not aware of?
Thanks in advance,
Johan Kriek

Found the solution.
You rename the tag <XML_OUTPUT> to anything else like <TEST>. And Hurray!!! it works.
It looks like SAP is using this name internally somewhere so we are getting error when we are using same name.
Anyways the problem is solved.
Regards,
Jai

How to unmarshall list tags/unbounded elements using jax-ws auto generated classes in weblogic 12c

hi
i have a need wherein i need to create/host jax-ws webservice ( starting from wsdl) and in that service translate the xml using xsl to a different structure and call another webservice hosted to another server ( non-weblogic).
so my approach is as soon as request comes to the service impl, i marshal the object to a xml then apply the required xsl transformation and then unmarshal the transformed xml to the object which can be used to trigger another webservice.
This approach works fine for the xmls without list tags/unbounded elements , however it gives marshal exception whenever the xmls has list/unbounded elements.
i am using jaxb and jax-ws generated class for marshalling and unmarshalling.
so need some help on how to deal in this scenario?
any help is appreciated

hi
i have a need wherein i need to create/host jax-ws webservice ( starting from wsdl) and in that service translate the xml using xsl to a different structure and call another webservice hosted to another server ( non-weblogic).
so my approach is as soon as request comes to the service impl, i marshal the object to a xml then apply the required xsl transformation and then unmarshal the transformed xml to the object which can be used to trigger another webservice.
This approach works fine for the xmls without list tags/unbounded elements , however it gives marshal exception whenever the xmls has list/unbounded elements.
i am using jaxb and jax-ws generated class for marshalling and unmarshalling.
so need some help on how to deal in this scenario?
any help is appreciated

XSLT mapping - Mapping of unbounded elements using Altova Mapforce

Hi,
Please give guidance on doing XSLT mapping for unbounded elements in Altova Mapforce. I am not seeing any functions (like FOR loop etc.,) in the XSLT mapping screen for the same.
I appreciate your input.
Regards
Ramesh

HI,
For XSLT Mapping refer this help to get functions,syntax etc-
http://www.w3schools.com/xsl/default.asp
Regards,
Moorthy

Oracle XSLT Transformation not preserving space in text element

If we have a BPEL process which is calling a XSLT transformation contains the code similar as below:
for Populating an element with white space only
<tns:TargetField>
<xsl:text disable-output-escaping="yes"> </xsl:text> 
</tns: TargetField>
Our expected result / output would be:
<tns:TargetField> </tns: TargetField> 
But, we get:
<tns:TargetField/>
Oracle XSLT is ignoring the white space even if we try with preserve space in XSD, or in XSLT this is not producing the expected output.
This looks a BUG with Oracle XSLT Transformation .
For a workaround solution we can use below XSLT snippet:
*<tns:TargetField>*
*<xsl:value-of select="string(' ')"/> *
*</tns:TargetField>*
This is returning Output:
*<tns:TargetField> </tns:TargetField> *
Any other work around do you find?
Edited by: panks on Jul 29, 2011 12:37 PM

The workaround only works with one white space, if one put more white spaces, it do not work.
<tns:TargetField>
<xsl:value-of select="string(' ')"/> 
</tns:TargetField>
This is returning Output:
<tns:TargetField> </tns:TargetField> 
Edited by: user10697506 on Aug 10, 2011 3:27 PM

Genereting JSTL tags with an XSLT transformation question

Hi there!
I have some XML datas to display in a jsp file.
XML content is of this type:
<message>
<title>A message</title>
</message>
The most elegent way to present them is to transform XML via xslt into xhtml.
(that way I can externally change with ease the message formatting output without changing the jsp)
For that, I use the cool tag
<x:transform>
on each xml file i want to display (with x:foreEach)
The output produced for each xml file is:
<div class="message">
<h2>A message</h2>
</div>
My problem is now that I want to include custom tags in the generated content!
For exemple:
<div class="message">
<h2>A message<c:out ...></h2>
</div>
My question is:
how can I make that xslt generated tag to be executed???
Since it is the product of an xslt transformation ,I suppose it won't be executed at all...
Advices greatly appreciated! :)

I'm not sure I understand what you mean when you say "how can I make that xslt generated tag to be executed???"
You've got your XML input and the XSL-T stylesheet that will transform the XML input into an XHTML stream containing JSTL tags.
I'm assuming that you're going to ask a servlet to pass the XML input to the XSL transformer and get the XHTML output stream. Once you have that, the servlet will write the XHTML to the HTTP response output stream, where it'll be rendered by the browser.
I think the key is to make sure that you tell the browser that response type is a JSP (that's the only document type in which it makes sense to put JSTL tags). When the browser gets that JSP, it'll treat it like any other: generate .java code, compile that to a .class file, and then render.
I'm not sure about efficiency, but it sure is an elegant solution. - MOD

XSLT transformation for Single XML Output

I want to save a book to a single XML document. Is it correct that I can do this by adding an xslt to merge the standard framemaker entity type output ? Can I easily reconfigure the standard Save As XML to acheive this? or do I need to add a new menu item and call the XSLT dialogue...
any advice appreciated.
Thanks!

Tracey,
   A related discussion appeared in the FrameSGML Yahoo group recently. Much of what follows is what I wrote there.
   Your XML application (defined in structapps.fm or another application definition file) can specify an XSLT post-process. No need to change Save as XML or define a new menu item. Depending on what you want, the XSLT transform can be as simple as the following:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:transform version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xsl:output method="xml"/>
    <xsl:template match="/ | node() | @*">
        <xsl:copy>
            <xsl:apply-templates select="@* | node()"/>
        </xsl:copy>
    </xsl:template>
</xsl:transform>
This is an identity transform that simply copies the interpreted input to the output. I've used the word "interpreted" here because XSLT does not distinguish among some variations of how content is entered. In particular, it does not distinguish between content in referenced general entities (which is what you want) or between attribute values that happen to be the same as the attribute default value and attributes that are not explicitly specified and hence use the default value.
There are a few things to watch out for involving use of general entities.
First, if you are using entity attributes for graphics, you'll need to modify the above slightly. It's probably easier to replace the entity attributes with file attributes, but if you want to keep the entities, the above needs to be extended to declare the entities.
Second, if you are using and want to preserve entity references for special characters or variables, you'll need to account for them as well. See $FMHOME\Structure\xml\PreserveEntity\readme.pdf.
    --Lynne

Tags not printed when outputting XML after XSLT transformation

Hi!
I want my to perform an XSLT transformation on requests to my web service.
This is the style of a typical request:
<app:aRequest xmlns:app="http://myNamespace">
<app:firstTag>value1</app:firstTag>
<app:secondTag>value2</app:secondTag>
<app:thirdTag>value3</app:thirdTag>
</app:aRequest>I want to transform it into something like this:
<app:aRequest xmlns:app="http://myNamespace">
<app:firstTag>A hard coded, completely different value!</app:firstTag>
<app:secondTag>value2</app:secondTag>
<app:thirdTag>value3</app:thirdTag>
</app:aRequest>To do that, I use the following XSLT:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsl:stylesheet version="1.0"
                xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                xmlns:app="http://myNamespace">
<xsl:template match="/">
<app:aRequest>
<app:firstTag>A hard coded, completely different value!</app:firstTag>
<app:secondTag><xsl:value-of select="app:aRequest/app:secondTag" /></app:secondTag>
<app:thirdTag><xsl:value-of select="app:aRequest/app:thirdTag" /></app:thirdTag>
</app:aRequest>
</xsl:template>
</xsl:stylesheet>And I use the following code to execute the transformation:
public Object unmarshal(Source source) throws XmlMappingException, IOException {
TransformerFactory factory = TransformerFactory.newInstance();
    // Does this factory support SAX features?
    if(factory.getFeature(SAXSource.FEATURE)) {
      SAXTransformerFactory saxTransformerFactory = (SAXTransformerFactory)factory;
    // Read xslt file.
    InputStream inputStream = getClass().getResourceAsStream("/META-INF/xsltTransformation.xsl");
    if(inputStream == null) {
      throw new RuntimeException("No XSLT transformation file present at " + location);
    Templates xsltOutputTemplate = saxTransformerFactory.newTemplates(new StreamSource(inputStream));
    Transformer transformer = xsltTemplate.newTransformer();
    // Perform transformation.
    StringWriter stringWriter = new StringWriter();
    StreamResult result = new StreamResult(stringWriter);
    transformer.transform(source, result);
    // Print result.
    String xmlString = stringWriter.toString();
    System.out.println(xmlString);
    // Proceed with unmarshalling.
    StringReader stringReader = new StringReader(xmlString);
    StreamSource transformedSource = new StreamSource(stringReader);
    return oxMapper.getUnmarshaller().unmarshal(transformedSource);
}However, the System.out.println(xmlString); produces the following result:
<?xml version="1.0" encoding="UTF-8"?>
value1
value2
value3The tags are not printed and the hard coded value is not present.
What am I doing wrong? Please help!

Following up on what the good Dr said,
Are you sure that you are using the stylesheet that you think you are?
I tried your stylesheet and input and got more or less what you wanted and not what you actually got.
Note that I did not use your code.

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

Start to learn XSLT transformation

Hi,
i started to learn XSLT transformation, but i get the first problems very soon.
Here is my coding :
<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>
        <EXPORT>
          <xsl:for-each select="BUT000">
            <BUT000>
              <PARTNER>
                <xsl:value-of select="PARTNER"/>
              </PARTNER>
            </BUT000>
          </xsl:for-each>
        </EXPORT>
      </asx:values>
    </asx:abap>
</xsl:template>
</xsl:transform>
My problem is, that the transformation exit on the tag "for-each" and do nothing.
My source is a internal table from type BUT000.
In the internal table are two entries.
Where is my fault?
Regards,
Anton

Check those tutorials:
XSLT Tutorial - http://www.w3schools.com/xsl/
XPath Tutorial - http://www.w3schools.com/xpath/
XQuery Tutorial - http://www.w3schools.com/xquery/default.asp
Regards.
Liang

Regarding XSLT transformation

Hi Experts,
Can you please help me out in this XSLT transformation
I had a souce xsd which contain the following elements
1)year-integer
2)mmc-string
3)RPO list(complex type)
4)isfleet
My target xsd in XSLT transformation contain a single element arg0 which is of type list. Below is the xsd structure of my target .
<xs:element name="getPvcList">
<xs:complexType>
<xs:sequence>
<xs:element name="arg0" type="java:List" xmlns:java="java:java.util"/>
</xs:sequence>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="java:java.util" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
<xs:complexType name="List">
<xs:complexContent>
<xs:restriction base="soapenc:Array" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"/>
</xs:complexContent>
</xs:complexType>
</xs:schema>
</xs:complexType>
I need to map all the elements in the source to the the target element argo.
Thanks,
Bharath

Hi
Check for correct spelling:
localejbs/AF_modules/MessageTransformBean
Check the parameters for trailing spaces:
'com.sap.aii.messaging.adapter.XSLTConversion_'
Check the path:
Windows: C:\...
Unix: /usr/...
and
Check the adit log of the message monitoring in the RWB for entries according to the module....
Trc or trace files on visual administrator is the closest answer from my part.
please refer,
/people/michal.krawczyk2/blog/2005/09/07/xi-why-dont-start-searching-for-all-errors-from-one-place
regards,
vasanth

Automatic insert of xmlns:xsl during XSLT transformation

I am using the xmlparserv2.jar of dated "12/10/00" to perform a XSLT transformation. I need to insert a xml:space="preserve" attribute to a generated tag. However, there is an addition attribute added : xmlns:xml="http://www.w3/org/XML/1998/namespace". How can I suppress the generation of this attribute ?
Here is my XML :
<?xml version = '1.0' standalone = 'no'?>
<COLDdoc>
<Page template="bkgnd1" num="1">
<Line num="1"> CN011A021C 1A021</Line>
<Line num="2"> 1954.90 7713.36</Line>
</Page>
</COLDdoc>
My XSL is :
<?xml version = '1.0' standalone = 'yes'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:output method="xml" indent="no" doctype-system="svg-20000303-stylable.dtd"/>
<xsl:template match="Line">
<text>
<xsl:attribute name="x">0</xsl:attribute>
<xsl:attribute name="y">
<xsl:value-of select="@num*10"/>
</xsl:attribute>
<xsl:attribute name="xml:space">preserve</xsl:attribute>
<xsl:value-of select="."/>
</text>
</xsl:template>
</xsl:stylesheet>
The result XSLT Transformation :
<?xml version = '1.0' encoding = 'UTF-8'?>
<!DOCTYPE text SYSTEM "svg-20000303-stylable.dtd">
<text x="0" y="10" xmlns:xml="http://www.w3/org/XML/1998/namespace" xml:space="preserve"> CN011A021C 1A021</text>
<text x="0" y="20" xmlns:xml="http://www.w3/org/XML/1998/namespace" xml:space="preserve"> "> 1954.90 7713.36</text>
Regards.
Jeffrey
null

Hi Greg,
please try it with the following (just slightly) modified transformation (works fine for me):
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
               xmlns:asx="http://www.sap.com/abapxml"
               xmlns:sap="http://www.sap.com/sapxsl"
               version="1.0">
<xsl:strip-space elements="*"/>
<xsl:template match="/PEXR2002/IDOC">
    <asx:abap version="1.0">
      <asx:values>
        <HEADER_DATA>
          <SNDPRN>
            <xsl:value-of select="EDI_DC40/SNDPRN"/>
          </SNDPRN>
          <BGMREF>
            <xsl:value-of select="E1IDKU1/BGMREF"/>
          </BGMREF>
          <MOABETR>
            <xsl:value-of select="E1IDKU5/MOABETR"/>
          </MOABETR>
          <CREDAT>
            <xsl:value-of select="EDI_DC40/CREDAT"/>
          </CREDAT>
          <DATUM>
            <xsl:value-of select="E1EDK03/DATUM"/>
          </DATUM>
        </HEADER_DATA>
      </asx:values>
    </asx:abap>
</xsl:template>
</xsl:transform>
I recommend to test all transformations that you define on a sample source and check the output. If you apply your original transformation you would see that it basically doesn't select anything and therefore you just get an XML document with the field names but no values.
Cheers, harald

Xslt transformation - single tag to unbounded element in target schema

Similar Messages

Maybe you are looking for