The status of the WO W00002954 production order cannot be changed because it has related transactions that are not released.

@dtatum - do you have any clock entries that are NOT approved?

We do not have any employees set up in our system to clock into jobs/operations. Just to be sure I check and there are no records of any clock entries in our system.

This is the additional detail from the trace on trying to close the order
 

Error: At least one item has not been processed.

   at PX.Objects.AM.ProductionStatus.SetStatusTranScope(List`1 productionItemList, String newStatusID, FinancialPeriod financialPeriod, Boolean isMassProcese, Boolean checkUnreleasedTrans)
   at PX.Objects.AM.CloseOrderProcess.ReleaseOrder(List`1 list, Boolean isMassProcess, FinancialPeriod financialPeriod)
   at PX.Objects.AM.CloseOrderProcess.CloseOrders(List`1 list, Boolean isMassProcess, FinancialPeriod financialPeriod)
   at PX.Data.PXProcessingBase`1.<>c__DisplayClass85_0.g__ProcessList|0(List`1 list, PXProcessingMessagesCollection`1 perrowmessage)
   at PX.Data.PXLongOperation.<>c__DisplayClass18_0.b__0()

We have noticed the specific Move batch that Acumatica is saying is unreleased had most likely had been deleted. 

We typically backflush materials, so only a Move transaction is entered for both labor and materials - I have found that a number of people will go to enter and release a Move transaction only to discover that there are critical materials that prevent the transaction from being released

Since this transaction opens in a Pop-up window, most people close the window without realizing that the transaction remains open in a Balanced status. If you come back later to enter another Move transaction once critical materials are resolved, it won’t warn that there is another balanced Move transaction, nor does that transaction show on the events tab or anywhere else. 

If you want to modify the production order in anyway, including closing the order, you have to first delete the balanced transactions - but again they’re very hard to find from the production order itself. 

Take a look at AM000011 and see if you have any unreleased transactions associated with the production number 

@dtatum I’m late to the party on responses but this happens to us frequently.  You can more easily locate the production transactions that are not released in the “Transactions by Production Order” screen.  To see all unreleased, you can filter by the Released check box=False or filter by the specific production order.   

It is best to have a std business process to monitor balanced and on hold transactions to keep your system healthy.  Hope that helps.  

I’m trying to close out productions orders.  The following errors have been generated “ production order cannot be changed because the order has related clock entries that are not approved. You must approve or delete these clock entries first.”  I’m unable to find these clock entries. I have run the following command in the “Transactions by Production Order” screen released check box=False and no transactions are displayed.  Is there another screen that might be of assistance?

Hi @BOSullivan,

What was discovered by submitting this with Acumatica Support was a specific Move Batch had orphaned records in the database related to a potentially deleted move. The fix that was applied was a script ran by Acumatica Support and we have not had this issue since then.

Given your error it may or may not be the same issue due to your error stating “clocked entries that are not approved” whereas ours was related to unreleased transactions related to the WO. There wasn’t a screen accessible to me to identify this issue.

My recommendation would be to submit this to Acumatica Support.

Try checking Approve Clock Entries (AM516000) to see if you have any unapproved entries first

Nope all the approve clock entries have been approve and the error is still appearing.

Typically, this error occurs because a user starts a move or materials transaction, the record is saved but not released. Then the user navigates away from the screen, or goes back to the production order to make edits. The user then goes to make a new move or materials transaction, not realizing they already have one for this production order in a balanced state. The order is later completed/closed from these transactions but the balanced transactions are still linked to the order.

It is best to monitor all unreleased transactions regularly to mitigate this. You can use the unreleased documents dashboard to help with this. Or filter for ‘Balanced’ moves or materials etc. The same might go for clock entries.