PM Forecast Is Ignoring Base Interval If Generated PM Work Order Moved/Shifted To An Earlier Date. (Doc ID 2988983.1)

Last updated on DECEMBER 01, 2023

Applies to:

Oracle Enterprise Asset Management - Version 12.2.10 and later
Information in this document applies to any platform.

Goal

The Preventive Maintenance (PM) forecast is not filling in the gap crated by shifting dates for a PM work order (WO) earlier by 1 interval.

Example:

Weekly (7 days interval) PM generates WO1 on 10th and WO2 on 17th.
Released-firmed and shifted WO1 to 3rd.

Next PM forecast is not suggesting any WO to fill in the gap for 10th. The WO2 will remain on 17th and WO1 on 3rd but the gap is 2 weeks wide.

Solution

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Goal

Solution

References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

PM Forecast Is Ignoring Base Interval If Generated PM Work Order Moved/Shifted To An Earlier Date. (Doc ID 2988983.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!