CX_SY_CONVERSION_NO_DATE_TIME:XSLT

Hi to All!
We have a SAP ABAP Web Service and we called it form an SAP ABAP Proxy both have been generated with the u201Coldu201D SOAP runtime.
Now we have adjusted the Web Service with an new field type date this field can be initial.
We have also regenerate the Proxy but now we get an Error at calling the Proxy .
ERROR: CX_SY_CONVERSION_NO_DATE_TIME:XSLT Exception aufgetreten.
Im ST-Program /1SAI/TXS00000000000000000024 ist bei der Deserialisierung ein Fehler aufgetreten.
.Der Wert 0000-00-00 ist kein gültiges Datum gemäß des XML-Formats für ABAP.
Is there a way to solve this error?
Thanks
Hermann

Did you found the solution??
I have the same error at the moment..

Similar Messages

CX_SY_CONVERSION_NO_DATE_TIME:XSLT exception when calling Web Service

I have created a Web Service on our Sandbox SAP server and am attempting to call it from our DEV SAP Server. The returning structure contains date fields that sometimes are null. A null date field in SAP is equal to 00000000.
When I call the Web Service and the date values are null, I get the following exception:
CX_SY_CONVERSION_NO_DATE_TIME:XSLT exception.An error occurred when deserializing in the simple transformation program /1SAI/TXS982F8A669D1A54B7AD0D.
Value 0000-00-00 is not a valid date in accord with the XML format for ABAP
I would not expect to see this type of error, sense the call is between two SAP systems.
Is there anyway to fix this without moving space to any null date field in the function module?
That's kind of annoying to do sense I have so many date fields.
Example:
IF date1 IS INITIAL.
    MOVE space TO date1.
ENDIF.
IF date2 IS INITIAL.
    MOVE space TO date2.
ENDIF.
IF date3 IS INITIAL.
    MOVE space TO date3.
ENDIF.
IF date4 IS INITIAL.
    MOVE space TO date4.
ENDIF.

Hi All,
I got a solution for this exception. Hope it will help to all facing this problem.
I was using proxy created from SE80.
In my proxy for exporting parameters of methods I have changed all date fields.
Earlier it was having Techn. type under Attributes of fields : XSDDATE_D. I chnaged this to DATS.
It worked fine.
Manish

CX_SY_CONVERSION_NO_DATE_TIME XSLT Exception

Hi,
we're running ECC6.0 and created a Web Service(WS) out of a SAP-Function Module(FM).
When calling this WS from Excel-VBA (XP; WS-Toolkit) the following error pops up:
CX_SY_CONVERSION_NO_DATE_TIME: XSLT Exception An Error occured while deserialization in ST-program /1BCDWB/WSSA..............
The value 4/6/2009 is not a valid date regarding XML-format for ABAP.
(this is my translation from original german error message, so english error message may differ a bit).
For explanation:
The FM/WS should give me a table with fields of type DATS and I think the single transformation cannot convert 20090604 to 2009-06-04 but only to 4/6/2009.
Any ideas would be great....

Thanks for your feedback, Ralph.
But, let me tell you that I tried again using a test tool for WebServices (soapUI 3.0.1, free software) and I got surprised to see that everything worked OK!, without errors (I had to previously clear "?" symbols and others "rare" values that the tool filled in for some parameters, nothing important).
All of the Date fields were transfered to the BAPI, according to xml format for dates: "YYYY-MM-DD".
So, I was able to avoid this "issue" by now, but I'm not sure what will happen until the real legacy sistem starts its owns tests.
I have to wait until that moment to be sure. But according to test tool soapUI, if you use that format, it should work (I'm using SAP ECC 6.0). Let's see what happens in the end.
May be there is some configuration or setting issue in the external/legacy system that calls your WebService.
Regards,
JG.

CX_SY_CONVERSION_NO_DATE_TIME exception

hello,
I have a problem using this service.
http://erp.esworkplace.sap.com/sap/bc/srt/xip/sap/ecc_empltimeeventerpcrtrc/version2?sap-client=800&wsdl=1.1&mode=sap_wsdl
if you try it on the Web navigator you get the exception below.
http://sr.esworkplace.sap.com/webdynpro/dispatcher/sap.com/tcesiespwsnavui/WSNavigator
CX_SY_CONVERSION_NO_DATE_TIME:XSLT exception.An error occurred when deserializing in the simple transformation program /1SAI/TXSAC09CA5318AB7CD2E251.Value yyyymmdd.... is not a valid date in accord with the XML format for ABAP
can you help please?

We send & receive a timestamp through webservices, we had the same problem with that format, with timestamps,.
This is because this format is abap format XSDDATETIME_LOCAL, but its not selectable in sproxy when altering the field.
To be able to select it, you can add it yourself:
Put a breakpoint in program
SAPLSPRX_UI
FORM get_extintview
on statement:
IF lv_act_Tab = sesi_tab_extview
( = line 76 of include LSPRX_UIF12 in our system).
Now, in SPROXY, select the field which should be XSDDATETIME_LOCAL.
Debugger pops up.
in table
GT_DYN_FIELD_ATTR take record with NAME = GS_EXTINTVIEW-OBJECT-ATTR_DT-R3_DATATYP_T
(the one having LISTBOX_VALUES entries)
and add entry to the LISTBOX_VALUES with values
XSDDATETIME_LOCAL
XSDDATETIME_LOCAL
now you can select it in the sproxy
select it and activate it.
Now you have correct datatype.

Webservice error......

Hi,
I am getting the below error when i am calling webservice from SOAP UI client, i have authorization of SAP_ALL and SAP_NEW.
Your help would be appreciated.
Thanks in advance.
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
   <soap-env:Header/>
   <soap-env:Body>
      <soap-env:Fault>
         <faultcode>soap-env:Server</faultcode>
         <faultstring xml:lang="en">CX_SY_CONVERSION_NO_DATE_TIME:XSLT exception.An error occurred when deserializing in the simple transformation program /1BCDWB/WSS0060807205412435000.Value is not a valid date in accord with the XML format for ABAP</faultstring>
         <detail>
            <ns:SystemFault xmlns:ns="http://www.sap.com/webas/710/soap/runtime/abap/fault/system/">
               <Host>undefined</Host>
               <Component>APPL</Component>
               <ChainedException>
                  <Exception_Name>CX_SOAP_CORE</Exception_Name>
                  <Exception_Text>CX_SY_CONVERSION_NO_DATE_TIME:XSLT exception.An error occurred when deserializing in the simple transformation program /1BCDWB/WSS0060807205412435000.Value is not a valid date in accord with the XML format for ABAP</Exception_Text>
               </ChainedException>
               <ChainedException>
                  <Exception_Name>CX_SXMLP</Exception_Name>
                  <Exception_Text>XSLT exception</Exception_Text>
               </ChainedException>
               <ChainedException>
                  <Exception_Name>CX_ST_DESERIALIZATION_ERROR</Exception_Name>
                  <Exception_Text>An error occurred when deserializing in the simple transformation program /1BCDWB/WSS0060807205412435000: Main Program:/1BCDWB/WSS0060807205412435000| Program:/1BCDWB/WSS0060807205412435000| Line: 25| Valid:X</Exception_Text>
               </ChainedException>
               <ChainedException>
                  <Exception_Name>CX_SY_CONVERSION_NO_DATE_TIME</Exception_Name>
                  <Exception_Text>Value is not a valid date in accord with the XML format for ABAP</Exception_Text>
               </ChainedException>
            </ns:SystemFault>
         </detail>
      </soap-env:Fault>
   </soap-env:Body>
</soap-env:Envelope>

Hi Ashok,
              looks like there is a mismatch in the Date and Time format being used by the server side program and the payload you are sending via SOAP UI client. To make sure that there is a consistency in the format please check the standard format for Date/Time in XML standards.
Given below is a reference:
http://www.w3schools.com/Schema/schema_dtypes_date.asp
In short the Date-Time should be specified in UTC format as 'YYYY-MM-DDThh:mm:ss' where
YYYY - indicates the year
MM - indicates the month
DD - indicates the day
T - indicates the start of the required time section
hh - indicates the hour
mm - indicates the minute
ss - indicates the second
There are certain variations to specify the Time zones etc. The details you can find in the above link or by googling "UTC time format".
Please do get back if you still didn't get it solved.
Regards
Barada.

Deserialization error [Causes and Cure]

Hi all,
What is meant by "desearilizing error" ? Please provide information or links on this.
And what should be done inorder to overcome it.
I have a client proxy in SAP and i am trying to consume a WEB SERVICE from .NET.
The services has 1 input parameter which is String datatype.
But when i test it i am getting Deserializing Error as
'CX_SY_CONVERSION_NO_DATE_TIME:XSLT exception'.
Please help. I am on the end of my wits :).
Thanks & Regards.
Yats.

Question: what is DESERIALIZATION ERROR
Answer: When you get the replay from .NET server, it is an XML document that needs to be converted into ABAP objects. The ABAP proxy tries to parse that XML and populate the ABAP objects -- this is called DESERIALIZATION.
The way ABAP proxy parses the XML response from a remote server depends on what is the XML "structure" it was programmed to expect. That "structure" is described in XSD part of WSDL. If you manually trim WSDL, the inner XSD (schema) definition may be compromised, and although you successfully create the proxies, yet those proxies would be expecting a slightly different structure of XML streams. Hence when the XML stream comes in, and the proxy tried to de-serialize (parse) to create ABAP object, it fails. This is called DESERIALIZATION ERROR.
You mentioned that you could successfully get a single record, while when multiple records came from server, it failed.
This happens because XSD schema is telling the proxy generator to somehow expect a single record, instead of creating a collection (Array) of records -- again a schema mismatch.
Solution: You need to analyze the incoming stream of XML through a tool e.g. Altoa XML Spy. That way you would figure out if the incoming stream is according to the trimmed WSDL you used to create you ABAP proxies.

Web service not working

Hi all,
I created a webservice for a function module.
Note : already there was a group of function modules in the webservice. I have included recently developed function module in the same webservice.
In soamanager, this function module is existed. but when i test that function module in soamanager, it is throwing an error saying -
CX_SY_CONVERSION_NO_DATE_TIME:XSLT exception.An error occurred when deserializing in the simple transformation program /1BCDWB/WSS9F3FEB5B8A0EC491810.Value 01-04-2009 is not a valid date in accord with the XML format for ABAP
please guide me to solve this issue.
thanks and regards,
Murali Krishna T

Are you passing a date to the web service? Check out the type of the corresponding field, usually in the SOAP messages you have to stick to [ISO 8601|http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#isoformats] for date and time formats. This means that your date should be of form yyyy-mm-dd (see also the schema definition for the [date|http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#date] type).
Cheers, harald

Is Header necessary to pass while calling a webservice ?

Hi all,
        I am calling a webservice which has 1 input parameter.
        My question is, 'Is it mandatory to pass header information while calling the webservice',
        while testing ?
        I got this question because, I tried calling the webservice, but got an error as,
        'CX_SY_CONVERSION_NO_DATE_TIME:XSLT exception'. But I am not passing any
        DateTime field.
        Further my webservice is located in a .NET system and I am trying to consume it from SAP.
        Please advice.
        Any links for the same will be of Gr8 help.
Thanks.
Yats.

Hi Venu,
DateTime is not as an input.
I have only 1 input parameter and that is a string.
Thanks.
Yats.
Edited by: Yatin Vishwas Parab on Jun 17, 2009 7:59 AM

DateTime Field causes dump in SOAP webservice

We're consuming a web service written in C# (.NET 4.0) which has datetime (xsd:dateTime) fields. The ABAP proxy class dumps when the service response is returned with:
CX_SY_CONVERSION_NO_DATE_TIME:XSLT exception.An error occurred when deserializing in the simple transformation program /1SAI/TXS72F7E0958348097F34D9.Value 2011-12-15T00:00:00 is not a valid date with time in accordance with the XML format for ABAP
Apparently SAP expects 2011-12-15T00:00:00Z but we are getting 2011-12-15T00:00:00 (without the Z). What does this mean and how can we fix it? Our .NET developer apparently has no control over the "Z" and this all seems a bit of strange reason to dump.
Here is the partial SOAP response:
<Expires>2011-07-18T00:00:00</Expires>
Here is the relevant WSDL:
<xsd:element minOccurs="0" name="expires" type="xsd:dateTime" />

ping

FileName in ABAP XSLT Mapping

Dear SDN,
In an integration scenario we are using sender File Adapter and a ABAP XSLT Mapping.
Is there any way to get the source FileName from such mapping. Im trying to use the adapter-specific message attributes, but it doesn't work, and I didn´t find an example, probably I and doing somthing wrong.
regards,
GP

Thank you for your help,
I just try to access the adapter-specific attibutes using:
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:key="java:com.sap.aii.mapping.api.DynamicConfigurationKey">
<xsl:variable name="filename" select="key:create('http://sap.com/xi/XI/System/File', 'Directory')" />
</xsl:stylesheet>
but the following error raised:
<SAP:Stack>Error while calling mapping program YXSLT_TEST (type Abap-XSLT, kernel error ID CX_XSLT_RUNTIME_ERROR) Call of unknown function</SAP:Stack>
have you had this situation?

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

PI 7.1 XSLT and ASMA

Hi,
I want to set the file name in the File Adapter as part of an XSLT-Mapping.
The steps are as follows in the XSLT:
1. Set Filename to new filename in ASMA.
2. Check if Month = '1' on payload xml. .
If month = 1 , then copy record in xml, else next record.
But I get an error:
Execution of mapping "urn:rlp.de:budgeting/OM_FileIN_to_FileOUT_Budget_1" failed. Reason: MappingException: Mapping failed, TransformException: Transformer exception occurred when executing XSLT BudgetFileNameMap (urn:rlp.de:budgeting, -1, 24903e11-1bce-11df-97ba-ddab0a076144), javax.xml.transform.TransformerException: com.sap.engine.lib.xsl.xpath.XPathException: Illegal number of arguments or types of arguments in a call of function 'dyn:put'., XPathException: Illegal number of arguments or types of arguments in a call of function 'dyn:put'.
The XSLT:
<?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"
                                     xmlns:ns0="urn:rlp.de:test:budgeting"
                                     xmlns:map="java:java.util.Map"
                                     xmlns:dyn="java:com.sap.aii.mapping.api.DynamicConfiguration"
                                     xmlns:key="java:com.sap.aii.mapping.api.DynamicConfigurationKey">
     <xsl:param name="inputparam"/>
     <xsl:template match="/">
          
          <xsl:variable name="dynamic-conf" select="map:get($inputparam, 'DynamicConfiguration')" />
           
          <xsl:variable name="dynamic-key"   select="key:create('http://sap.com/xi/XI/System/File', 'FileName')" />
          <xsl:variable name="new-value"     select="yourfilename.xml" />
          <xsl:variable name="fileName"      select="dyn:put($dynamic-conf, $dynamic-key, $new-value)" />
          <MT_FileIn_Budget>
               <xsl:copy-of select="/ns0:MT_FileIn_Budget/BudgetRecord[Monat=1]"/>
          </MT_FileIn_Budget>
    
    <xsl:copy-of select="." />
     </xsl:template>
</xsl:stylesheet>

found it, was an error in the code:
wrong:     <xsl:variable name="new-value"     select="yourfilename.xml" />
right:     <xsl:variable name="new-value"     select=" 'yourfilename.xml' " />
double quote single quote in a row!
cheers
Holger

XSLT MAPPING

In which cases we will go for XSLT MAPPING?
What are different functions available in altova map force ? please provide me the helpful material regards this?

Hi,
Check this link..
http://help.sap.com/saphelp_nwpi711/helpdata/en/73/f61eea1741453eb8f794e150067930/frameset.htm
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/01a57f0b-0501-0010-3ca9-d2ea3bb983c1
STEPS.
1. Open the Alto MapForce, import the source .xml and .xsd file in it
2. Similarly import the target .xml and .xsd in MapForce.
3.These two data files should match with source and target data types in Integration Repository.
4.Complete the graphical mapping using extensive list of XSLT functions available there.
5. Save the mapping file.
6.Click the XSLT tab. You will have the entire xslt logic there.
7.Copy that content and save it as .xsl file.
8. Zip above .xsl file and import the same into IR under Imported Archives.
Thanks.

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

XSLT Mapping error

Hi All
I am working on PI 7.1 where I have customized standard XSLT mapping according to my requirement.
I have to add 2 fields in the standard data type ReplenishmentOrder_Notfication from SNC 7.0 SWCV.
In standard scenario once IDOC STPPOD.DELVRY03 is released from ECC the PI scenario send this to SNC Proxy ReplenishmentOrderNotification_In.
In my requirement I have to send XML file generated from IDOC to one of Application Folder. I have customized data type, message type, operation mapping, service interface by coping standard things.
So the changes I have done in standard XSLT mapping are just changin name of data type and not added any mapping for the two new fields I have added to the data type as its not require at the moment.
When I am running test I am getting follwoing error in Trace. Here please notice that its mentioning standard xslt mapping program name only though on the top you see customized names.
Please give your inputs to resolve the issue. Thanks.
Operation Mapping
StppodDelvry03_MT_ReceivedDeliveryNotification_01
Name
StppodDelvry03_MT_ReceivedDeliveryNotification_01
Namespace
http://sap.com/xi/SNC/Global
Runtime error
TransformerException occurred during XSLT mapping StppodDelvry03_ReceivedDeliveryNotification_01 (http://sap.com/xi/SNC/Global, 46c20a71-248e-11dc-c4be-dd500a115642, -1)
<Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace> <Trace level="1" type="T">Interface Mapping http://sap.com/xi/SNC/Global StppodDelvry03_ReceivedDeliveryNotification_01 </Trace> <Trace level="1" type="T">TransfromerException during XSLT processing: Thrown: javax.xml.transform.TransformerException: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(, row:1, col:8)(, row=1, col=8) -> com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(, row:1, col:8) at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:251) at com.sap.aii.ib.server.mapping.execution.AbstractMappingTransformer.transform(AbstractMappingTransfor
Edited by: Amol on May 22, 2009 3:26 PM

Hi Amol
for the error CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV
<Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace> <Trace level="1" type="T">
just check this Thread issue is solved by restarting the service verifySenderAgreement
at thread
Re: Wrong Sender Agreement
Thanks
Abhishek

CX_SY_CONVERSION_NO_DATE_TIME:XSLT

Similar Messages

Maybe you are looking for