Firm Work Orders Operation Dates Could Not Be Changed (Doc ID 2143057.1)

Last updated on AUGUST 11, 2022

Applies to:

Symptoms

ACTUAL BEHAVIOR

Changing the schedule dates for an operation on a work order does trigger the bottom-up scheduling; however, the dates are not getting get updated with the new date/time.
This issue does not occur in Forms, it updates the date/time properly in Forms.


EXPECTED BEHAVIOR

Firm Work Orders Operation Dates should be changed as expected.


STEPS

Steps taken in Self Service:
1. Responsibility: Maintenance Super User (does not work properly).
2. Create a WO in self-service. The Firm flag is set to No. I have two operation steps on it, an hour each.
3. The WO saves with a duration of 1 hour, both resources working the same hour, which is correct Oracle functionality.
4. I want to have OP1 do their work before OP2. So I check the firm flag, go to OP2 and change the start and end time, moving them back by an hour.
5. I save the WO and receive the message System triggered Bottom-Up Scheduling process for the invalid dates entered, which is fine. It should still have accepted the times I entered above, but it puts them back to the original time.

Steps taken in Forms (works properly):
1. Responsibility: Enterprise Asset Management.
2. Create a WO in Forms, just as I did above. The Firm flag is set to No. I have two operation steps on it, an hour each.
3. I want to have OP1 do their work before OP2. So I check the firm flag, go to OP2 and change the start and end time, moving them back by an hour.
4. I save the WO and receive the message System triggered Bottom-Up Scheduling process for the invalid dates entered, which is fine.
5. The WO is saved with the time changes I made, with a Duration of 2 hrs now and scheduled end date extended out an hour, just as I wanted.

Cause

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