Problem with Planned Start Date of Batch Created by Releasing a Planned Order When Changing the Implement Date
Last updated on MAY 05, 2017
Applies to:Oracle Process Manufacturing Process Planning - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version, APS Feedback
Problem with Planned Start Date of batch created by releasing a Planned Order when changing the Implement Date.
Customer has a planned order with a Suggested Start Date and Suggested Due Date of 07-MAY-2017 00:00:00. If they simply release the order and create a batch, the batch has a planned completion of 07-MAY-2017 00:00:00 and a planned start date a few seconds earlier, which is correct and matches what happens if they create a batch manually (their total resource duration is only 3 seconds). The problem is if they change the Implement Date when releasing the order. When they change the Implement Date to 24-MAY-2017 00:00:00, the batch is created with a planned completion of 24-MAY-2017 00:00:00, but the planned start date is 07-MAY-2017 00:00:00, even though the total resource duration is still 3 seconds. Instead of backscheduling to calculate the planned start date like normal, it seems like something is updating the planned start date to equal the Suggested Start Date. The first step still starts only 3 seconds before the planned completion of the batch.
Expect the planned start date to still be calculated based on the duration of the batch.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms