cancel
Showing results for 
Search instead for 
Did you mean: 

SAX mapping

Former Member
0 Kudos

Hi,

I have Java SAX mapping for IDOC-to-JDBC scenario. Sometimes it happens that, XI starts to create first XML SQL message, then in one moment stops(this XML hasn't right structure) and starts with second. With second, XI ends OK, but this has, XML syntactically, OK structure, and it can not be parsed to SQL. JDBC says:

Error while parsing or executing XML-SQL document: ERROR occured parsing request:com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:2, col:6)(:main:, row=2, col=6) -> com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:2, col:6)

This is some mix of two messages that should be mapped separatly. has anybody any idea?

thx

mario

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Mario,

This SAX Parser exception generally occurs when some condition is not being satisfied by the message payload when it is being parsed through the SAX Parser..for eg. if some tag in your message has data of greater legth than is specified in the condition in IR it throws a saxparser exception.

A mapping error is a non-fatal error that occurs during the mapping process.

The fatal errors are errors such as IOException that interrupt the mapping process and the exception is thrown by the mapping utility.

For more sax parser exception please refer:

http://java.sun.com/j2se/1.5.0/docs/api/org/xml/sax/helpers/DefaultHandler.html

Hope this will be of help for you.

Regards,

Shibani

*Reward with points if helpful*

Former Member
0 Kudos

all fields of target XML SQL message are type of string....

Former Member
0 Kudos

may be that messages that u are parsing , the fileds of which have different format.

Please check and let me know.

Former Member
0 Kudos

can you be more specific?