Best Of
Re: PO PDF's are getting generated when PO's are revised using PO change API
The correct API is "PO_CHANGE_API1_S.update_po". You need to customize the PO approval workflow to by-pass approval for specific changes. This will avoid regeneration of PO PDF and further communication out.
Refer: KB729385
Customize PO Approval workflow by adding conditions to bypass reapproval when PO change is from external system or by modifying PO_CHORD_WF6.standard_po_reapproval(POXWCO6B.pls) procedure and add conditions to bypass reapproval.
Re: patch 6880880 - Windows x64 - hash Digests: md5sum - sha256
You're right, such validation only works against corrupt/failed downloads, it's just a file validation.
This is what I use checksums for: validate download success. So, in that context..
I do agree checksums to be displayed as well
Re: Post to Ledger is yes in subledger, but still the journals were not posted in GL
Hi,
Common Causes for Journals Transferred but Not Posted
- GL Posting Failures
• Even if Post to Ledger = Yes, the posting step is handled by the GL posting engine.
• If journals hit validation errors (e.g., invalid accounts, period status, suspense rules), they transfer but remain unposted.
• Check the Posting Execution Report in GL for those dates — it will show if journals failed posting due to errors. - GL Period Status
• If the GL period was Open for journal entry but not Open for Posting during those 20 days, journals transfer but cannot auto-post.
• Sometimes period control changes mid-month (e.g., temporarily closed for reconciliation). - Concurrent Manager / Resource Issues
• The scheduled Create Accounting program may have completed, but the Post Journals sub-process could have errored out due to concurrent manager load, memory, or timeout.
• Look at the program log files for those runs — you may see “Post Journals request failed” messages. - Data Volume / Batch Size
• If those 20 days had unusually large transaction volumes, the posting step may have failed or been deferred.
• Sometimes journals are transferred but left unposted if the posting request exceeds limits. - Intermittent GL Setup Changes
• Check if any posting options or ledger setup changes were made in October (e.g., suspense account rules, journal approval settings).
• If approval was required for those journals, they would remain unposted until manually approved.
Re: Error to apply patch 38726236 (PTB) - Brazilian Portuguese
Thanks for the update. We have raised SR already, will mention this Bug to ease the diagnostics.
Re: Error to apply patch 38726236 (PTB) - Brazilian Portuguese
Hi all,
Oracle has opened a new BUG 38776090 to "Oracle EBS Applications Translation" to review the issue related to the "Translated Patch: 38726236:R12.CLL.E" install error, but a solution has not been provided yet, only a workaround until a new patch is finalized:
"The steps are as follows:
01 - Finalize the application of the patch that is presenting the problem with the option `adop flags=autoskip`. If you are unable to finalize the patch application, you can use the options below:
`options=forceapply` `restart=yes` `flags=autoskip` `abandon=no`
02 - Copy the original FORMS (US) to the problematic translation (PTB or ESA)
-- PTB
cp $CLL_TOP/forms/US/CLLRIIOI.fmx $CLL_TOP/forms/PTB/CLLRIIOI.fmx
-- ESA (If using Latin America)
cp $CLL_TOP/forms/US/CLLRIIOI.fmx $CLL_TOP/forms/ESA/CLLRIIOI.fmx
Through this process, you will be able to use the English FORMS in The language presented a translation problem. I emphasize that this is a temporary solution.
03 - The bug fix will be through a new patch to resolve the problem with FORMS CLLRIIOI.fmx, so we will notify you when the new patch is released for application."
Re: Where to find the Assets associated with CSI?
I still find it incomprehensible that a software company as big as Oracle thought delivering this product could be done with no thought to how its functionality was used. I have worked with/for Oracle for the last 30 years and never have I seen them be so cavalier with a migration. No working with customer groups, no testing, little to no communication. It is like you told AI, give us a support site and didn't give it any requirements.
You have only added fuel to the ABO movement at my company. I am about to join them. This product is as close to unusable as anything I have ever seen. Bring back the old MOS until you figure out how to do a migration of a known, trusted, and useful product.
Re: Unable to access Readme from Patchset 38308115: PEOPLESOFT FSCM UPDATE IMAGE 9.2.055 - NATIVE OS
Hi, please find attached readme file and bug fixes list for Image #55 for your review.
Thank you.
Regards,
Georgeta Moraru
