User login
Sponsored links
Recent blog posts
- AJAX XML - The JavaScript code
- AJAX XML - The PHP Page code
- Peoplecode Trace in a File.
- Display pdf file , image, website on peoplesoft page using html area.
- Ren Server -- Over View
- SQR Code
- AP PO Tables - Some imp Query.
- PeopleSoft XML Publisher - Report Development
- Debugging Functionality in Peoplesoft
- Steps for Creating an XML Export File with PeopleSoft
You are viewing this site as a guest. You can still ask questions and help others! Join our Dev2Dev IT Community to receive your own blog, share your knowledge, and much more.
PeopleSoft 9.0 BOE Crystal Report Printing Junk characters when the report is run from Prcs schedul directly sent to the printer
Fri, 02/05/2010 - 11:02am
We have just upgraded from PeopleSoft 8.8 SP1 to 9.0 in the test environment and facing a strange issue. Whenever we run any crystal report of BOEXI from the process scheduler and send it directly to the printer, it prints the report plus several page of junk chars. Reports sent to pdf, files and other output destinations are all working fine. SQRS are working fine.
Bookmark/Search this post with:
Unanswered Forum Posts
| Title | Under | Posted on |
|---|---|---|
| Abs Mgmt: How can Abs rule pro-rate contractor's last month's entitlement (need help urgently) | PeopleSoft Functional | 03/10/2010 - 9:21pm |
| Can we user LONG datatype as a search option in PeopleSoft | PeopleSoft Technical | 03/10/2010 - 11:22am |
| special caracters are not translated correctly when ftp from windows to unix | Programming | 03/09/2010 - 3:23pm |
| How to view the employees from particular country in peoplesoft? | PeopleSoft Technical | 03/03/2010 - 1:56am |
Update on this issue
-------------------------
Oracle support acknowledged this issue and are working on the fix on the current codeline PeopleTools 8.51. I have requested for a backport of the fix on Release 8.49.24 but Oracle Support pushed it back to me saying that I am the only customer facing this issue. I was wondering if anybody else faced this issue during their upgrade. Please help.
Post new comment