Best Of
Re: Errors in transactions pertaining to Fixed assets
You can remove the assets with a negative addition that uses the same Transaction Date. It will revers the ADD and all depreciation postings (unless the asset has subsequent transactions).
You can dispose the asset using the original Transaction Date. That will also remove that asset's depreciation.
Unposting journals made by AM is generally a bad idea. We haven't found it to be a good approach in 28+ years.
Re: Allow adjustment to paid invoices feature at OU level, Is it possible to allow for few users?
Hi @User_L2IG5,
Since it is at the OU level, a common approach is to enable it only when adjustments to paid invoices are needed, make the adjustments, then disable it again after, to avoid accidents.
If you really need to allow it for some responsibilities but not for others, you could consider a personalization that changes the list of values on the invoice form so that only unpaid invoices are available. The personalization would be applied to all but the responsibility that you want to use to modify paid invoices. You'd have to test thoroughly to ensure there's no way for a user to accidentally get to a paid invoice.
Re: Tracking User Changes in F4095 (DMAAI)
Hi,
Currently, there is no audit columns such as User ID (USER), Program ID (PID), Date Updated (UPMJ) etc... in the Distribution/Manufacturing - AAI Values(F4095) table to track any Add/Changes records. For this, below enhancement request has been entered in the system.
E1: 42: Add Audit Fields to the Distribution/Manufacturing - AAI Values (F4095) Table (Doc ID 2976930.1)
Also, as Pilar mentioned, you can enabled using out own internal auditing tool CFR11. You can refer to below KM Documents which might be able to help you :
E1: CFR11: Auditing Tool (21CFR Part 11) Guides and MTRs(Doc ID 636234.1)
E1: CFR11: Auditing EnterpriseOne Table Changes (Doc ID 660722.1)
E1: CFR11: Troubleshooting Issues With EnterpriseOne Auditing Tool (21CFR Part 11)(Doc ID 1256916.1)
E1: CFR11: Frequently Asked Questions on EnterpriseOne Auditing Tool (21CFR Part 11)(Doc ID 1087604.1)
If you need more details on that you would need to open a service request for the product area Tools and Technology > DB OS > Auditing Tool.
Regards,
Ankur Patel
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: 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



