My Oracle Support Banner

E1: UBE: Frequently Asked Questions (FAQ) about Storing UBE Output in Database From Tools Release or Later (Doc ID 2687819.1)

Last updated on JULY 15, 2020

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.


We are considering moving the print queue to database using P98617.
We would like to know the pros and cons of doing this along with best practices, any known issues and limitations. 


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
 1. How to Define Default Output Location to Store UBE Output in Database in Tools Release or Later?
 2. When UBE produces both pdf and CSV, is it possible to store CSV to file system while pdf to database ?
 3. Does storing the pdfs\csvs on database provide any disk space savings compared to file system storage ?
 4. Does E1 store\create UBE output directly to the database or does it use temp space to create pdfs on Enterprise server and then moves pdf to F9861101R as record?
 5. Is there any limitation on single pdf or CSV size on the database?
 6. How will storing to database effect TCs?
 7. Is is preferred to store batch output on DB?
 8. Are there any APIs available for developers to directly read the BLOB data to retrieve pdf\csv from database?

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