Skip to Content
avatar image
Former Member

XSLT mapping errors

Hi,

I am tring to develope a senario with XSLT mapping. As part of this i have

1. Created Soruce and Target data types and message types

2. Created Inbound and outbound message interfaces

3. Imported both source and target messages types (XSD) files to mapforce tool and did all mapping b/w source and target.

4. Tested the mappings with input file in mapforce tool and mappings are working fine.

5. Copied the content from the XSLT tab and saved it as .xsl file and zipped the .xls flle.

6. Imported Zip file under import archive section.

7. Created a interface mapping with the XLS file

After this i tried to test the mappings in the interface mapping using the 'Test' Tab. Interface execution failed with below error message.

"Transformer configuration exception occurred when loading XSLT mm_file.xsl (http://testxslt.com/xsltmap, e4ce06a0-231e-11db-b54f-c55b0aeb1850, -1

Could not load stylesheet.com.sap.engine.lib.xml.util.NestedException: Attribute 'separator' not allowed for element 'xsl:attribute' "

Could you please suggest me where i did wrong and give me light on this.

Thanks in advance..

Regards

Sree

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Jul 07, 2009 at 09:27 PM

    Hi Reddy,

    It says Attribute 'separator' not allowed for element 'xsl:attribute'. So please check this. Probably you would have copied the xsds and done mapping in map force. I feel this attribute has only few values and in that values you dont have separator.

    Try to open the xsd in altova and see the possible values if any are there.

    Regards,

    ---Satish

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Srini,

      If you uploaded the xsd then open the same xsd in altova xml spy and go to that attribute and see whether any values they mentioned. But if you created manually a message type then dont need to check. Then the problem might be something else

      Regards,

      ---Satish