PM Calendar generation fails with ORA-01841 (invalid year) once a PM Plan Horizon's Object Property Value (a hardcoded year like '2024') falls behind — the calculation subtracts the current date from a fixed end-of-year date derived from that year, and it eventually needs bumping forward. Is there a way to make this stay current automatically instead of needing a periodic manual update?

All FAQ questions / Asset and maintenance management

Answer

No — the PM_PLAN_HORIZON Object Property Value has to be a literal 4-digit year (it can't hold an expression or formula), and there's no out-of-the-box mechanism to auto-update it. This is one of a handful of IFS configuration values that are effectively 'set it and remember to bump it' — periodically updating the year manually (or via your own small scheduled task, the same pattern used for other manually-bumped date/year values) is the only way to keep PM Calendar generation from eventually failing again.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Asset and maintenance management questions