Skip to main content

Hi all,

We have PM Actions scheduled for the entire year. The maintenance team is using the Maintenance Plan Analysis screen to find these actions by searching with Group ID and “Remaining to Due < 10.”

In the attached screenshots, you’ll see that the Due Date is 5/27/2025, which is today’s date. So, the Remaining to Due should be 0. However, it's currently showing as 4.

In our test environment, the Remaining to Due is showing correctly. I’ve already checked the scheduled database tasks and background jobs, and nothing appears to have failed.

I was able to fix an individual record by going to the PM Action > right-click > Regenerate Plan (see screenshots below). My question is: where or how is this regeneration typically automated in the system? I haven’t found anything in IFS Help, and I can't identify any configuration differences that would explain why it's working correctly in the test environment but not in production.

We’re currently running Apps 10, Update 20. Let me know if you need any other information.

 

 

Hi,

There is a batch schedule method “PM_ACTION_CALENDAR_PLAN_API.UPDATE_OVERDUE_VALUES ” available for this. You can create a batch schedule using this method with the required interval and it will update overdue values as well as remaining to due for all PMs.

The reason may be the schedule task is not available/not active in the production environment.

We are experiencing this issue also but seeing an error in the background job stating ‘ORA-01476: divisor is equal to zero’

 

Any ideas?

 

We are experiencing this issue also but seeing an error in the background job stating ‘ORA-01476: divisor is equal to zero’

 

Any ideas?

 

Hi ​@lisa.gilesAB , I was facing the same problem and IFS did a fix in cloud and our local support applied in our Env v10 UPD26.
Raise a case and ask them to apply in yours.

Hope it helps.
The lines commented are the problem.

 

Reply


Terms & ConditionsCookie settings