Best Of
Re: View Billing Events
Hi,
There are no self-service pages for reviewing billing events. This must be done through the forms application.
Regards,
Shane
Re: Oracle b2b 14c does not support EDI, EDIFACT
Hello.
But the support of version 12.2.1.4 will not end at the end of 2026?
Re: What is the best practice to remove old PA Exceptions for Receipt Accruals on Closed projects
Hi Reina,
If PA_ADDITION_FLAG is N then these transactions are eligible for project transfer,
If project Organization is in closed status, these transactions cannot be interfaced to PA.
Please log service request with oracle support to check the possible workaround to remove the exceptions from report.
Regards,
Nagarjuna D.
Re: SYSAUX - AUTO_STATS_ADVISOR_TASK expired tasks not being purged
@User_7A4U6 - I am noticing the exact same behavior. Since around the same time frame, our SYSAUX has been growing. Like you I tracked it down to SM/ADVISOR and eventually AUTO_STATS_ADVISOR_TASK - when I check my EXECUTION_DAYS_TO_EXPIRE parameter, it's set to 30. But when I check DBA_ADVISOR_EXECUTIONS table, the earliest entry in there goes back to May 5, 2025, even though it's September.
When I saw your post and saw that yours went back to late April, that seemed too similar to be a coincidence.
Let me ask you - when did you apply the April 2025 CPU (19.27, I believe)?
Because of internal delays, I didn't apply the patch until June 4. Notice how May 5 and June 4 are 30 days apart.
Any chance you installed your April 2025 CPU on or around May 24th?
My theory is something in the April 2025 broke the purging job, because ever since I installed it, my old AUTO_STATS_ADVISOR_TASKS aren't being purged. That's why SYSAUX keeps growing.
Quick question - are you running on Windows or Linux?
Have you figured out a reliable workaround yet? Or did you open an SR with Oracle? If you haven't, I probably will.
Hopefully we can get to the bottom of this. I'm just curious what our environments have in common, as I haven't seen this issue widely reported so it could be something unique to our installations. I searched MOS and found instances of issues like this with some old 12.2 installations as well as installations before 19.21 (with regards to PDBs), but nothing more recent.
Thanks!
Re: python3-oracledb, libraries are missing
It's a bug, thanks for reporting.
You can safely rollback to previous version ( 3.1.1-1.el9 ), fixed 3.3.0-1.0.1.el9 should be issues today/tomorrow.
Thanks for reporting once again!
Re: Error: Could not find or load main class LoadDTDToClob
Reference the following:
Error Encountered In Generating PO Via XML Gateway - 'ORA-31011: XML parsing failed ORA-19213 error occurred in XML processing at line 1 LPX-00103. Warning document structure does not match DTD.' (Doc ID 2704939.1)
I will request this be posted to the Purchasing community since it is for PROCESS_PO_007
Thanks
Bobbi
Re: How to Make Supplier code Inactive in JDE , We tried to change the Search Type From V to "VO" but It
Hi,
I have an idea. In the supplier master, change the item restrictions field to "I" (EDF2) and do not add any items to the item restriction list. This means that only the items on the list can be purchased from the supplier. Since there are no items on the list, the system will always show an error when an order is entered.
Pilar
Re: Is there any way to avoid or minimize the rounding difference in Sales Order of foreign currency ?
Hello,
This issue would be best handled by a service request. That would give us the opportunity to review your entire setup, logs and the current results you are receiving.
However, you may check the bellow documents:
E1: 42: Rounding- Extended Foreign Amount is Recalculated (Doc ID 2242213.1)
E1:42: Inconsistent Extended Price Rounding with Decimals Upon Entering & Re-entering in Sales Order (Doc ID 2514849.1)
Thank you,
Laura
