My Oracle Support Banner

R12 Payments Batches: Formatting/Processing Extract throws ORA-31061 and ORA-31011 errors during XML Parsing (Doc ID 1334833.1)

Last updated on JANUARY 24, 2018

Applies to:

Oracle Payments - Version 12.0.0 to 12.2 [Release 12.0 to 12.2]
Information in this document applies to any platform.

Purpose

In Oracle Payments (both Funds Capture [iPayment] and Funds Disbursement [AP Payments]) formatting takes a large XML document with base table data known as the Extract. The Extract is then parsed and formatted according to the rules of the corresponding BI Publisher (XDO) template. For more information about Extracts and Templates refer to <Note 799597.1>

During this process should illegal characters exist inside the extract ORA-31061 (XDB error: special char to escaped char conversion failed) and/or ORA-31011 (XML parsing failed) errors will be thrown.

It is very complex to determine which record(s) in the underlying base tables contain the offending character(s), and a single failure can cause a complete batch to fail.

This document will show how to identify/workaround the problem by means of an utility patch created for XML Database (XDB):

BUG 8246403 - NEED HINTS TO DEBUG "ORA-31011: XML PARSING FAILED" ERROR

Troubleshooting Steps

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
Purpose
Troubleshooting Steps
References

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