My Oracle Support Banner

EBS-DRM Integration When Run GL_DRM_IMPORT_PKG.gl_drm_import_process, OPP Log Shows: XML-20210: (Fatal Error) Unexpected EOF (Doc ID 1622663.1)

Last updated on SEPTEMBER 21, 2023

Applies to:

Oracle General Ledger - Version 12.1 to 12.2 [Release 12.1 to 12.2]
Information in this document applies to any platform.
GL_DRM_IMPORT_PKG; XML-20210

Symptoms

When trying to use the GL_DRM_IMPORT_PKG.gl_drm_import_process, it is ending in error. Cannot migrate flexfield values due to this error.

OPP log is showing the following error.

at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3548)
       at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:302)
       at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:176)
       Caused by: org.xml.sax.SAXParseException: <Line 12, Column 1>: XML-20210: (Fatal Error) Unexpected EOF.
       at oracle.xdo.parser.v2.XMLError.flushErrorHandler(XMLError.java:441)
       at oracle.xdo.parser.v2.XMLError.flushErrors1(XMLError.java:303)
       at oracle.xdo.parser.v2.XMLReader.popXMLReader(XMLReader.java:530)
       at oracle.xdo.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1312)
       at oracle.xdo.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:338)
       at oracle.xdo.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:285)
       at oracle.xdo.parser.v2.XMLParser.parse(XMLParser.java:289)
       ... 16 more

       Output file was found but is zero sized - Deleted
       [UNEXPECTED] ... java.lang.reflect.InvocationTargetException
       at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:597)
       at oracle.apps.xdo.common.xml.XSLT10gR1.invokeParse(XSLT10gR1.java:570)
       at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:235)
       at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:182)
       at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:1044)
       at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:997)
       at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:212)
       at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1665)
       at oracle.apps.xdo.

To obtain the OPP Log:

Responsibility: System Administrator
Navigation Path:

1. Concurrent -> Manager -> Administration
2. select the Output Post Processor
3. click on the Processes button
4. select the process that was active when the request ran
5. click on the Manager Log button to open the OPP log file.

For OPP log you need to check the date to make sure that it is for the time when the process was run.
If it is not then sometimes you have to shut down the opp and restart it which creates the log.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
 To obtain the OPP Log:
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.