I want to disable my Scheduling Optimization Triggers relating to Pso_Service_Integration because they cause a failure in BPA Workflow (there is an implicit commit in the code).
Assuming the customer uses Dispatch Console but not PSO, are there any issues here?
Hi
Did you just get this issue after upgrading to 24R1 or 24R2? The current project I am on has had PSO enabled for about a year with no issues but the Commit has reared its head since the latest upgrade from 23R2 to 24R2. I am about to raise a case with IFS as the Commit is affecting multiple BPAs for Serial Objects, Work Tasks etc. so just wanted to see whether your circumstances are similar.
It’s hard to be sure because i wasn’t involved with the project prior to their upgrade to 24r1. The customer applied the upgrade and then copied Prod over UAT, and then i saw this issue. So it wasn’t clear whether the Commit issue was present in 23r2 but the triggers were switched off - or if the upgrade introduced the commit issue
Hope that makes sense
Yes please raise the case as this will be a big pain
I’m firing up a 23R2 Build Place environment so I can do some troubleshooting and comparisons first but will keep you posted.
good idea - thanks
The Oracle Scheduling_Dataset_Flag_API. Set_Update_Now_Flag_ method was changed in 24Rx and includes functionality to lock a record which includes the Commit.
I am no expert on PSO, but if you are in the position to disable the PSO triggers, go ahead.
The project I am on uses PSO and we have many affected BPAs as it’s work task and serial object centric so the IFS Case is going in!
Hi
Thanks for working through that to confirm the issue.
Can you share the case number with me please when you have it
I would DM you with it but you need to be following me to do that. Can you add me?
done
For
After applying 24R2 SU3 this now seems to be resolved.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.