SOAP Response XSLT Transformation Error

I am doing a webservice call and trying to transform the SOAP Response using XSLT.
I am getting the following error when the command CALL TRANSFORMATION Executes.
The element abap was expected for the XML-ABAP transformation
Please let me know if anyone ave received this error before and how did you solve it.
Regards
Sudhir Atluru

Hi Petra
for this Error com.sap.aii.af.ra.ms.api.ConfigException
check this Link
experts needed! com.sap.aii.af.ra.ms.api.ConfigException
http://help.sap.com/saphelp_nw04s/helpdata/en/78/20244134a56532e10000000a1550b0/frameset.htm
also refer SAP Note 978606
Regards
Abhishek

Similar Messages

How can I display XSLT transformer errors on a web page ?

Hi,
I have some JSP pages that access DB, create an XML based on DB data and then transform it into HTML through an XSLT stylesheet. Developing the XSL code it's easy to make mistakes and generate errors on trasformation, but what I receive on the web page is only a "Could not compile stylesheet" TransformerConfigurationException, while the real cause of the error is displayed only on tomcat logs. This is the code for transformation:
static public void applyXSLT(Document docXML, InputStream isXSL, PrintWriter pw) throws TransformerException, Exception {
        // instantiate the TransformerFactory.
        TransformerFactory tFactory = TransformerFactory.newInstance();
        // creates an error listener
        XslErrorListener xel = new XslErrorListener();
        // sets the error listener for the factory
        tFactory.setErrorListener(xel);
        // generate the transformer
        Transformer transformer = tFactory.newTransformer(new SAXSource(new InputSource(isXSL)));
        // transforms the XML Source and sends the output to the HTTP response
        transformer.transform(new DOMSource(docXML), new StreamResult(pw));
}If an exception is thrown during the execution of this code, its error message is displayed on the web page.
This is the listener class:
public class XslErrorListener implements ErrorListener {
    public XslErrorListener() {
    public void warning(TransformerException ex) {
        // logs on error log
        System.err.println("\n\nWarning on XEL: " + ex.getMessage());
    public void error(TransformerException ex) throws TransformerException {
        // logs on error log
        System.err.println("\n\nError on XEL: " + ex.getMessage());
        // and throws it
        throw ex;
    public void fatalError(TransformerException ex) throws TransformerException {
        // logs on error log
        System.err.println("\n\nFatal Error on XEL: " + ex.getMessage());
        // and throws it
        throw ex;
}When I have an error in the XSL stylesheet (for examples a missing closing tag), I can find on tomcat logs the real cause of the error:
[Fatal Error] :59:10: The element type "table" must be terminated by the matching end-tag "</table>".
Error on XEL: The element type "table" must be terminated by the matching end-tag "</table>".but on my web page is reported just the TransformerConfigurationException message that is:
"Could not compile stylesheet".
How can I display the real cause of the error directly on the web page?
Thanks,
Andrea

This code is part of a bigger project that let developers edit XSL stylesheets through a file upload on the system and we can't impose the use of any tool for checking the xsl. So, I need to display the transformer error on the web page.I see. This code is part of an editorial/developmental tool for developers to create and edit XSL stylesheets.
As part of the editorial process, XSL errors during editing can be considered a normal condition. In other words, it is normal to expect that the developers will generate XSL errors as they are developing stylesheets.
In this light, handling the XSL transformation errors is a business requirement that you need to handle. Using the Java Exceptions mechanisms, e.g. try / catch are inappropriate to handle business requirements, in my opinion.
I suggest that you look at how you handle the occurence of XSL errors differently than what you currently have. You need to:
(1) capture the Transformation exception on the server;
(2) extract the message from the exception and put it into a message that can be easily understood by the user;
The current error message that you have going to the web browser is not useful.
And you should not have the Transformation exception sent to the web browser either.
What you are attempting to do with the exception is not appropriate.
Handle the Transformation exception on the Business tier and use it to create a useful message that is then sent to the Presentation tier. In other words, do not send Java exceptions to web browser.
/>

SOAP Response XSLT mapping issue

Hi,
Source XML.
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Create__CompIntfc__APC_WORKER2_CIResponse xmlns:ns0="http://peoplesoft.com/APC_WORKER2_CI">
   <ns0:notification>y</ns0:notification>
   <ns0:detail>
      <ns0:keyinformation>
         <ns0:PERSON_ID/>
         <ns0:SUBMIT_DATE/>
         <ns0:ACTION/>
      </ns0:keyinformation>
      <ns0:messages>
         <ns0:type/>
         <ns0:messagesetnumber/>
         <ns0:messagenumber/>
         <ns0:messagetext/>
         <ns0:explaintext/>
      </ns0:messages>
   </ns0:detail>
</ns0:Create__CompIntfc__APC_WORKER2_CIResponse>
Target XML
<?xml version="1.0" encoding="UTF-8"?>
<ns1:Z_HPA_357_PROVISION_USER_IMS.Response xmlns:ns1="urn:sap-com:document:sap:rfc:functions"><SUCCESS>y</SUCCESS></ns1:Z_HPA_357_PROVISION_USER_IMS.Response>
XSLT Mapping
<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:fn="http://www.w3.org/2005/xpath-functions" xmlns:ns1="http://authserv.apc.com/peoplesoft">
<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes" />
<xsl:template match="/">
    <ns1:Z_HPA_357_PROVISION_USER_IMS.Response xmlns:ns1="urn:sap-com:document:sap:rfc:functions">
      <SUCCESS>
        <xsl:value-of select="soap:Create__CompIntfc__APC_WORKER2_CIResponse/a:notification" />
      </SUCCESS>
    </ns1:Z_HPA_357_PROVISION_USER_IMS.Response>
</xsl:template>
</xsl:stylesheet>
Can somebody help to figure out the issue in higlighted area of XSLT mapping.
We just need to move "notification" value to "SUCCESS" value of RFC.
thanks.
santosh,.

Hi Santosh,
add the source namespace with a prefix:
xmlns:ns0="http://peoplesoft.com/APC_WORKER2_CI"
do it most simple generic without path
do not forget the prefix
ns0:
use xsl:value-of:
xsl:value-of select="//ns0:notification"
Regards,
Udo

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.

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

SOAP Response Version Mismatch error with SAP web service

My company just recently upgraded to SAP CRM 7.
The old way of creating web services in SAP worked fine, but now, there is something a bit off with SAP. When I call the web service the send returns a Fault Event with the error : SOAP Response Version Mismatch
I had a simple web service created with only 1 text input and 1 text output to make sure that it wasn't the parameters or return type. I got the same error.
Searching on the forum or the web hasn't provided with any good answer to the issue.
Any thoughts on this?

Problem solved

XSLT Transformation Errors

I receive the following errors whenever I try to use xslt. I checked the file for strange characters and there are none. This happens with the delivered samples as well. I would appreciate any help.
Thanks,
Errors:
oracle.xml.parser.v2.XPathException: Unknown expression at EOF: text()|@*.
at oracle.xml.parser.v2.XSLExprBase.createPattern(XSLExprBase.java:170)
at oracle.xml.parser.v2.XSLTemplate.<init>(XSLTemplate.java:146)
at oracle.xml.parser.v2.XSLStylesheet.addBuiltInTemplate(XSLStylesheet.j
ava:671)
at oracle.xml.parser.v2.XSLStylesheet.initStylesheet(XSLStylesheet.java:
395)
at oracle.xml.parser.v2.XSLStylesheet.<init>(XSLStylesheet.java:147)
at WebQryFormatEngine.applyXSLtoXML(WebQryFormatEngine.java:50)
at testxslt.main(testxslt.java:40)

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by [email protected]:
I receive the following errors whenever I try to use xslt. I checked the file for strange characters and there are none. This happens with the delivered samples as well. I would appreciate any help.
Thanks,
Errors:
oracle.xml.parser.v2.XPathException: Unknown expression at EOF: text()|@*.
at oracle.xml.parser.v2.XSLExprBase.createPattern(XSLExprBase.java:170)
at oracle.xml.parser.v2.XSLTemplate.<init>(XSLTemplate.java:146)
at oracle.xml.parser.v2.XSLStylesheet.addBuiltInTemplate(XSLStylesheet.j
ava:671)
at oracle.xml.parser.v2.XSLStylesheet.initStylesheet(XSLStylesheet.java:
395)
at oracle.xml.parser.v2.XSLStylesheet.<init>(XSLStylesheet.java:147)
at WebQryFormatEngine.applyXSLtoXML(WebQryFormatEngine.java:50)
at testxslt.main(testxslt.java:40)<HR></BLOCKQUOTE>
Resolved the issue by turning off the jit flag on our AIX compiler.
Thanks

Xslt transformation error in web application deployed on top of SOA

Dear Experts,
I am doing xsl transformation using Javax API in JDveloper, is working fine when it is a simple java application. But fails to run if I deployed the same as web application. Also I have mentioned the xsl files in the server path properly. But receiving the same error. Also I have searched lot in the net, not able to find the problem . Please help me in this. very urgent. Thanks.
Error received:
javax.xml.transform.TransformerConfigurationException: XML-22000: (Fatal Error) Error while parsing XSL file (null)
Thanks,
Rajesh

And one more .. Use fully qualified name in inherits = "" tag
Inherits="namespace.classname, assemblyname, version=1.0.0.0, culture=neutral, publickeytoken=value"
Please remember to click Mark As Answer if a post solves your problem or Vote As Helpful if it was useful.

Tracing SOAP-ENV:Server.Exception errors

Hi,
I have generated my WebServices from an ADF Application Module using Jdeveloper 10.1.2.1.
After deploying the Web Services to the Application Server I call the web service test screens i.e. http://machine:port/MyWebServicesPath/MyWebService to check that the deployment has been successful.
When I enter the required values into the test screen occasionally I receive a SOAP response that contains error messages that are not being returned from my application code
e.g.
faultcode = FaultSOAP-ENV:Server.Exception
faultstring = oracle.jbo.common.ampool.ApplicationPoolException: JBO-30003: The application pool (package1.MyServiceLocal) failed to checkout an application module due to the following exception:
faultactor = /MyWebServicesPath/MyWebService
Checking the logs written by the web service application code confirms that these errors are thrown before the values reach the application code.
Are there any logs that would give me a clearer picture of what the problem is as tracking down the problem by trial and error often requires multiple time-consuming redeployments.
Thanks in advance
Lisa

Hi Lisa,
From a quick search with google on JBO-30003, it seams to indicate that the most common error condition is a dead connection to the underlying database.
The ADF Application Module that you are exposing as a service is most likely to be the one throwing this error. The SOAP server is then wrapping this runtime error into a SOAP fault with the code,actor and string that you see.
Hope this helps,
Eric

Error on XSLT transforming a SOAP response

Hello,
I am getting error ABAP XML formatting error in XML node of type "element", name: "abap" using my XSLT program.
Here is the XML response (SOURCE) as string.
b60##<?xml version="1.0" encoding="utf-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:execResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://webservice.hostname.com/"><execReturn xsi:type="xsd:string"><?xml version="1.0" encoding="Shift_JIS" ?><Report><Header><system>ABCWEB</system><dataType>ABCDEFGHIJ</dataType><sendType>response</sendType></Header><Body><SequenceNo>1234567890</SequenceNo><InquiryFactory>ABC</InquiryFactory><ProcessingID></ProcessingID><ProcessingDate>1234567890</ProcessingDate><KeyNo>ABCDEFGHIJ</KeyNo><ProcessingClassify>S</ProcessingClassify><Product>ABCDEFGHIJ</Product><ResponseClassify>0</ResponseClassify><OrderInformation-List><OrderInquiry><TransferNo>1234567890</TransferNo><TransferLineNo>000010</TransferLineNo><CustomerOrderNo>ABCDEFGHIJ</CustomerOrderNo><CustomerOrderLineNo>      </CustomerOrderLineNo><ShipInstructionNo>1234567890</ShipInstructionNo><DropUnitPrice>1234567890</DropUnitPrice><Qty>200</Qty><Amount>6000</Amount><WBSNo>                        </WBSNo><SpecPartNo>ABCDEFGHIJ</SpecPartNo></OrderInquiry></OrderInformation-List><SalesOrderPartNo>ABCDEFGHIJ</SalesOrderPartNo><CatalogPartNo></CatalogPartNo><AgentPartNo>1234567890</AgentPartNo><CustomerPartNo></CustomerPartNo><R3CompanyCD>1000</R3CompanyCD><OrderPlacingCompanyCD>R110011</OrderPlacingCompanyCD><ShipToCD>1234567890</ShipToCD><ShipToCompanyName>SINGAPORE</ShipToCompanyName><ShipToAddress1>ABCDEFGHIJ</ShipToAddress1><ShipToAddress2>ABCDEFGHIJ</ShipToAddress2><ShipToAddress3>SINGSAPORE</ShipToAddress3><ShipToAddress4></ShipToAddress4><ULPort>ABCDEFGHIJ</ULPort><DropCurrency>EUR</DropCurrency><DeliveryAirport>SINGAPORE</DeliveryAirport><DropMethod></DropMethod><SCMCustomer>EA07000442</SCMCustomer><RealShipToCd></RealShipToCd><SOCurrency></SOCurrency><SOPayterm></SOPayterm><LogisticCategory>0</LogisticCategory><SOOrderNo></SOOrderNo><MaterialKeyA1>1234567890</MaterialKeyA1></Body></Report></execReturn></ns1:execResponse></soapenv:Body></soapenv:Envelope>##0####
The above is the result after adding the following modifications in ABAP.
REPLACE ALL OCCURRENCES OF
      '<' IN wf_string1 WITH '<' .
REPLACE ALL OCCURRENCES OF
      '>' IN wf_string1 WITH '>' .
REPLACE ALL OCCURRENCES OF
      '"' IN wf_string1 WITH '"'
I would like to display the result starting from <BODY> as table as shown below.
SequenceNo       1234567890
InquiryFactory       ABC
ProcessingID
ProcessingDate    1234567890
and so on.
I am using the the same ABAP/XSLT program following example /people/durairaj.athavanraja/blog/2004/09/20/consuming-web-service-from-abap
Please let me know what I did wrong.
Tony

I have no idea why this is showing like this, but please bear with me. I tried every way I can to make my reply readable but the text editor is keeping on doing this. So here it goes.
Hi Sandeep,
I tried to debug the CALL transformation. I am getting CX_XSLT_FORMAT_ERROR and when I run the whole program this is the error message "ABAP XML formatting error in XML node of type "element", name: "abap"
Here is my XLST program for the response above.
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:strip-space elements="*"/>
<xsl:output indent="yes"/>
<xsl:template match="NewDataSet">
        <OUTTAB>
          <xsl:for-each select="Table">
            <OUTTAB1>
              <report>
                <header>
                  <system>
                    <xsl:value-of select="system"/>
                  </system>
                  <dataType>
                    <xsl:value-of select="dataType"/>
                  </dataType>
                  <sendType>
                    <xsl:value-of select="sendType"/>
                  </sendType>
                </header>
                <body>
                  <SequenceNo>
                    <xsl:value-of select="SequenceNo"/>
                  </SequenceNo>
                  <InquiryFactory>
                    <xsl:value-of select="InquiryFactory"/>
                  </InquiryFactory>
                  <ProcessingID>
                    <xsl:value-of select="ProcessingID"/>
                  </ProcessingID>
                  <ProcessingDate>
                    <xsl:value-of select="ProcessingDate"/>
                  </ProcessingDate>
                  <KeyNo>
                    <xsl:value-of select="KeyNo"/>
                  </KeyNo>
                  <ProcessingClassify>
                    <xsl:value-of select="ProcessingClassify"/>
                  </ProcessingClassify>
                  <Product>
                    <xsl:value-of select="Product"/>
                  </Product>
                  <ResponseClassify>
                    <xsl:value-of select="ResponseClassify"/>
                  </ResponseClassify>
                  <OrderInformation-List>
                    <OrderInquiry>
                      <TransferNo>
                        <xsl:value-of select="TransferNo"/>
                      </TransferNo>
                      <TransferLineNo>
                        <xsl:value-of select="TransferLineNo"/>
                      </TransferLineNo>
                      <CustomerOrderNo>
                        <xsl:value-of select="CustomerOrderNo"/>
                      </CustomerOrderNo>
                      <CustomerOrderLineNo>
                        <xsl:value-of select="CustomerOrderLineNo"/>
                      </CustomerOrderLineNo>
                      <ShipInstructionNo>
                        <xsl:value-of select="ShipInstructionNo"/>
                      </ShipInstructionNo>
                      <DropUnitPrice>
                        <xsl:value-of select="DropUnitPrice"/>
                      </DropUnitPrice>
                      <Qty>
                        <xsl:value-of select="Qty"/>
                      </Qty>
                      <Amount>
                        <xsl:value-of select="Amount"/>
                      </Amount>
                      <WBSNo>
                        <xsl:value-of select="WBSNo"/>
                      </WBSNo>
                      <SpecPartNo>
                        <xsl:value-of select="SpecPartNo"/>
                      </SpecPartNo>
                    </OrderInquiry>
                  </OrderInformation-List>
                  <SalesOrderPartNo>
                    <xsl:value-of select="SalesOrderPartNo"/>
                  </SalesOrderPartNo>
                  <CatalogPartNo>
                    <xsl:value-of select="CatalogPartNo"/>
                  </CatalogPartNo>
                  <AgentPartNo>
                    <xsl:value-of select="AgentPartNo"/>
                  </AgentPartNo>
                  <CustomerPartNo>
                    <xsl:value-of select="CustomerPartNo"/>
                  </CustomerPartNo>
                  <R3CompanyCD>
                    <xsl:value-of select="R3CompanyCD"/>
                  </R3CompanyCD>
                  <OrderPlacingCompanyCD>
                    <xsl:value-of select="OrderPlacingCompanyCD"/>
                  </OrderPlacingCompanyCD>
                  <ShipToCD>
                    <xsl:value-of select="ShipToCD"/>
                  </ShipToCD>
                  <ShipToCompanyName>
                    <xsl:value-of select="ShipToCompanyName"/>
                  </ShipToCompanyName>
                  <ShipToAddress1>
                    <xsl:value-of select="ShipToAddress1"/>
                  </ShipToAddress1>
                  <ShipToAddress2>
                    <xsl:value-of select="ShipToAddress2"/>
                  </ShipToAddress2>
                  <ShipToAddress3>
                    <xsl:value-of select="ShipToAddress3"/>
                  </ShipToAddress3>
                  <ShipToAddress4>
                    <xsl:value-of select="ShipToAddress4"/>
                  </ShipToAddress4>
                  <ULPort>
                    <xsl:value-of select="ULPort"/>
                  </ULPort>
                  <DropCurrency>
                    <xsl:value-of select="DropCurrency"/>
                  </DropCurrency>
                  <DeliveryAirport>
                    <xsl:value-of select="DeliveryAirport"/>
                  </DeliveryAirport>
                  <DropMethod>
                    <xsl:value-of select="DropMethod"/>
                  </DropMethod>
                  <SCMCustomer>
                    <xsl:value-of select="SCMCustomer"/>
                  </SCMCustomer>
                  <RealShipToCd>
                    <xsl:value-of select="RealShipToCd"/>
                  </RealShipToCd>
                  <SOCurrency>
                    <xsl:value-of select="SOCurrency"/>
                  </SOCurrency>
                  <SOPayterm>
                    <xsl:value-of select="SOPayterm"/>
                  </SOPayterm>
                  <LogisticCategory>
                    <xsl:value-of select="LogisticCategory"/>
                  </LogisticCategory>
                  <SOOrderNo>
                    <xsl:value-of select="SOOrderNo"/>
                  </SOOrderNo>
                  <MaterialKeyA1>
                    <xsl:value-of select="MaterialKeyA1"/>
                  </MaterialKeyA1>
                </body>
              </report>
            </OUTTAB1>
          </xsl:for-each>
        </OUTTAB>
</xsl:template>
</xsl:stylesheet>
Also I noticed that the actual response has two version header. Would it matter? Do I need to crop this out from the actual XML response before transformation. My OUTTAB is still empty.
*<?xml version="1.0" encoding="utf-8"?>*<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:execResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://webservice.hostname.com/"><execReturn xsi:type="xsd:string">*<?xml version="1.0" encoding="Shift_JIS" ?>*<Report><Header><system>
Please advise. Thank you.
Tony

SOAP Response error:

HI Experts,
Here my scenario is RFC PI SOAP synchronous interface. While sending the message from PI receiver system is expeting SAOP envelop I added this envelop with xslt mapping. Even response message is coming with SOAP envelop I removed with Xslt.. now I am getting below error message in response:
*Here i am not using any authoentication. it is not required..*
In SXMB_moni:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In communication channel:
Description
23.11.2011 14:45:11.557     Information     The message was successfully received by the messaging system. Protocol: XI URL: http://r3vidci.got.volvo.net:52000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
23.11.2011 14:45:11.564     Information     Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the request queue.
23.11.2011 14:45:11.568     Information     Message successfully put into the queue.
23.11.2011 14:45:11.572     Information     The message was successfully retrieved from the request queue.
23.11.2011 14:45:11.573     Information     The message status was set to DLNG.
23.11.2011 14:45:11.577     Information     Delivering to channel: SOAP_Receiver_BOSS_VID
23.11.2011 14:45:11.577     Information     MP: entering1
23.11.2011 14:45:11.579     Information     MP: processing local module localejbs/AF_Modules/MessageTransformBean
23.11.2011 14:45:11.599     Information     Transform: using Transform.Class: $identity
23.11.2011 14:45:11.634     Information     Transform: transforming the payload ...
23.11.2011 14:45:11.637     Information     Transform: successfully transformed
23.11.2011 14:45:11.638     Information     MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
23.11.2011 14:45:11.676     Information     SOAP: request message entering the adapter with user J2EE_GUEST
23.11.2011 14:45:11.695     Information     SOAP: completed the processing
23.11.2011 14:45:11.696     Information     SOAP: continuing to response message bf2ba0ac-15e1-11e1-cc01-00000c601d4e
23.11.2011 14:45:11.696     Error     SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
23.11.2011 14:45:11.698     Error     MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
23.11.2011 14:45:11.699     Error     Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
23.11.2011 14:45:11.700     Error     Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized. Setting message to status failed.23.11.2011 14:45:11.704     Error     The message status was set to FAIL.

Hi Rajesh,
I tried with XMLSPY.. i am able to send and get the responce witout any authentication.. I gone through vijay's blog... but i din't find any solution in that..
one more thing.. here inteface is sending from SAP portal system > SAP ECC> SAPI--> webservice(Microsoft system). whenever Portal team sending the message to SAP they are getting below error"
call to messaging system failed: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENER
In PI I am getting below error:
.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized

Xsl/stylesheet transformation problem in soap response(usinf xmlx-tags.tld)

Hi,
I have problem in transforming the soap response using xmlx-tags.tld.....
I was not able to read the <EmpName> value from the returned xml...
The stylesheet / xsl does not return any elements if I use other then "/" in match
attribute : <xsl:template match="/">
here is my soap call and stylesheet in JSP:
<x:xslt media="html">
<x:xml>
<ws:soap ttl="360000">
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
... making soap call here...
</soap:Body>
</soap:Envelope>
</ws:soap>
</x:xml>
<x:stylesheet media="html">
<xsl:stylesheet version='1.0' xmlns:xsl='http://www.w3.org/1999/XSL/Transform'>
<xsl:output method="xmll" omit-xml-declaration="no"
doctype-public="-//W3C//DTD HTML 4.0 Transitional//EN" indent="yes" />
<xsl:template match="GetEmpResult">
<html>
<body>
Result: <B>Symbol <xsl:value-of select="EmpName"/></B>
</body
</html>
</xsl:stylesheet>
</x:stylesheet>
</x:xslt>
the SOAP response looks like this:
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<GetEmpResponse xmlns="http://ws.cdyne.com/">
<GetEmpResult>
<EmpID>string</EmpID>
<EmpName>string</EmpName>
<SalAmount>decimal</SalAmount>
<Error>boolean</Error>
</GetEmpResult>
</GetEmpResponse>
</soap:Body>
</soap:Envelope>
I tried all the possibilities of template matches, but not succeeded....
Can somebody help me the correct <xsl:template> to access EmpName from the above
SOAP responses...
regards
Vijay

Hi,
Dynamic xslt are not quite supported in OSB, there are some approaches that may be helpful for your case though...
Have a look at these...
http://atheek.wordpress.com/2011/12/21/using-xalanevaluate-to-parametrize-xpath/
http://beatechnologies.wordpress.com/2010/12/01/dynamic-xquery-in-oracle-service-bus/
Let me know how you go...
Cheers,
Vlad

HTTP response code 500 : Error during parsing of SOAP header

Hi Experts,
I have a MAIL to IDOC scenario. An external third party emails invoices to our inbox - which we pick up and process the attachment. All is well when I test the scenario internally, but when the third party emails it fails with (see ERROR MESSAGE below).
When I look at the SOAP header of the failed message I see the values from the dump in this field:
<sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderTHREAD-INDEX">AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=</sap:Record>
Can anyone tell me what SHeaderTHREAD-INDEX does? Or what my problem is (Our email is Outlook)
ERROR MESSAGE.........
SOAPFault received from Integration Server. ErrorCode/Category: XIProtocol/WRONG_VALUE; Params: SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14), AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=協彎䅍䔾ਉ़䥎噏䥃䕟乏㸸㌱ㄵㄹ㰯䥎噏䥃䕟乏㸊उ㱁䵏啎呟䕘䍌彖䅔㸷⸵〼⽁䵏啎呟䕘䍌彖䅔㸊उ㱃啒剅乃失㹅啒㰯䍕剒䕎䍙ㄾਉ़䅍何乔彖䅔㸱⸴㜼⽁ꯃ䅢坡汫, ST: ST_XM; AdditionalText: An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC; ApplicationFaultMessage: ; ErrorStack: XML tag SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14) (or one of the attributes) has the incorrect value AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQ An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC Data loss occurred when converting AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1p
Transmitting the message to endpoint http://sdcxp1-ci.na.fmo.com:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during parsing of SOAP header.

We work with Microsoft Outlook, but I'm sure this could work with any email system.
This error only came from external emails - what we did in the end is to get the third party to email a particular email (email1) in our company. This is set up as a regular email account. On this email put a forward rule to email2 for a particular sender/subject. email2 is set up as POP3 so that XD1 can poll it - we also block any emails except from email1.
Doing this accomplishes a couple of things:
1) We get around the error because XI polls email2 (which has adapter settings of IMAP4 so we can see MAIL adapter attributes ie. sender, subject etc...When we originally had as POP3 we were not able to see these - but setting as IMAP4 causes the error for external emailers)
2) We have a SPAM filter - the XI email is clean from SPAM and the adapter will not have errors, as it only receives valid emails to process
3) We have a central email (email1) which is used to archive all XI emails - we use this for all email scenarios (as we also save to folder and forward in the rule)
Hope this helps your situation.

Error Reading Soap Response

Hi,
We are having a problem reading Soap Response:
Scenario: From XI/PI we are calling a webservice with Synchronous
message with WS-Security including Authentication, Signature, TimeStamp
and Encryption using SOAP Receiver Adapter. We are able to send the
request successfully and also the webServer is able to understand the
request and sending the response back. The problem is the PI is unable
to read the response and giving a below error:
com.sap.aii.af.ra.ms.api.DeliveryException: expecting end tag:
Transform, but found
InclusiveNamespaces at state 1
We tested successfully end-end with NON-Secured sites with out WS-
Security.
Please let me know if you have seen this error or any thoughts.
Thanks,
Laxman
This is the actual Request Message:
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:getUser xmlns:ns0="http://csa -namespace:8090/ddsssaws/IdentityManagementService">
<string>XYZ123</string>
</ns0:getUser>
Also we extracted raw traffic using TCPMon:
Below is the raw-traffic of SOAP adapter (used TCPGateway to capture the traffic)
Request:
POST /edsssaws/IdentityManagement HTTP/1.0
Accept: /
Host: 999.97.19.45:9999
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
Content-ID: <soap-1f3af770018111ddc0d300144f2515b0Atsap.com>
Content-Disposition: attachment;filename="soap-1f3af770018111ddc0d300144f2515b0Atsap.com.xml"
Content-Type: text/xml; charset=utf-8
Content-Description: SOAP
Content-Length: 5530
SOAPACTION:
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header><wsse:Security xmlns:wsse='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd' SOAP:mustUnderstand='1'><wsse:BinarySecurityToken xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='sap-9' ValueType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3' EncodingType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary'>MIIFFTCCBH6gAwIBAgIKZptrmQABAAALBTANBgkqhkiG9w0BAQUFADByMRMwEQYKCZImiZPyLGQBGRYDY29tMRMwEQYKCZImiZPyLGQBGRYDZWRzMRQwEgYKCZImiZPyLGQBGRYEY29ycDEUMBIGCgmSJomT8ixkARkWBGFtZXIxGjAYBgNVBAMTEUVEUyBFbnRlcnByaXNlQ0ExMB4XDTA4MDQwMTIxMjMyN1oXDTEwMDQwMTIxMjMyN1owIjELMAkGA1UEBhMCVVMxEzARBgNVBAMTCklUQVBJTlRERVYwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALjKvScjIEmp5Q1X3/gfR0WZO22KiEAOAx9kM0q3kpT/0dk2ZVit5YCBT4Zkt6Tttyh21xmnCcVgcRo0YOxXcXrLq25HRsSbxY3Zu37qq4tqExX5gQCtfR1pRjRrhQfDPmPGzFOrTzSjxJ5BH49p3KZcUhj7KpWQEakDBvJAgMBAAGjggMAMIIC/DAdBgNVHQ4EFgQUadHS0gj0CBQymaNnAlGJphSCB/YwHwYDVR0jBBgwFoAULNVTI/CtjM0k4MlzJLuQI4tVUy8wggEaBgNVHR8EggERMIIBDTCCAQmgggEFoIIBAYaBxWxkYXA6Ly8vQ049RURTJTIwRW50ZXJwcmlzZUNBMSgxKSxDTj11c3Bsc3NjYTAwMixDTj1DRFAsQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1jb3JwLERDPWVkcyxEQz1jb20/Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdD9iYXNlP29iamVjdENsYXNzPWNSTERpc3RyaWJ1dGlvblBvaW50hjdodHRwOi8vd3d3LmVkcy5jb20vY3J0cmV2bHN0L0VEUyUyMEVudGVycHJpc2VDQTEoMSkuY3JsMIIBDwYIKwYBBQUHAQEEggEBMIHMIG2BggrBgEFBQcwAoaBqWxkYXA6Ly8vQ049RURTJTIwRW50ZXJwcmlzZUNBMSxDTj1BSUEsQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1jb3JwLERDPWVkcyxEQz1jb20/Y0FDZXJ0aWZpY2F0ZT9iYXNlP29iamVjdENsYXNzPWNlcnRpZmljYXRpb25BdXRob3JpdHkwQwYIKwYBBQUHMAKGN2h0dHA6Ly93d3cuZWRzLmNvbS9jcnRyZXZsc3QvRURTJTIwRW50ZXJwcmlzZUNBMSgxKS5jcnQwDAYDVR0TAQH/BAIwADALBgNVHQ8EBAMCBLAwPAYJKwYBBAGCNxUHBC8wLQYlKwYBBAGCNxUIh4qV4WN/hPFkRuHwclug63SWS2GpOIihPT8LwIBZAIBBDATBgNVHSUEDDAKBggrBgEFBQcDATAbBgkrBgEEAYI3FQoEDjAMMAoGCCsGAQUFBwMBMA0GCSqGSIb3DQEBBQUAA4GBAGzyuh56APinQtmE9oWsT8NHcQqMASHZnN26RAofnxuIUH1VyBK2CGyiiDnCS0cDIGBl45sqOO8uRClE7CngeZEAV9JL5bhpUF6rywmFKvqe5FyqnrScczeaODV0g9sO4vUrwdGlReA5ncvtSN/u82MWDqtHAHBfpYQxZUrW</wsse:BinarySecurityToken><wsu:Timestamp xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsu-targetID-1f10b320-0181-11dd-aebd-00144f2515b0'><wsu:Created ValueType='xsd:dateTime'>2008-04-03T13:23:17Z</wsu:Created><wsu:Expires ValueType='xsd:dateTime'>2008-04-03T13:25:17Z</wsu:Expires></wsu:Timestamp><xenc:EncryptedKey xmlns:xenc='http://www.w3.org/2001/04/xmlenc#' Id='EK52789332'><xenc:EncryptionMethod Algorithm='http://www.w3.org/2001/04/xmlenc#rsa-1_5'/><ds:KeyInfo xmlns:ds='http://www.w3.org/2000/09/xmldsig#'><wsse:SecurityTokenReference><wsse:KeyIdentifier ValueType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier' EncodingType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary'>ykCivrkfwQdj30aJid9VGnjtY=</wsse:KeyIdentifier></wsse:SecurityTokenReference></ds:KeyInfo><xenc:CipherData><xenc:CipherValue>Fi5B3uBMSp4nAKh3rLAs4DJQ5iCLoupE1oq3VOFueea1Y90xI200OFraV2mRS2ywsejH36nwy
XYPuB5ZQScJampqZDtTR28cq890s4sEKFpycsNyNM9VScWaVoi4nKBKRIdGVoLgLf+NrmzJnXD
6eb4F6tWWyw8g2FJel4=</xenc:CipherValue></xenc:CipherData><xenc:ReferenceList><xenc:DataReference URI='#ED13608949'/></xenc:ReferenceList></xenc:EncryptedKey><ds:Signature xmlns:ds='http://www.w3.org/2000/09/xmldsig#'><ds:SignedInfo><ds:CanonicalizationMethod Algorithm='http://www.w3.org/2001/10/xml-exc-c14n#'/><ds:SignatureMethod Algorithm='http://www.w3.org/2000/09/xmldsig#rsa-sha1'/><ds:Reference URI='#wsuid-body-1f108c10-0181-11dd-838e-00144f2515b0'><ds:Transforms><ds:Transform Algorithm='http://www.w3.org/2001/10/xml-exc-c14n#'/></ds:Transforms><ds:DigestMethod Algorithm='http://www.w3.org/2000/09/xmldsig#sha1'/><ds:DigestValue>UaW58GCrg/nrA/EfW+OyHP2DCio=</ds:DigestValue></ds:Reference><ds:Reference URI='#wsu-targetID-1f10b320-0181-11dd-aebd-00144f2515b0'><ds:Transforms><ds:Transform Algorithm='http://www.w3.org/2001/10/xml-exc-c14n#'/></ds:Transforms><ds:DigestMethod Algorithm='http://www.w3.org/2000/09/xmldsig#sha1'/><ds:DigestValue>LFuszgJ412Fe8PRtK3W69RTXndY=</ds:DigestValue></ds:Reference></ds:SignedInfo><ds:SignatureValue>K4iZoVGhuI41fj9BdXx7wUz/JEi2pqh60gZZta8tOfaVmC1PfNtPg61N0sYescfM4RmkQpDorS1d
VB/DAJKz173HTD5rn/SuwmYgql4aVKPNlIDD90ZXoJ/mfzwT/Kei6yjWtvCYthCxaUtP/LFDB/dA
mr1OUAj9X2DHkzF6g=</ds:SignatureValue><ds:KeyInfo><wsse:SecurityTokenReference><wsse:Reference URI='#sap-9'/></wsse:SecurityTokenReference></ds:KeyInfo></ds:Signature></wsse:Security></SOAP:Header><SOAP:Body xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsuid-body-1f108c10-0181-11dd-838e-00144f2515b0'><xenc:EncryptedData xmlns:xenc='http://www.w3.org/2001/04/xmlenc#' Type='http://www.w3.org/2001/04/xmlenc#Content' Id='ED13608949'><xenc:EncryptionMethod Algorithm='http://www.w3.org/2001/04/xmlenc#tripledes-cbc'/><xenc:CipherData><xenc:CipherValue>lZkC7zZZfqBUg5rnqMZypi5ZvnPBvw36fjeFmCDQ5DMDjKXShO4apBjBE3gUsLGL1TMli18D0NWK
dmVHQTePitGhvQ7YiyaXgjekZckS2P91Qv/9Zut5/hzCYhgVarnUgGmr8Qi4aSYXCY0oBD6SzVXy
/UoQHPASF3mhYPaFBtmTJu2dHmV6v4HTKC+Om0</xenc:CipherValue></xenc:CipherData></xenc:EncryptedData></SOAP:Body></SOAP:Envelope>
Response:
HTTP/1.1 200 OK
Date: Thu, 03 Apr 2008 13:23:54 GMT
Content-Length: 9511
Content-Type: text/xml
Set-Cookie: JSESSIONID=cTPmH0hKYvKqK427JJb573FT1RWZhHY5l7XnLlsjsk6yRkS2g5y6!1973031667; path=/
Connection: close
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><env:Header><wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" env:mustUnderstand="1"><xenc:EncryptedKey xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"><xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5"></xenc:EncryptionMethod><dsig:KeyInfo xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><wsse:SecurityTokenReference><wsse:KeyIdentifier xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier" wsu:Id="Id-dgdMMmsGkjae8aSYF_59_xwe" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">adHS0gj0CBQymaNnAlGJphSCB/Y=</wsse:KeyIdentifier></wsse:SecurityTokenReference></dsig:KeyInfo><xenc:CipherData><xenc:CipherValue>mbOmTXSiYuEiWHbP3dbrDXFpZaSoQ084wMBt7uRxNo49p1fpQBkDpr/H2wPNbHy4qzSTVzP7EESzWFjFEb/7BH3dt4JuyzBFH1M0X77YBW5YHNGpiUmj934ziydojqcU6jWBsUaFxXsAPmvy0q3vVk8xnZcQHxMNhPS5ebK9o=</xenc:CipherValue></xenc:CipherData><xenc:ReferenceList><xenc:DataReference URI="#Id-yMgwZrtQctSvW1mT1sDWdZ8D"></xenc:DataReference></xenc:ReferenceList></xenc:EncryptedKey><wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" wsu:Id="Id-2DXBQHwdRE0oquWQV0mjtw1U" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">MIIFVjCCBLgAwIBAgIKfps5MgABAAADHjANBgkqhkiG9w0BAQUFADByMRMwEQYKCZImiZPyLGQBGRYDY29tMRMwEQYKCZImiZPyLGQBGRYDZWRzMRQwEgYKCZImiZPyLGQBGRYEY29ycDEUMBIGCgmSJomT8ixkARkWBGFtZXIxGjAYBgNVBAMTEUVEUyBFbnRlcnByaXNlQ0ExMB4XDTA2MDUyMzIzMDY0OVoXDTA4MDUyMjIzMDY0OVowYzELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlRYMQ4wDAYDVQQHEwVQbGFubzEMMAoGA1UEChMDRURTMQwwCgYDVQQLEwNTRFMxGzAZBgNVBAMTElNTQVdlYlNlcnZpY2VzLURFVjCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA0qRmvQkxnPnEZQNSabPVwM6sEf8vFUOAlgQ9uuiDImVmDw4Afg45zbmTBeDdv4wsIap7kI4VJhv60SdOQg6i1mIEi83Qk7UJYD8XvKuOalSLYhHu92lsp0kIZlAdzipVd1Pp0cI3wSvP6o9zfX0gALpisf8rGJ1CkVWbtHaVp0CAwEAAaOCAwAwggL8MB0GA1UdDgQWBBTKT4KKuR/7BB2PfRomJ31UaeO1jAfBgNVHSMEGDAWgBQs1VMj8K2MzSTgyXMku5Aji1VTLzCCARoGA1UdHwSCAREwggENMIIBCaCCAQWgggEBhoHFbGRhcDovLy9DTj1FRFMlMjBFbnRlcnByaXNlQ0ExKDEpLENOPXVzcGxzc2NhMDAyLENOPUNEUCxDTj1QdWJsaWMlMjBLZXklMjBTZXJ2aWNlcyxDTj1TZXJ2aWNlcyxDTj1Db25maWd1cmF0aW9uLERDPWNvcnAsREM9ZWRzLERDPWNvbT9jZXJ0aWZpY2F0ZVJldm9jYXRpb25MaXN0P2Jhc2U/b2JqZWN0Q2xhc3M9Y1JMRGlzdHJpYnV0aW9uUG9pbnSGN2h0dHA6Ly93d3cuZWRzLmNvbS9jcnRyZXZsc3QvRURTJTIwRW50ZXJwcmlzZUNBMSgxKS5jcmwwggEPBggrBgEFBQcBAQSCAQEwgf4wgbYGCCsGAQUFBzAChoGpbGRhcDovLy9DTj1FRFMlMjBFbnRlcnByaXNlQ0ExLENOPUFJQSxDTj1QdWJsaWMlMjBLZXklMjBTZXJ2aWNlcyxDTj1TZXJ2aWNlcyxDTj1Db25maWd1cmF0aW9uLERDPWNvcnAsREM9ZWRzLERDPWNvbT9jQUNlcnRpZmljYXRlP2Jhc2U/b2JqZWN0Q2xhc3M9Y2VydGlmaWNhdGlvbkF1dGhvcml0eTBDBggrBgEFBQcwAoY3aHR0cDovL3d3dy5lZHMuY29tL2NydHJldmxzdC9FRFMlMjBFbnRlcnByaXNlQ0ExKDEpLmNydDAMBgNVHRMBAf8EAjAAMAsGA1UdDwQEAwIEsDA8BgkrBgEEAYI3FQcELzAtBiUrBgEEAYI3FQiHir5XhY3E8WRG4fByW6DrdJZLYak4iKE9PwvAgFkAgEEMBMGA1UdJQQMMAoGCCsGAQUFBwMBMBsGCSsGAQQBgjcVCgQOMAwwCgYIKwYBBQUHAwEwDQYJKoZIhvcNAQEFBQADgYEALsVozc1aVcPNBVsRXRbAiStchxG2fKDOt9kRzL6BHtQa/fkp81EjOBhETn8N1IHLUsINn05wGgdDA2UszjLtRIpQmdpCyh2gzFW8Dlx5X7vJyvJsoDOPDBArv55dTjCEfok1oz3ux3mrVotuvr1pKIVTr7ylpRM8p8GBXw=</wsse:BinarySecurityToken><dsig:Signature xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:SignedInfo><dsig:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></dsig:CanonicalizationMethod><dsig:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"></dsig:SignatureMethod><dsig:Reference URI="#Id-wS1xP_ArcYYXY4qkqYznI7_W"><dsig:Transforms><dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>tr3NrozQWsKrvH38naIEnQXrzgQ=</dsig:DigestValue></dsig:Reference><dsig:Reference URI="#Id-1vPAqVSMhSLH3WiBQkTTfldz"><dsig:Transforms><dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"><c14n:InclusiveNamespaces xmlns:c14n="http://www.w3.org/2001/10/xml-exc-c14n#" PrefixList="xsd n1"></c14n:InclusiveNamespaces></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>AUWlqeyq6w5LQnggK5dT6flLUU=</dsig:DigestValue></dsig:Reference></dsig:SignedInfo><dsig:SignatureValue>Yx5Pre8VChTLOhPVln5xhO21dM93a2FPxQTsZY1BBIWlqeHkAEQqXvhI/EU459QZIGDOubLK0Z9AT0SRmDOgtnWNBT0duqveQ1Ippbd0hXaehW48ObrMIKnYfq5ub1kNYv9mslybPRZw9OaiijNmLfIty8qc8ctRV0lFwAjcQyk=</dsig:SignatureValue><dsig:KeyInfo><wsse:SecurityTokenReference><wsse:Reference URI="#Id-2DXBQHwdRE0oquWQV0mjtw1U"></wsse:Reference></wsse:SecurityTokenReference></dsig:KeyInfo></dsig:Signature><wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="Id-wS1xP_ArcYYXY4qkqYznI7_W"><wsu:Created>2008-04-03T13:23:55.459Z</wsu:Created></wsu:Timestamp></wsse:Security></env:Header><env:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" wsu:Id="Id-1vPAqVSMhSLH3WiBQkTTfldz"><xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Type="http://www.w3.org/2001/04/xmlenc#Content" Id="Id-yMgwZrtQctSvW1mT1sDWdZ8D"><xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"></xenc:EncryptionMethod><xenc:CipherData><xenc:CipherValue>LB6IKwEJgvTPdPGNeIzcpjPjC9GXi3sou5PaCnF3m4x6ToA6gDV5Sw/ODnCEeqFURgWFX8ZgxYF9YJdyj7ERAifs8MNBh/rHCitT02mU8pirwGdqSXlfCX4KYsHtUnyiGKbbMCwvCCs4LgBPnx8tCN39aazA1Ge/5JPfwupYMU/lAbyajdP1qva/gxhMCqGkgAnQgB1TJDfARvDsJnx6p2zqKsnRnNreBFClyBG7GHeMvpnzg4poPCFlj2baIoK2CSQmVbPdcPk4rgg1PAWDQwIIzBCKpZjysHeb/sW9jObekbnn4mCnUdzjRERoklstpZNeWKi/jLEaNsIX1ixhsUyWIyknYGaBjDiiGqmS6BIO1RHu0SydiMv1L/FzIWgyO9VhilGdTWsVDP6CxljxTqg41bobuPazkjQHyBK9rCGQI9J/bjSiA2S6FBDHxhA6SfDjyhvGzDhGNLMd/***2ieUGQWg/atFbqItqW2HZzb7T0cuIiROBYaGLUbWnghcUXAn9dV38GbCMfWk65OhpkD5EQXr/5bPxK41L3sPIrAs2JnMM9nLuj6gLo35VMlsdVQ1c0o3JYQ4JARnSlnUrgW20Cilwf3Fn2m7Yj4QicC6RUhChEudnbgYIjqq0Ypc8BsjJWAPYRuVAUVArINqgUjCNuOxQKV3dyEayS0lZ8UOBfopGBnIlEDS9h62ZIiIKfRhCD6xLsY1PED7K5ZHRvj2TEtQtYoZxeTNDH7/IdukO/cATF9B0DhSvx2YK8EzlG3pygcLGeHZ4DfwmGC5lnO5NZrqFaHXa1LNNgZ9H1rezZyOfizbvT/O5mC8tvINNvP5Ik37OdD6Lmjnc4u0gAKee6QqQ7uk8A6xbrjrnOWp46vnoNmvMZxyAMAD8xFBz9b8MVHu0IJX5etLdRbjsSsMYNpUomqFjfweFe3NeHESUA5IhkYUQVNNwJJ3MCpJDWWHFNLEbzRoUolXVOQhC0PC6j6KmHQH2yib0KWKKJn7kLrUtgGazJMatLDhWDU5oEtZbDJzauxikxto0R6ZirhjKqmVCeVu51yrbW4lgC2upXxJsQ2q5igBaX7Qvz4D1ICkp1m7CRG7cWrU6MfBSXusRsPIp/7wJsdBpXSPb97cZi6y82EP6iQhsyRJ9YODUr22WObb4CvIYo8bDFW1Sw6BImoqkgsoXB/j2oNp0g6vLhYy0OjF5LAdDbhDk23WA00KGj9xAHEPVkqfXdivfc3quxWdpIBri0JnQGA/T1GsxwM4YKvhp5hPl28sgLeo7/I0DstkK6Jispkt5/03N364bRQBAHykAqUAyDvMHz8jiZK0Jo2cnTDTzoDtDi9q2wbSI25lh31FZ68kKJ1t399VRdF4JlSKvaXE8pj1ljE3J6GsII6haD3W17Kns2hmnduL0pEeChUgq0VrXaK8k5e0CR1JdmzVEHNo7WKWwB901cOrtRfxh1yQWvw0dHCSlxzAlISAb7Y2t0MlIoITIKi9XzJSpbxtp5zCQiup3PPDni1wQWotYd9WVZ2Zs2KxDkusDbENOAu68RjtWoOQxGXPrek73CQ9ja2D6doNjdbwX9Exrhqlek9507Sn0J2RO5kJG6huXD3TTXcBcBlD8HYq76JfSNtqgpUwKztPCxaECMmvTm4n1YRT5pkpKfOmlx262TJllv1l2B5cs3f6ODWf/ULarjwMPT2ajviYvCDXl4Kl8HNcmXKhR3W8IzCvWCsPwwDoFbjCk5Xkdd6IVPAX9i0LP5hZqS1bMrJnTreNTVd4glne7T6SdjkFt2MR1UJnsNHlVDoeGhb5VhfphgPg2r1DUyY7k3QlXHGxCBctjlkTUVg9D0NgWf4JrE2KXtdCPR/gX7HjrR6wq24UsibqOH5yi2Zh2hGwP2OWrPRQ6QMqIdW2voAux0GOkL7Ip8GCRml5eilopmRyh8D3PxWw8CwfC81slylodVHvGP8AjGE9cddQhMzQ2s96ZPQVTLEo734UQFkH511HtJGWVCTbxGBmtpEyoJZSJJ9CeG2sXuwEGF7YXR31xJJZbtOKFyskQw3BJGb1SE35iF5lr0hshYB1/gm2YmlTX68nZtux9NWRIKnJ3EHvWUc9UIudzoEMf0LyLZm5pFtkZAUQ16F4BfqEVJekVlUBOs1dCSYN6lUcsVzinhUcY1eBni75vEXaO8zSTy4ZwcOiGYvR9QK2bSuzYen1LKBaFK6UIAVstr29avGAGp5nk3qM63/05rUv2jnDM6XYIoFSx1lpE7SwtvbiRUQjgUA4ZX7Oa7Mp9HJj5W0o7ZVViKbYTtxux5/2AXgXxLo/i3YsHd7BUE/2KTjUrKokTYUzCgTlXkSmYOfRY1wdxeixrLfbSWBD1Y4ZbcMw3l/57XIPmGl42HrRyEFIxGnt7kQHR9A3abfJ93E0Y8AMiQuhG2/WTZho/IzxQ/OfDJm78o97K10pbe7OUIrfpPNTfM3cenEd37ZFWI67yPNwYfiZw8E7uks8GIKSAqrt7q55C10EpmizEcydD5EKtGyElXk6ifr3GO6WbHJNUp6FvgyHQTF6VXRiC91Rv/ZvUQggxRDyF6HibOq5BqDwTbMY0OnbB6nR3KlGYfhkBfEUiqbd10HYzCzWx0uGv54swAwsRUtOQFMpbr5B17yXdE5vGN2uTm02Bgr3EwOUyuw2ttgdUedDH8APmOlDr23wPiFljsTgWbbX/UZQGCyhNxa8avQtDdlymu8e8PS5tMupjMSkJtULUUXQyoKGwcXwwvp25iubNODEt5aZNt45bGKwOW5P3Xzu2ZJ6tAtW/zh7NfN1EHVZIwIlxWgPaag0ComeirsmZfNu3W2wge7Cg9aOYws81iIRaLa0YgYWZwH3C6yTRRQcM8fx1U1TiK2tIkFcc4iAjefZKMHBsodtTzo4EYaYvb9SyjGgZLTMYSlTbpx31Ot0T/t8kFxpML/ObDgoKoxWUVXxfD74HDW/0Uo9JDgdaV/lxJ2CJ7y8gb4ayKsVRNB4BmP5OzA/q9vzZWgtfoM4ODu//vsAed9Dvi4f1pJt5Cf8WWxv1PtWS4gvFe87a03kyhwSzI4obai23oYlCcyrUyL9LBZCwcBgn4tDcno6HPIHT2iEpi00sTuTD2bqXyTkXrxgzGSwlfBzCXr7xczoZDJoU5oj5t59cyq/faUZZkhc0bb8dhOH2/oYcanpfdtNS64VeO42eXaPbkMP00IrHTAUb2KxXQa7h80vB3LMA29cS3EBaJ8pnIJ/sPh0bT5A/FiiiJVJNm8g7EBcvd2nbJWRAkVNp1SxLPoUKF1dRt3OiJwhbdOASOnmJS8IXRjskuIYRsMgXSNdlMGxadedsdB9TKRvgzGkutWu9mQ3+0XJJIp7S23E8b3OLH1CAxhH3wyWu8TmeksImbGc0VY7oSTTtNNWOdeRDQ==</xenc:CipherValue></xenc:CipherData></xenc:EncryptedData></env:Body></env:Envelope>

Any thoughts???
Appreciate your input.
Thanks,
Laxman

Error in ABAP XSLT transformation

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

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

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

SOAP Response XSLT Transformation Error

Similar Messages

Maybe you are looking for