[
https://issues.apache.org/jira/browse/OFBIZ-13261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17985234#comment-17985234
]
Yashwant Dhakad edited comment on OFBIZ-13261 at 6/23/25 6:31 AM:
------------------------------------------------------------------
*Steps to Reproduce and Code Fix Summary*
*Issue Description*
When an exception day is set in the calendar, it is not honored during
production run scheduling. As a result, the system calculates the completion
date incorrectly by including the exception day.
*Steps to Reproduce the Issue*
# *Calendar Setup*
- Created a calendar and set the default daily capacity to 8 hours.
- Marked 30 June as an exception day (non-working day).
!image-2025-06-23-11-54-47-490.png!
!image-2025-06-23-11-55-28-617.png!
# *Routing and Routing Task Configuration*
- Defined a routing and associated it with a routing task.
- Routing task includes:
- Setup time: 8 hours
- Run time: 8 hours
- Routing task is linked to a fixed asset, which in turn is assigned to the
above calendar.
!image-2025-06-23-11-55-56-255.png!
!image-2025-06-23-11-56-16-151.png!
!image-2025-06-23-11-56-27-740.png!
!image-2025-06-23-11-56-35-835.png!
# *Fixed Asset Association*
- Verified that the fixed asset is correctly associated with the calendar
containing the exception day.
!image-2025-06-23-11-56-49-284.png!
# *Production Run Creation*
- Created a production run for 4 quantity.
- Expected calculation:
- 1 day for setup (8 hrs)
- 4 days for run time (4 × 8 hrs)
- Excluding weekends (Saturday, Sunday) and the exception day (30 June,
Monday)
- Start Date: 27 June (Thursday)
- Expected Completion Date: 4 July (Thursday)
- Actual Completion Date (before fix): 3 July
!image-2025-06-23-12-00-50-164.png!
!image-2025-06-23-11-57-18-484.png!
*After Fix (Code Change)*
- The logic was updated to skip exception days during production scheduling.
- Now the system accurately excludes weekends and exception days in
calculating end date.
!image-2025-06-23-12-01-12-577.png!
✅ Final Result:
With the fix in place, the job now correctly completes on 4 July, as expected.
was (Author: yashwant.dhakad):
*Steps to Reproduce and Code Fix Summary*
*Issue Description*
When an exception day is set in the calendar, it is not honored during
production run scheduling. As a result, the system calculates the completion
date incorrectly by including the exception day.
*Steps to Reproduce the Issue*
# *Calendar Setup*
- Created a calendar and set the default daily capacity to 8 hours.
- Marked 30 June as an exception day (non-working day).
!image-2025-06-23-11-54-47-490.png!
!image-2025-06-23-11-55-28-617.png!
# *Routing and Routing Task Configuration*
- Defined a routing and associated it with a routing task.
- Routing task includes:
- Setup time: 8 hours
- Run time: 8 hours
- Routing task is linked to a fixed asset, which in turn is assigned to the
above calendar.
!image-2025-06-23-11-55-56-255.png!
!image-2025-06-23-11-56-16-151.png!
!image-2025-06-23-11-56-27-740.png!
!image-2025-06-23-11-56-35-835.png!
# *Fixed Asset Association*
- Verified that the fixed asset is correctly associated with the calendar
containing the exception day.
!image-2025-06-23-11-56-49-284.png!
# *Production Run Creation*
- Created a production run for 4 quantity.
- Expected calculation:
- 1 day for setup (8 hrs)
- 4 days for run time (4 × 8 hrs)
- Excluding weekends (Saturday, Sunday) and the exception day (30 June,
Monday)
- Start Date: 27 June (Thursday)
- Expected Completion Date: 4 July (Thursday)
- Actual Completion Date (before fix): 3 July
!image-2025-06-23-11-57-05-685.png!
!image-2025-06-23-11-57-18-484.png!
*After Fix (Code Change)*
- The logic was updated to skip exception days during production scheduling.
- Now the system accurately excludes weekends and exception days in calculating
end date.
!image-2025-06-23-11-57-28-311.png!
✅ Final Result:
With the fix in place, the job now correctly completes on 4 July, as expected.
> Calendar Exception Days Ignored in Production Run End Date Calculation.
> -----------------------------------------------------------------------
>
> Key: OFBIZ-13261
> URL: https://issues.apache.org/jira/browse/OFBIZ-13261
> Project: OFBiz
> Issue Type: Improvement
> Components: manufacturing
> Affects Versions: Upcoming Branch
> Reporter: Yashwant Dhakad
> Assignee: Yashwant Dhakad
> Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: image-2025-06-23-11-54-47-490.png,
> image-2025-06-23-11-55-28-617.png, image-2025-06-23-11-55-56-255.png,
> image-2025-06-23-11-56-16-151.png, image-2025-06-23-11-56-27-740.png,
> image-2025-06-23-11-56-35-835.png, image-2025-06-23-11-56-49-284.png,
> image-2025-06-23-11-57-05-685.png, image-2025-06-23-11-57-18-484.png,
> image-2025-06-23-11-57-28-311.png, image-2025-06-23-11-59-45-318.png,
> image-2025-06-23-12-00-14-107.png, image-2025-06-23-12-00-50-164.png,
> image-2025-06-23-12-01-12-577.png
>
>
> Within the *Manufacturing → Calendar* tab, users can define non-working days
> using the *"Add Calendar Exception Day"* form. However, even after correctly
> setting up exception days, the system fails to consider them when calculating
> the end date of a production run.
> As a result, the projected end date does not align with real-world schedules,
> leading to inaccuracies in planning and execution.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
