FA:SCM:CST: Reverse a Closed Work Order But Transactions Are Hitting The Work Order Close Expense Event After Adjustment
(Doc ID 2771839.1)
Last updated on MAY 06, 2021
Applies to:Oracle Fusion Manufacturing Cloud Service - Version 11.13.21.01.0 and later
Oracle Fusion Cost Management Cloud Service - Version 11.13.21.01.0 and later
Information in this document applies to any platform.
When the user reopens a close work order to perform a transaction and closes the work order again it creates an entry into the WO close expense event rather than hitting the WO Job Variance event.
Why is that happening?
Currently when you reverse a work order in it's entirety after it has already been costed, the work order does not reverse the previous variances that were generated on the first work order close.
It instead places the original variance amounts into a general expense bucket. This causes challenges as even though your overall P&L expense total is correct, the individual variance buckets are not reversed.
This adds additional layers of complexity when trying to manage and report on these variance buckets.
1. User reopens a closed work order to reverse all the transactions including the WIP Material Issue and WIP Product Completion.
2. User then closes the work order again.
3. Entries are created into the WO close expense event rather than hitting the WO Job Variance event.
Expectation is that the original variance would be reversed after closing the work order again and will be hitting the WO Job Variance event.
Instead, it creates an entry into the WO Job Close Expense event.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document