Solved

Actual Start Date and Actual End Date on Operations are incorrect

  • 1 November 2023
  • 4 replies
  • 110 views

Userlevel 4
Badge

Trying to figure out if this is a bug, a feature or inherent in the design of the manufacturing module:

On the Production order’s operations, there are four fields related to start and end dates for the operation:

  1. Start Date
  2. End Date
  3. Actual Start Date
  4. Actual End Date

The first two always show the start and end dates of the production order.

The other two with the word  “Actual” I would assume would get set as follows:

  1. When the first transaction for the operation is performed, the Actual Start Date is set to the date on the transaction
  2. When a transaction is performed that completes the qty to produce and sets the operation status to completed, the Actual End Date is set to the date of the transaction

In other words, these fields are logically set on the first and last operations of the production order.

However this is not what happens. On a clean install of 2023R2 Update 1, this is the behavior:

 

When a labor transaction is released, regardless of the date on the labor transaction, the Actual Start Date is always set to the current day:

 

Likewise, if the labor transaction completes the operation, the Actual End Date is always set to the current day, regardless of the date on the labor transaction:

 

The strangest behavior of all is this: When subsequent labor transactions are completed, the end date of all prior labor transactions is set to the current date.
(for the sake of illustration, I manually updated the Actual Start Date and Actual End Date to the dates that were on the labor transactions)

Before releasing operation 0020

 

After completing Operation 0020

 

Looking at the code ProductionTransactionHelper.cs reveals this:

This is inside a foreach loop for all the production order operations. Since this indiscriminately sets this to the current date, this is why we have this result.

 

And in ProdMaintBase.cs, we have this:

This is called for each operation and again, it is setting the dates to the current date which gives the result we see.

 

Why is this being set this way? Actual should mean...Actual…
The only way to get accurate production reporting data on an operation level as far as I know, is to join to the labor transactions and get the actual dates completed. This is messy because if you have multiple transactions for an operation, you have to group by and select last and first transactions etc.

icon

Best answer by Freeman Helmuth 23 February 2024, 17:09

View original

4 replies

Userlevel 4
Badge

This was confirmed as a bug in the manufacturing module. It is tracked as case number 336173 and now shows as development in progress.

Userlevel 7
Badge

Hi @Freeman Helmuth were you able to find a solution? Thank you!

Userlevel 4
Badge

@andrestamour43

You say that actual start and end represent the date the that operation status changed. However, if a labor transaction is released for a date prior to today, in actuality, that prior date is the date the status of the operation changed. What is happening now is that the system is recording the date that the activity was reported in the system(which is when the Release button is clicked) instead of the date the activity physically occurred(which is the date on the labor transaction)

 

And yes, it does reset the completion dates of all prior operations. I’ll open a ticket on this.

Userlevel 5
Badge +1

@Freeman Helmuth - Great questions! 

I think what you are expecting these fields to display makes sense. But with that said the field (so far) has represented the date the operation status changed.

So Actual Start Date corresponds to the date the operation status change from Released to In-Process/Completed. 

Actual End Date - by that same logic - would correspond to the date the operation changed to Completed status. 

If I am understanding the second part of the post the dates are being filled in during the any release of a labor transaction regardless if it is for the given operation? That sounds like a bug and I would recommend reaching out to your partner to log a support request. 

Are you looking to develop a KPI / report comparing planned start and end dates of an operation against actual dates or something else? I’m asking because I would be curious to know if anyone else has created something similar to your end goal. 

Hope this helps! 

Reply


About Acumatica ERP system
Acumatica Cloud ERP provides the best business management solution for transforming your company to thrive in the new digital economy. Built on a future-proof platform with open architecture for rapid integrations, scalability, and ease of use, Acumatica delivers unparalleled value to small and midmarket organizations. Connected Business. Delivered.
© 2008 — 2024  Acumatica, Inc. All rights reserved