Forward and Backward Scheduling of Work Order is not Working as Expected Post 20D Update
(Doc ID 2733003.1)
Last updated on DECEMBER 01, 2020
Applies to:Oracle Fusion Manufacturing Cloud Service - Version 22.214.171.124.0 and later
Oracle Maintenance Cloud Service - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
When scheduling work orders, the start or completion dates can be incorrectly scheduled. This problem occurs when the work orders have shift based resources and the plant timezone in Manage Inventory Organization Parameters uses a non-zero offset(offset is the difference between local time and UTC). The problem is more visible when there are more shift-based resources in the work order and if the plant time zone offset is bigger.
Steps to Reproduce
1. Plant timezone in Manage Inventory Organization Parameters should be set to a time zone with non-zero offset.
2. Work Order should have operations with multiple shift based resources.
3. Navigate to Supply Chain management -> Work Execution ->Manage Work Orders and search for any work order.
4. Open Work Order and go to General Information Tab.
5. Select a new date for start date and then click on Save.
6. The work order is re-scheduled, but the entered start date is changed to a different date.
The customers who received the quarterly update to 20D in November or December 2020 are potentially affected by this known issue.
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