My Oracle Support Banner

PO Output For Communicate XML Fails With ORA-31061 - Solution For Special Characters (Doc ID 1346198.1)

Last updated on MAY 09, 2024

Applies to:

Oracle Purchasing - Version 12.1.3 and later
Information in this document applies to any platform.


Note: The same solution could be applied to any report in E-Business Suits as long as the same "ORA-31061: XDB error: special char to escaped char conversion failed." error was captured in FND Debug. 

On 12.1.3 "PO Output for Communication" completed with error.

Following errors were captured in the Concurrent log file

Document Template Code :PO_STANDARD_XSLFO
Language Code :US
Document XSL Contents Tue Jun 14 05:57:43 EDT 2011
Retrieved the Document XSL Tue Jun 14 05:57:43 EDT 2011
Calling the getPOXml method
GenerateDocument::getPOXml() : l_exists 1
GenerateDocument::getPOXml() : m_whichTables MAIN
GenerateDocument::getPOXml()- Calling the POXMLGEN method Tue Jun 14 05:57:43 EDT 2011
GenerateDocument::getPOXml() - Exception
genDoc() : PoPDFExceptionoracle.apps.po.communicate.PoPDFException: PO_PDF_XML_FAILED
oracle.apps.po.communicate.PoPDFException: PO_PDF_XML_FAILED

Following debug message was captured in FND Debug as well
"ORA-31061: XDB error: special char to escaped char conversion failed."

Reproducible Steps

Responsibility = Purchasing, Vision Operations (USA)
Navigation = Reports > Run > Name = PO Output for Communication
Submit the report to run and the concurrent program will completed with error.

Note: Issue is specific to XML reports


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

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