Encoding Technique converting in XSLT Mapping.

Hi,
I have a scenarion File->XI->File. the incoming file has the encoding technique UTF-8. i have to convert it to ISO-8859-1. i'm using an XSLT mapping to do that after which my java mapping gets executed. when i tested this mapping with the source file in the Design, it works fine, but when i execute the whole scenario end to end,it is throwing some exception with Unsupported Charecter. the code of the XSLT looks as given under:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format">
 <xsl:output encoding="ISO-8859-1"/>
 <xsl:template match="/">
 <xsl:copy-of select="*"/>
 </xsl:template>
</xsl:stylesheet>
Can any one tell me how to resolve this.
Any help wud b gr8ly appreciated.
Thnx in Advance
Anil

HI Anil,
Check these links, it might help you.
Ampersand ('&') dumps XI Mapping. JDBC to BIW
/people/pooja.pandey/blog/2005/06/27/xslt-mapping-with-java-enhancement-for-beginners
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
/people/prasadbabu.nemalikanti3/blog/2006/03/30/xpath-functions-in-xslt-mapping
Best regards
Mahesh.M

Similar Messages

XSLT Mapping to convert u201C.CSVu201D file into XML Structure.

Hi All,
I wanted to know can we use XSLT Mapping to convert u201C.CSVu201D file into XML Structure.
I am communicating between two XI Systems. First XI system is going to give u201C.CSVu201D file as main document. I need to post IDOC Corresponding to this. So what I want to do is read this u201C.CSVu201D file (Main document in payload) and first convet it into XML and then use second mapping which will convert XML to IDOC.
I know this is possible with JAVA Mapping but just wanted to confirm can we do this with XSLT mapping as well?
Regards,
Gouri

Hi Amit,
I know this way it shd work as i am able see other XSLT files. But this particular file is not visible.
I am copying following code only in sample.xslt file.
<xsl:stylesheet
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:fn="fn"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
version="2.0" exclude-result-prefixes="xs fn">
<xsl:output indent="yes" encoding="US-ASCII" />
<xsl:param name="pathToCSV" select="'file:///c:/csv.csv'" />
<xsl:function name="fn:getTokens" as="xs:string+">
 <xsl:param name="str" as="xs:string" />
 <xsl:analyze-string select="concat($str, ',')" regex='(("["]*")+|[,]*),'>
 <xsl:matching-substring>
 <xsl:sequence select='replace(regex-group(1), "^""|""$|("")""", "$1")' />
 </xsl:matching-substring>
 </xsl:analyze-string>
</xsl:function>
<xsl:template match="/" name="main">
 <xsl:choose>
 <xsl:when test="unparsed-text-available($pathToCSV)">
 <xsl:variable name="csv" select="unparsed-text($pathToCSV)" />
 <xsl:variable name="lines" select="tokenize($csv, ' ')" as="xs:string+" />
 <xsl:variable name="elemNames" select="fn:getTokens($lines[1])" as="xs:string+" />
 <root>
 <xsl:for-each select="$lines[position() > 1]">
 <row>
 <xsl:variable name="lineItems" select="fn:getTokens(.)" as="xs:string+" />
 <xsl:for-each select="$elemNames">
 <xsl:variable name="pos" select="position()" />
 <elem name="{.}">
 <xsl:value-of select="$lineItems[$pos]" />
 </elem>
 </xsl:for-each>
 </row>
 </xsl:for-each>
 </root>
 </xsl:when>
 <xsl:otherwise>
 <xsl:text>Cannot locate : </xsl:text><xsl:value-of select="$pathToCSV" />
 </xsl:otherwise>
 </xsl:choose>
</xsl:template>
</xsl:stylesheet>
Is this correct?
-Gouri

XSLT mapping encoding for Korean language

Hi all,
I am using a XSLT mapping to ocnvert input XMl into flat file.Evrything seems to be working fine expect when Korean, Chinese, Vientam, etc characters are coming in the input file.
I think the above mentioned characters are occupying 2 bytes in the flat file due to which the position of the next field got misplaced in the flat file.
I tried with different unciode options in the following XSLT mapping.
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns0="urn:hsbc:a2r:corp:global:fi:paymentservice">
 <xsl:output method="text" omit-xml-declaration="yes" encoding="UTF-8"/>
 <xsl:template match="/">
 <ns0:PS>
 <Details>
 <xsl:for-each select="ns0:PaymentService/Details">
 <FileData>
 <xsl:value-of select="FileData"/>
 </FileData>
 </xsl:for-each>
 </Details>
 </ns0:PS>
 </xsl:template>
</xsl:stylesheet>
Not sure which encoding should be used here...

> Not sure which encoding should be used here...
Ask your customer or project lead.

How we can view convert data after XSLT mapping & before Graphical mapp

Hello Friends,
Currently i am working on XI standard content. In this client need some customization.
In interface mapping, XSLT mapping on 1st position & Graphical mapping on 2nd position.
As per my understanding 1st XSLT mapping will be exected then Graphical mapping.
Can I see or check convert data from XSLT mapping.
I want to check data between XSLT mapping & Graphical mapping.
Kindly help me out.
Regards,
Narendra

>
Narendra GSTIT wrote:
> I dont want to test standalone XSL Code.
>
> The data which I get from Source interface and after XSLT mapping I want to check this that my XSLT code is going well or not.
>
> i.e. check for proper input & get proper output.
You have ro do standalone testing of the XSLT mapping.....Interface Mapping or Interface Determination will give you output message which will be that of message mapping (the last mapping)
What is the issue in testing the XSLT mapping alone?...may be in Stylus Studio.
Just ensure that XSLT mapping produces proper output and then this output message of XSLT is the input to your Message Mapping.....once the entire Interface mapping gets executed then it would mean that all the included mapping programs work fine.
Regards,
Abhishek.

Convert XML using XSLT mapping

Hi,
I have an XML in the following format and would want to cnvert it in the target format shown below. Kindly let me know the XSLT mapping to conert from hierarchy to flat structure.
Source XML:
<group Level1="Mac Tools Item Classifications">
 <group Level2="6-Other Merchandise">
 <group Level3="61-Racing">
 <group Level4="011-Collectibles">
 <group Level5="001-NASCAR"/>
 <group Level5="002-NHRA"/>
 <group Level5="003-Other"/>
 </group>
 <group Level4="012-Apparel">
 <group Level5="001-Jackets"/>
 <group Level5="002-Shirts"/>
 <group Level5="003-Other">
 <group PartNumber="SHOE823-060"/>
 <group PartNumber="SHOE823-070"/>
 <group PartNumber="SHOE823-080"/>
 <group PartNumber="SHOE823-085"/>
 <group PartNumber="SHOE823-090"/>
 </group>
 </group>
 </group>
 </group>
</group>
Target XML:
<Group>
 <part>
 <Level1/>
 <Level2/>
 <Level3/>
 <Level4/>
 <PartNumber/>
 </part>
 <part>
 <Level1/>
 <Level2/>
 <Level3/>
 <Level4/>
 <PartNumber/>
 </part>
</Group>
I am not clear how to capture level1, level 2, etc. till the end node.
Regards,
Swaroopa

HI,
This is a sample

<xsl:variable name="var0_floatToString" select="user0:floatToString(/body/getQuote/inputGetQuote/@customerIDFloatAttr)"/>
 <xsl:if test="@customerIDFloatAttr">
 <xsl:attribute name="customerIDFloatAttr">
 <xsl:value-of select="@customerIDFloatAttr"/>
 </xsl:attribute>
 </xsl:if>
 <xsl:attribute name="customerIDAttr">
 <xsl:value-of select="$var0_floatToString"/>
 </xsl:attribute>
using <xsl:attribute name here name ="leval1" like that u can use in XSLT Mapping .
 Hope it helps
Regards.,
V.Rangrajan

How to use standard java functions in a XSLT mapping

Hi All,
I wish to use a standard java function in a XSLT mapping, The issue is either i am giving incorrect namespace which is used to invoke the function or the signature of the function call is incorrect, I have read all the links in http://help.sap.com, and i know one can enhance a XSLT mapping by writing one's own java code and thereby using java standard functions , but the requirement is such that i need to try and use java standard function in XSLT mapping itself.
Please refer to the sample code below:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0"
 xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
 xmlns:javamap="java:java.lang.String">
<xsl:output method="text"/>
<xsl:template match="/">
<xsl:variable name="input" select="Title">
<xsl:if test="function-available('javamap:toUpperCase')">
<xsl:value-of select="javamap:toUpperCase($input)"/>
</xsl:if>
Author:<xsl:value-of select="Author"/>
</xsl:template>
</xsl:stylesheet>
error encountered is: Illegal number or type of arguments.
please reply if you have tried a similar scenario in SAP XI.
Thanks & Regards,
Varun

Hi Varun,
 First of all i want to tell you that as per the documentation you can only call the static function inside xslt mapping. Your toUpperCase method is a non static function.
What i am getting is that you have an element called Author and you want to convert its value into uppercase.
you can write your own user defined function which is static.
Signature of your java method :
public static string toUpperCase(String Author,Map inputparam)
try this xslt map.
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="2.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:javamap="java:JavaProgram">
 <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
 <xsl:param name="Author">
 <xsl:value-of select="//Author_name"/>
 </xsl:param>
 <xsl:param name="inputparam" />
 <xsl:template match="/">
 <Author>
 <xsl:if test="function-available('javamap:toUpperCase')">
 <xsl:value-of select="javamap:toUpperCase($Author,$inputparam)"/>
 </xsl:if>
 </Author>
 </xsl:template>
</xsl:stylesheet>
Hope this will work.
Thanks and Regards
Vishal Kumar

XSLT mapping with Java helper classes

Hi,
I'm trying to implement a XSLT mapping to convert my request to a specific soap request message format for this I'm calling some methods from a java helper class. I have imported the jar file into the archives. When I tried to test the interface it keeps complaing there is some exception but doesn't give me the exact error. Has any one called any java helper classes with in XSLT mapping, if so I would appreciate if you could help me with this. Here is the code from xsl.
<wsse:Security soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="0" xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/07/secext" xmlns:UserToken="java:com.company.test.mapping.UserTokenMap">
<wsse:UsernameToken>
 <wsse:Username xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
 <xsl:value-of select="UserToken:getUsername()"/>
 </wsse:Username>
 <wsse:Password wsse:Type="wsse:PasswordDigest" xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
 <xsl:value-of select="UserToken:getPasswordDigest()"/>
 </wsse:Password>
 <wsse:Nonce xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
 <xsl:value-of select="UserToken:getNonce()"/>
 </wsse:Nonce>
 <wsu:Created xsi:type="soapenc:string" xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
 <xsl:value-of select="UserToken:getCreateDate()"/>
</wsu:Created>
</wsse:UsernameToken>
</wsse:Security>
Thanks,
Joe

Hi,
I'm getting following exception when I refer to the java class with in my XSLT mapping. Any one encountered the same problem.
com.sap.engine.services.ejb.exceptions.BaseRemoteException:
Exception in method transform.
 at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.transform(MapServiceRemoteObjectImpl0.java:218)
 at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0p4_Skel.dispatch(MapServiceRemoteObjectImpl0p4_Skel.java:104)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native
Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.UnsupportedClassVersionError:
com/earthlink/xi/mapping/UserTokenMap (Unsupported
major.minor version 49.0)
 at java.lang.ClassLoader.defineClass0(Native
Method)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:448)
 at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingLoader.findClass(RepMappingLoader.java:175)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
 at com.sap.engine.lib.xsl.xpath.JLBLibrary.<init>(JLBLibrary.java:33)
 at com.sap.engine.lib.xsl.xpath.LibraryManager.getFunction(LibraryManager.java:69)
 at com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:98)
 at com.sap.engine.lib.xsl.xpath.XPathProcessor.innerProcess(XPathProcessor.java:56)
 at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:43)
 at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:51)
 at com.sap.engine.lib.xsl.xslt.XSLValueOf.process(XSLValueOf.java:76)
 at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296)
 at com.sap.engine.lib.xsl.xslt.XSLElement.process(XSLElement.java:248)
 at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296)
 at com.sap.engine.lib.xsl.xslt.XSLElement.process(XSLElement.java:248)
 at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296)
 at com.sap.engine.lib.xsl.xslt.XSLElement.process(XSLElement.java:248)
 at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296)
 at com.sap.engine.lib.xsl.xslt.XSLElement.process(XSLElement.java:248)
 at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296)
 at com.sap.engine.lib.xsl.xslt.XSLElement.process(XSLElement.java:248)
 at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296)
 at com.sap.engine.lib.xsl.xslt.XSLTemplate.process(XSLTemplate.java:272)
 at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:463)
 at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:431)
 at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:394)
 at com.sap.engine.lib.jaxp.TransformerImpl.transformWithStylesheet(TransformerImpl.java:398)
 at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:240)
 at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingTransformer.transform(RepMappingTransformer.java:150)
 at com.sap.aii.ibrep.server.mapping.ibrun.RepXSLTMapping.execute(RepXSLTMapping.java:81)
 at com.sap.aii.ibrep.server.mapping.ibrun.RepSequenceMapping.execute(RepSequenceMapping.java:54)
 at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingHandler.run(RepMappingHandler.java:80)
 at com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:107)
 at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInterfaceMapping(ServerMapService.java:127)
 at com.sap.aii.ibrep.server.mapping.ServerMapService.transform(ServerMapService.java:104)
 at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.transform(MapServiceBean.java:40)
 at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.transform(MapServiceRemoteObjectImpl0.java:167)
 ... 10 more
; nested exception is:
 java.lang.UnsupportedClassVersionError:
com/earthlink/xi/mapping/UserTokenMap (Unsupported
major.minor version 49.0)

Graphical Mapping Vs XSLT mapping Vs Java Mapping Vs ABAP Mapping

Hi Experts,
I have a question regarding different message mapping options available in XI namely
Graphical Mapping
XSLT mapping
Java Mapping
ABAP Mapping
Q1: Which amoung the above mappings is the best and why?
Q2: On what cases Graphical, XSLT, Java and ABAP Mapping should be used?
Q3: Is it true that graphical and XSLT mappings are converted into Java class internally?
Kindly help!
Thanks
Gopal
Message was edited by:
gopalkrishna baliga

Hi,
There is no hard and fast rule for using the mapping techniques.
Graphical Mapping is used for simple mapping cases. When, the logic for your mapping is simple and straight forward and it does not involve mult hiearchical mapping requirement. and context handling.
Java and XSLT mapping are used when graphical mapping cannot help you.
When the choice is between Java And XSLT, XSLT is simpler than java mapping and easier. But, it has its drawbacks. XSLT can lead to a bad perfrormance if the Source XML is huge.
Java Mapping uses 2 types of parsers. DOM and SAX. DOM is easier to use with lots of classes to help you create nodes and elements, but , DOM is very processor intensive.
SAX parser is something that parses your XML one after the other, and so is not processor intensive. But, it is not exaclty easy to develop either.
For further info on each of the mapping, refer to these links,
Graphical Mapping,
http://help.sap.com/saphelp_nw04/helpdata/en/6d/aadd3e6ecb1f39e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/c4cdfc334824478090739c04c4a249/content.htm
XSLT Mapping
http://help.sap.com/saphelp_nw04/helpdata/en/73/f61eea1741453eb8f794e150067930/content.htm
http://www.w3.org/TR/xslt20/
Java Mapping
http://help.sap.com/saphelp_nw04/helpdata/en/e2/e13fcd80fe47768df001a558ed10b6/content.htm
DOM parser API
http://java.sun.com/j2se/1.4.2/docs/api/org/w3c/dom/package-frame.html
Also, check this thread for more info,
Different types of Mapping in XI
Am not sure about XSLT , but , yes graphical mapping is converted into java classes internally and these classes use SAX parsing as well.
Regards,
Bhavesh

XSLT Mapping for Namespace Prefix replacement

Hey All,
I have below XML:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:OrderChange ns0:transactionPurposeIndicator="Change" xmlns:ns0="http://www.api.org/pidXML">
<ns0:OrderChangeProperties>
<ns0:OrderChangeNumber>1</ns0:OrderChangeNumber>
<ns0:OrderChangeDate>2009-10-19</ns0:OrderChangeDate>
</ns0:OrderChangeProperties>
</ns0:OrderChange>
And i need to convert it to below format:
<?xml version="1.0" encoding="UTF-8"?>
<pidx:OrderChange pidx:transactionPurposeIndicator="Change" xmlns:pidx="http://www.api.org/pidXML" xmlns="http://www.api.org/pidXML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.api.org/pidXML Z:\integration\trunk\schemas\pidx\OrderChange_1-2.xsd">
<pidx:OrderChangeProperties>
<pidx:OrderChangeNumber>1</pidx:OrderChangeNumber>
<pidx:OrderChangeDate>2009-10-19</pidx:OrderChangeDate>
</pidx:OrderChangeProperties>
</pidx:OrderChange>
Can someone please let me know the XSLT Mapping to achieve this. I have tried searching on the forum but haven't found much help.
Appreciate your help.
Thanks

Hi Saif,
The below blog and doc will be useful
Useful XSLT mapping functions in SAP XI/PI
Changing Namespaces and the encoding format of XML - Process Integration - SCN Wiki
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/000ee4d0-be91-2d10-8aaf-ff8045bdd37d?overridelayout=t…
regards,
Harish

Removing specific XML tag in XSLT mapping

Hi there,
I've asked before about a XML to string XSLT mapping and the answers provided here helped me to successfully do that mapping! Thanks a lot!
I'm using the following mapping to convert a string back to XML.
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:m="http://my.namespace.com">
 <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="no"/>
 <xsl:template match="/">
 <xsl:for-each select="//m:my_tag">
 <xsl:value-of select="." disable-output-escaping="yes"/>
 </xsl:for-each>
 </xsl:template>
</xsl:stylesheet>
But now, I'm having a problem converting back from string to XML. The response tag "m:mytag" has a string like this:
"<?xml version="1.0" encoding="UTF-8"?><tag1><tag2>Data</tag2></tag1>".
And when I use the XSLT mapping shown above, the output file comes like this:
<?xml version="1.0" encoding="UTF-8"?>
<?xml version="1.0" encoding="UTF-8"?>
<tag1>
<tag2>Data</tag2>
</tag1>
As you can see, the initial <?xml ...> tag is duplicated, and it generates a parsing error in XI.
How can I eliminate one of the "<?xml version="1.0" encoding="UTF-8"?>" strings in the mapping?
Thanks a lot.

Wow!!!
The output="html" actually worked on XML Spy!
Removing the XSLT file initial tag didn't work.
I had already resolved this problem using the replace-string method that I found here: http://aspn.activestate.com/ASPN/Cookbook/XSLT/Recipe/65426
But your method is way more elegant and efficient. :o)
I'll test the html method on XI, but I'm almost sure it'll work too.

XSLT mapping not working b'coz " " & " " replaced with and

Hello Experts,
I have a RFC to JMS scenario. One of the parameter of RFC is a string field. This field will contain the XML data in it.
I need to create a complete XML payload using this data in a string field. For this I am using XSLT map :
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.1" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" >
 <xsl:output method="xml" omit-xml-declaration="no"/>
 <xsl:template match="/">
 <xsl:for-each select="//Nem">
 <xsl:copy-of select="."/>
 </xsl:for-each>
 </xsl:template>
</xsl:stylesheet>
This XSLT mapping works fine when tested independently.
But in actual scenario at runtime the "<" & ">" used to indicate a node are getting replaced with < and >. Then the XSLT mapping fails and produces no output.
The output of XSL will be passed in to a java mapping which signs the payload digitally.
What is the issue with these signs? How can I overcome this problem?
Any inputs will be of great help.
Kind Regards,
Abhijeet.
Edited by: Abhijeet Ambekar on May 4, 2010 2:01 PM

Hi Stefan,
Yes - I want to get rid of & # 60. But these (& # 60 and & # 62) are not added by XSLT mapping. Rather they are in the input available to XSLT map.
In sxmb_moni, i can see the inbound payload correctly :
<?xml version="1.0" encoding="UTF-8" ?>
- <rfc:HDK083_REFUS_SENDDOCU xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
<P_SIGN_DOCUMENT />
<P_XML_DOCUMENT><NemRefusionIndberetningSamling><NemRefusionIndberetningStruktur MessageID="1"><HeaderStruktur><SignOffIndikator>true</SignOffIndikator><TransaktionKode>Opret</TransaktionKode><IndberetningstypeKode>Anmeldelse</IndberetningstypeKode><FravaerTypeKode>Sygdom</FravaerTypeKode><FravaerendeStruktur><FravaerendeTypeKode>Loenmodtager</FravaerendeTypeKode><LoenUnderFravaerIndikator>false</LoenUnderFravaerIndikator></FravaerendeStruktur><IndberetningUUIDIdentifikator>bf9cc44e-af15-4e19-8457-5845d75385d2</IndberetningUUIDIdentifikator><ReferenceAttributTekst>ref. Nielsen-1503831372 (23. oktober 2009)</ReferenceAttributTekst>
but when I try to download the payload or right click on payload to view source I get something like below:
<?xml version="1.0" encoding="UTF-8"?><rfc:HDK083_REFUS_SENDDOCU xmlns:rfc="urn:sap-com:document:sap:rfc:functions"><P_SIGN_DOCUMENT></P_SIGN_DOCUMENT><P_XML_DOCUMENT>& # 6 0;NemRefusionIndberetningSamling& # 62; & # 60;NemRefusionIndberetningStruktur MessageID="1"& #62;& #60;HeaderStruktur& #62;& #60;SignOffIndikator& #62;true& #60;/SignOffIndikator& #62;& #60;TransaktionKode& #62;Opret& #60;/TransaktionKode& #62;& #60;IndberetningstypeKode& #62;Anmeldelse& #60;/IndberetningstypeKode& #62;& #60;FravaerTypeKode& #62;Sygdom& #60;/FravaerTypeKode& #62;& #60;FravaerendeStruktur& #62;& #60;FravaerendeTypeKode& #62;Loenmodtager</FravaerendeTypeKode><LoenUnderFravaerIndikator& #62;false</LoenUnderFravaerIndikator></FravaerendeStruktur& #62;<IndberetningUUIDIdentifikator& #62;bf9cc44e-af15-4e19-8457-5845d75385d2& #60;/IndberetningUUIDIdentifikator& #62;& #60;ReferenceAttributTekst& #62;ref. Nielsen-1503831372 (23. oktober 2009)& #60;/ReferenceAttributTekst& #62;
(extra spaces added to "& # 60" as browser was converting it to < ,>)
If i take the source code for payload and test XSLT mapping, it fails. But if I manually replace all "& # 60" with < and "& # 6 2" with >, then the mapping works fine.
So I think for XSLT map to work correctly, we need to replace all "& # 60 " . Please suggest.
Kind Regards,
Abhijeet.

XSLT Mapping: Namespace for prefix 'ns0' has not been declared

Hello, I am working on a synchronous SOAP call and having some trouble with the response message. The web service has its own namespace and I am trying to convert this to my custom data type in PI. PI wants the message to be in format of having ns0 prefix and namespace like we have defined (http://foo for example).
I have an XSLT mapping (see below) which works fine with my test response payload (pulled from SXMB_MONI source) on this online XSLT test site:
http://www.freeformatter.com/xsl-transformer.html
However when I import this archive to PI and test with operation mapping it always says "Namespace for prefix 'ns0' has not been declared."
This is very confusing because when I test it online, I see both prefix and namespace declaration perfectly. Is there a way to see the results in the PI test tool? After this XSLT java error it doesn't give me the output even in Trace Level All mode.
Please advise on this issue or if you know an easier way (such as altering my datatype/message type to match the inbound SOAP message). I tried working with the 3rd party WSDL but the response message types show a different root level node than what PI is receiving so I gave up to make my own matching datatype. I just have to solve this last inbound namespace issue and should be finished.
FYI I have refreshed all PI caches and activated all objects.
Thanks for your ideas!
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:ns0="http://foo"
<xsl:output method="xml" indent="yes" omit-xml-declaration="yes"/>
<xsl:template match="@* | node()">
 <xsl:copy>
 <xsl:apply-templates select="@* | node()"/>
 </xsl:copy>
</xsl:template>
<xsl:template match="/*">
 <xsl:element name="ns0:{local-name()}">
 <xsl:apply-templates select="@* | node()" />
 </xsl:element>
</xsl:template>
<xsl:template match="/">
 <xsl:element name="{local-name()}">
 <xsl:apply-templates select="@* | node()" />
 </xsl:element>
</xsl:template>
</xsl:stylesheet>

Some additional info, here is an example payload which goes through the XSLT mapping perfectly, but in PI I get the error about missing ns0 declaration.
XML input:
<bar xmlns='http://irrelevantnamespace'
xmlns:soap='http://schemas.xmlsoap.org/soap/envelope/'
xmlns:xsd='http://www.w3.org/2001/XMLSchema'
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
<foo/>
</bar>
XSLT mapped output using test tool and XSL above:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:bar xmlns:ns0="http://foo">
 <foo />
</ns0:bar>

XSLT Mapping for creating Excel files

Hi ,
I am following the blog /people/michal.krawczyk2/blog/2005/12/10/xi-generating-excel-files-without-the-java-nor-the-conversion-agent-not-possible by Michal regarding conversion of Flat files to Excel file format.
My input xml format is
 <?xml version="1.0" encoding="utf-8"?>
 <FILE>
 <Record>
 <Name>Navin</Name>
 <EmpID>123456</EmpID>
 <Location>Bangalore</Location>
 </Record>
 <Record>
 <Name>Ravi</Name>
 <EmpID>789456</EmpID>
 <Location>Hyderabad</Location>
 </Record>
 </FILE>
i need to convert this file into an Excel format with each record in single rows with Column Header names as Name,EmpID,Location.
Could you please suggest how the XLST mapping should be done for this as i am very new to XSLT mapping concept.
Please suggest how we can attain the target structure(datatype) and steps to do this XSLT mapping.
Note:- We are not doing Adapter module for this conversion.
Thanks,
Navin

> i need to convert this file into an Excel format with each record in single rows with Column Header names as Name,EmpID,Location.
This can be done with file content convertion. Use delimiter ; for excel
> Could you please suggest how the XLST mapping should be done for this as i am very new to XSLT mapping concept.
If you do not understand XSLT, you you want to maintain your development, in case if an error?
http://w3schools.com/xsl/default.asp

Idoc with XSLT Mapping ALE service error

Hi all,
I have the same problem with "converting to an ALE logical system".
In this case I have a Business System without logical system name in the SLD. This information for the IDoc control record, like SNDPOR, I will map with a xslt mapping.
In weblogs from Michael are the properties for the directory described.
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
I selected in the comminication channel the last two check boxes, as described in SAP help.
"Take Sender from Payload
If you want to take the sender of the message from the payload and not from the configuration information in the Integration Directory, set this indicator.
If you do not set the indicator, the information is taken from the configuration in the Integration Directory.
Take Receiver from Payload
If you want to take the receiver of the message from the payload and not from the configuration information in the Integration Directory, set this indicator.
If you do not set the indicator, the information is taken from the configuration in the Integration Directory.
If you set both of the above indicators, you do not require a heading mapping and do not need to set the alternative identifiers.
However, you must ensure that the SNDPRN, SNDPRT, RCVPRN, and RCVPRT fields are set in the IDoc control record.
Setting the senders and receivers of a message from the payload simplifies configuration and speeds up processing.
If the sender and receiver are not set correctly in the payload, the resulting error is only visible in the receiving system. "
In my XSLT-Mapping I set the appropriate Idoc fields:
<?xml version="1.0" encoding="iso-8859-1"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml"/>
<xsl:preserve-space elements="*"/>
<xsl:template match="DATEN">
<_-XXX_-018_XXXXX_XIDATEN>
<IDOC>
<xsl:attribute name="BEGIN">1</xsl:attribute>
<EDI_DC40>
<xsl:attribute name="SEGMENT">1</xsl:attribute>
<TABNAM>EDI_DC40</TABNAM>
<DOCREL></DOCREL>
<DIRECT>2</DIRECT>
<IDOCTYP>_-XXX_-018_XXXXX_XIDATEN</IDOCTYP>
<MESTYP>_-XXX_-018_XXXXX_XIDATEN</MESTYP>
<SNDPOR></SNDPOR>
<SNDPRN>XXXXX01IN</SNDPRN>
<SNDPRT>LS</SNDPRT>
<RCVPOR>xxx</RCVPOR>
<RCVPRN>xxx</RCVPRN>
<RCVPRT>LS</RCVPRT>
</EDI_DC40>
<xsl:variable name="pid" select="substring(.,1,1)"/>
But in the sxmb_moni the message is red with the error message :" converting to an ALE logical system"
Have you any idea?
With another interface I used a graphic Mapping and the same properties in the directory and it works.
Bye
Stefan

Hi togehter,
it works now, after cpa_cache and sxi_cache.
and and ...
<IDOCTYP>/XXX/018_XXXXX_XIDATEN</IDOCTYP>
<MESTYP>/XXX/018_XXXXX_XIDATEN</MESTYP>
Without: _-...
I would write a blog.
Does know one how that goes here?
Thanks
SDN is great
Stefan

XSLT mapping Help Required.

XSLT mapping Help Required.
Hi Experts,
I am New to XSLT Mapping. I am practising the below Example:
InputXML File:
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="Persons111.xsl"?>
<ns0:MT_XSLT_Source xmlns:ns0="http://XYZ.com/gen">
<Person>
<FirstName>Anshul</FirstName>
<LastName>Chowdhary</LastName>
<Gender>Male</Gender>
<Address>
<Street>2nd Main</Street>
<Houseno>83/b</Houseno>
<City>Mysore</City>
</Address> </Person>
</ns0:MT_XSLT_Source>
XSL StyleSheet File:
<?xml version='1.0' encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns0="http://XYZ.com/Gen"
Xmlns:ns1=”http://XYZ.com/Test”>
<xsl:template match="/">
<ns1:MT_XSLT_Target>
<Title> <xsl:value-of select="ns0:MT_XSLT_Source/Person/Gender"/> </Title>
<Name> <xsl:value-of select="concat(concat(ns0:MT_XSLT_Source/Person/FirstName,' '), ns0:MT_XSLT_Source/Person/LastName)"/>
</Name>
<Street> <xsl:value-of select="concat(concat(ns0:Mt_XSLT_Source/Person/Address/Houseno,' '),
ns0:Mt_XSLT_Source/Person/Address/Street)"/> </Street>
<City> <xsl:value-of select="ns0:Mt_XSLT_Source/Person/Address/City"/> </City>
</ns1:MT_XSLT_Target>
</xsl:template>
</xsl:stylesheet>
The Desired Output shuold be:
<?xml version="1.0" encoding="UTF-8"?>
<ns1:MT_XSLT_Target xmlns:ns1="http://XYZ.com/Test">
<Title>Male</Title>
<Name>Anshul Chowdhary</Name>
<Street>83/b 2nd Main</Street>
<City>Mysore</City>
</ns1:MT_XSLT_Target>
I have refered the xsl in xml and i am getting the below Oupt in a Single line like this:
Anshul Chowdhary Male 2nd Main 83/b Mysore
I am Unable to display in Target XML Fomrat as shown above. Please check and do the needful.
Regards,
GIRIDHAR

Hi,
I have used below for testing.
Input xml:
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="Persons111.xsl"?>
<ns0:MT_XSLT_Source xmlns:ns0="http://XYZ.com/gen">
<Person>
<FirstName>Anshul</FirstName>
<LastName>Chowdhary</LastName>
<Gender>Male</Gender>
<Address>
<Street>2nd Main</Street>
<Houseno>83/b</Houseno>
<City>Mysore</City>
</Address> </Person>
</ns0:MT_XSLT_Source>
xsl code:
<?xml version='1.0' encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns0="http://XYZ.com/gen"
 xmlns:ns1="http://XYZ.com/Test">
 <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
 <xsl:template match="/">
 <ns1:MT_XSLT_Target>
 <Title> <xsl:value-of select="ns0:MT_XSLT_Source/Person/Gender"/> </Title>
 <Name> <xsl:value-of select="concat(concat(ns0:MT_XSLT_Source/Person/FirstName,' '), ns0:MT_XSLT_Source/Person/LastName)"/>
 </Name>
 <Street> <xsl:value-of select="concat(concat(/ns0:MT_XSLT_Source/Person/Address/Houseno,' '),
 /ns0:MT_XSLT_Source/Person/Address/Street)"/> </Street>
 <City> <xsl:value-of select="/ns0:MT_XSLT_Source/Person/Address/City"/> </City>
 </ns1:MT_XSLT_Target>
 </xsl:template>
</xsl:stylesheet>
For testing in PI ,change the extension from .txt to .xsl and zip it and upload into PI as an imported archive .
Regards
Venkat

Encoding Technique converting in XSLT Mapping.

Similar Messages

Maybe you are looking for