Minimum Version Required: 25.01
Pre-Conditions
Verified Production Orders are locked to prevent Users from making changes to them that would impact costing and financials. In the event that a Verified Production Order needs to be reopened:
A Production Order has been completed and Verified. (If a Production Order is in completed status, see "Reopen Completed Production Order" Help Resource)
A User with the UnVerify permission will need to follow this process
Steps
Step 1:
Go to Companies Table
Set AP Close date to the day before the date on the Production Order that needs to be corrected
Step 2:
Go to Production Orders table
Filter to the Production Order that needs to be rolled back
Select Subtables -> Purchases
On the Subtabled Purchase, click the hyperlink for the Shipment associated with that Purchase
Select the Un-Verify link in the ReceiveTime field
Once these steps are completed, the Production Order will be in Completed Status. Correct the Production Order as needed by following "Reopen Completed Production Order" Help Resource.
Step 3:
Re-Verify the Production Order using Production Confirmation Costing dashboard
Re-Close AP to current date using the End of Day dashboard
Fields And Definitions
Verified Production Orders - A Production Order that has been completed, with costs verified and Journal Entries made against it. Correcting these means Journal Entries also have to be corrected (opening up days to re-record AP)
Best Practices
Double Check Production Orders before Verifying them to prevent having to roll back PdO's
Opening Accounts Payable in this process is risky. It allows users to back-date transactional documents to the period that was opened, and will re-calculate any transactions that were unlocked. When rolling back days, have a game plan, fix the records that need fixing and re-close as soon as possible to reduce the risk of Users unexpectedly back-dating transactions for periods that have been closed
If correcting costing for one PdO, make sure any others that may have been affected will also be corrected (Example: if WIP is incorrectly costed, all Packaging Runs that packaged that WIP will also be costed incorrectly)