E1: UBE: Frequently Asked Questions (FAQ) about Storing UBE Output in Database From Tools Release 9.2.1.0 or Later
(Doc ID 2687819.1)
Last updated on NOVEMBER 01, 2022
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.2 and laterInformation in this document applies to any platform.
Goal
- Considering moving the print queue to the database using P98617.
- Pros and cons of doing this along with best practices, any known issues, and limitations.
Solution
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
| Goal |
| Solution |
| 1. How to Define Default Output Location to Store UBE Output in Database in Tools Release 9.2.1.0 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 the 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 move pdf to F9861101R as a record? |
| 5. Is there any limitation on single pdf or CSV size on the database? |
| 6. How will store to database affect TCs? |
| 7. Is it 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 the database? |
| 9. Does JD Edwards EnterpriseOne have the ability to migrate UBE output from the file system to the database table F986110R? |
| 10. After Selecting the Database via P98617 to store in the DB table F986110R can you still access previous jobs stored via the File System, e.g. Printqueue? |
| 11. What are the records present in F986110R table with SBFITYPE as IN ? |
| References |