Best Of
Re: Dealinc long-running
This should be called once for deal_Id, Deal_detail_Id and reporting period; however currently it's being called at deal_id, deal_detail_id, item, loc and reporting period level in 19.0.1 version that is why you see so many executions. This requires a fix to call it only once for a deal_id, deal_detail_id and reporting period level to avoid unnecessary loops.
Re: How to create a compliance standard rule to check the software version on a windows host
Hi Karl,
You can use the Configuration Extensions.
- Create a Configuration Extension with this Command you want to execute.
- Create an Agent Side Rule and select this Configuration Extension which you have created in the step 1.
- Then add this Rule to a Standard (OR) Create a Standard and Assign this Rule.
- Deploy this CS to the Host Targets.
Best Regards,
Venkat
Re: Why is my weighted LRT not working?
Yes. Issue resolved. Much thanks for the help.
Re: SBC in AWS - cannot find Oracle Linux AMI
Hi Monica and Shilpi,
Thanks a lot for the details. I will go through it and try it out.
Regards,
Rajith.
Rajith
Re: support contract view
Hi @User_CYT2V ,
You should be able to select 'create service request' and raise an Oracle SR selecting the specific hardware (if you type "hardware" in which product or service the list will appear below)
and you can then ask to raise an SR. It will then ask you for the serial number:
Hopefully helps.
Kind Regards,
Rob
Re: GL Issue - sending transactions for check reversal/ reissue
Hello User,
What you’re seeing is a known/expected edge case in NA Payroll: when you turn on GL posting for a deduction midstream, later reversals/reissues of older checks can try to create offset (reversal) accounting lines for items that never had an original line sent to PSFIN—and that can cause the GL process (Distribute Actuals / CA Actuals) to error or go out of balance depending on your configuration.
Below are approaches we’ve most often seen enterprises use to avoid this going forward (without doing recurring SQL surgery).
Preferred: create a new deduction code for “post-to-GL” going forward
Instead of changing the existing deduction’s “Suppress Posting to GL” setting, create a new deduction code (or clone) effective 2026 and map it going forward.
Why it helps
- Old checks/reversals continue to reference the old code that never posted to GL.
- New checks use the new code that posts to GL.
- Reversals/reissues of old checks won’t attempt to reverse a GL line that never existed, because that old code still doesn’t post.
Tradeoffs
- Two deduction codes to manage/report on (you can mitigate with mapping/rollups in reporting).
- Requires coordination with Benefits/Retro/General Deduction processing.
This is the cleanest “policy + config” solution we’ve seen for exactly your scenario.
Regards,
Asif M - Oracle.
Re: Missing panel for updated KB articles, bugs, alerts, new issues
+1 for this request. I'd like to see the capability to see recently-updated articles on my selected software. The News section does not address this.
Jason M.
Re: Inquiry Regarding OCOM Account Password Reset Command
Hello.
Thanks to you, I’ve sorted it out.
I didn’t realise you could remove the password policy...
Thank you.
How can we Print or Download knowledge documents
Are other people able to do this. Will this ability be returned in the near future?