Skip to main content
Solved

Any issue disabling "Scheduling Optimization Triggers" if we are not using PSO


paul harland
Superhero (Employee)
Forum|alt.badge.img+24

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?

Best answer by adrianm

For ​@paul harland and anybody else reading this, IFS have acknowledged this is a bug and it will be fixed in 24R2 SU3. 

View original

adrianm
Do Gooder (Partner)
Forum|alt.badge.img+4
  • Do Gooder (Partner)
  • January 17, 2025

Hi ​@paul harland ,

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.


paul harland
Superhero (Employee)
Forum|alt.badge.img+24

@adrianm 

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


adrianm
Do Gooder (Partner)
Forum|alt.badge.img+4
  • Do Gooder (Partner)
  • January 17, 2025

@paul harland 

I’m firing up a 23R2 Build Place environment so I can do some troubleshooting and comparisons first but will keep you posted.

 


paul harland
Superhero (Employee)
Forum|alt.badge.img+24

good idea - thanks


adrianm
Do Gooder (Partner)
Forum|alt.badge.img+4
  • Do Gooder (Partner)
  • January 17, 2025

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!


paul harland
Superhero (Employee)
Forum|alt.badge.img+24

Hi ​@adrianm 

Thanks for working through that to confirm the issue.


paul harland
Superhero (Employee)
Forum|alt.badge.img+24

Can you share the case number with me please when you have it


adrianm
Do Gooder (Partner)
Forum|alt.badge.img+4
  • Do Gooder (Partner)
  • January 20, 2025

@paul harland

 

I would DM you with it but you need to be following me to do that. Can you add me?


paul harland
Superhero (Employee)
Forum|alt.badge.img+24

done


adrianm
Do Gooder (Partner)
Forum|alt.badge.img+4
  • Do Gooder (Partner)
  • February 3, 2025

For ​@paul harland and anybody else reading this, IFS have acknowledged this is a bug and it will be fixed in 24R2 SU3. 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings