Pierre Smits closed OFBIZ-8243.
Resolution: Not A Problem
This was a dud. Due to a misconfiguration of a TechDataCalendar record the end
date of a particular task was calculated wrong. Leading to an equally wrong end
date for the production run.
*In depth route cause analysis*
The schema task (e.g.
can be associated with a fixed asset of type GROUP_EQUIPMENT. This kind of
fixed assets can be associated with a TechDataCalendar through the field
calendarId. The associated TechDataCalendar is associated with a
TechDataCalendarWeek record (see
If there is no association between the fixed asset (associated with the schema
task) and a TechDataCalendar then TechDataCalendar = DEFAULT will be used in
the techDataCalendarServices. This TechDataCalendar DEFAULT is associated with
TechDataCalendarWeek DEFAULT, which has a capacity of 28,800,000/day
In my scenario a 24-7 TechDataCalendar was associated to TechDataCalendarWeek
DEFAULT, instead of a 24.-7 TechDataCalendarWeek (capacity 86,400,000 per day,
7 days per week).
> End date calculation of workefforts is wrong
> Key: OFBIZ-8243
> URL: https://issues.apache.org/jira/browse/OFBIZ-8243
> Project: OFBiz
> Issue Type: Bug
> Components: manufacturing, workeffort
> Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
> Environment: This happens in following setups:
> R15.12 against MySQL
> R15.12 against PostgreSQL
> It does not happen in setup:
> R15.12 against Derby.
> Reporter: Pierre Smits
> Assignee: Pierre Smits
> Labels: productionrun, routing
> Attachments: Screen Shot 2016-09-14 at 08.33.10.png
> When a new production run is generated based on a production schema with
> tasks, the process takes the tasks of the schema (in the designated order)
> and calculate the start and end date for each task (based on the provided
> start date of the production run.
> This process doesn't work properly as tasks with a total throughput time
> (setup + run time) more than 1 day leads to wrong results.
This message was sent by Atlassian JIRA