So, you’re upgrading and wondering if your discrete work orders are in place and ready for the upgrade?
There are some best practices that you should consider. First, you need to process open, partially completed work orders that have pending accounting activity not yet reported. By generating and posting these transactions, you’ll clear the unaccounted fields that the Work in Process program uses to generate manufacturing journal entries. This will result in a ‘clean’ cutover in Manufacturing Accounting. What’s important is that you’ll avoid inconsistencies in the Work Order Production File which values are used by the Work Order Variances program to generate the IV transactions.
This same importance pertains to all work order related files. Always, run programs in PROOF mode first and then in FINAL mode prior to upgrading to troubleshoot and correct any possible errors.
For fully completed work orders, generate manufacturing variances with P31804 as this is the last step to fully ‘close’ a Work Order and should be run once in final mode.
Finally, post all manufacturing transactions to the General Ledger. Run all active batches through to completion and verify the posting edit reports are free of errors. Then, use the Item Ledger & G/L Integrity report to confirm that no discrepancies exist between the Item Ledger (Cardex) and G/L manufacturing entries.
Remember, you can access key upgrade information via the UPGRADE section of the Information Center page for the Release that you are upgrading to. For example, if you are upgrading to A9.3.1, check out: Information Center: Upgrading to JD Edwards World Release A9.3/A9.3.1 (Doc ID 1447731.2) for documents that are specific to a A9.3.1 release upgrade.
Keep your eye out on My Oracle Support for new knowledge documents regarding additional best practices for discrete work orders and upgrading. In the meantime, post questions on My Oracle Support Community or open a Service Request!