DOYENSYS Knowledge Portal

We Welcome you to visit our DOYENSYS KNOWLEDGE PORTAL : Doyensys Knowledge Portal

Tuesday, September 13, 2016

XML-20201: (Fatal Error) Expected name instead of .

Error :

Output post processor failed with below error processing report output

Caused by: org.xml.sax.SAXParseException: <Line 17018, Column 25>: XML-20201: (Fatal Error) Expected name instead of  .

Concurrent Log file Error:

Inserting invoice IDs into Temp Table
SQL STATEMENT :  INSERT into xxdn.xxdn_ACC_DYN_TEMP  SELECT pv.VENDOR_NAME supplier_name,   ai.invoice_num invoice_number,   ab.INVOICE_DATE invoice_date,   ab.invoice_amount  invoice_amount,   ab.invoice_id SOURCE_INVOICE_ID,   ab.ORG_ID,   ab.SET_OF_BOOKS_ID   FROM   hr_organization_information oi, hr_all_organization_units_tl ae, AND ae.language = USERENV('LANG')   AND NVL(ORG_ID,85 ) = 85

Inserted records into Temp Table successfully..

+------------- 1) PUBLISH -------------+
Beginning post-processing of request 321496451 on node USWS1HMSDVCM02 at 12-SEP-2016 16:48:24.
Post-processing of request 321496451 failed at 12-SEP-2016 16:48:28 with the error message:
One or more post-processing actions failed. Consult the OPP service log for details.

OPP Log file shows the following error:
[9/12/16 4:48:28 PM] [UNEXPECTED] [2058679:RT321496451] java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.lang.reflect.Method.invoke(
        at oracle.apps.xdo.template.FOProcessor.generate(
        at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(
        at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(
        at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(
        at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(
Caused by: org.xml.sax.SAXParseException: <Line 17018, Column 25>: XML-20201: (Fatal Error) Expected name instead of  .
        at oracle.xdo.parser.v2.XMLError.flushErrorHandler(
        at oracle.xdo.parser.v2.XMLError.flushErrors1(
        at oracle.xdo.parser.v2.XMLReader.scanNameChars(
        at oracle.xdo.parser.v2.XMLReader.scanQName(
        at oracle.xdo.parser.v2.XMLReader.getEntity(
        at oracle.xdo.parser.v2.NonValidatingParser.parseContentEntityRef(
        at oracle.xdo.parser.v2.NonValidatingParser.parseElement(
        at oracle.xdo.parser.v2.NonValidatingParser.parseRootElement(
        at oracle.xdo.parser.v2.NonValidatingParser.parseDocument(
        at oracle.xdo.parser.v2.XMLParser.parse(
        ... 17 more


select invoice_number from xxdn_ACC_DYN_TEMP where invoice_number like '%&%';

The above table is taken from the output file of the concurrent request and this gives the output column in which the "&" is included in the value which is supposed to be removed.

Checking output xml file Line 17018, we notice “&”, which is causing the issue.
<INVOICE_NUM>2016-0402 & 2016-5829</INVOICE_NUM>

You will have to run a data fix for this particular output or check with the developers to fix this.

No comments: