My Oracle Support Banner

Average Cost Job Serialized Completion Creates Final Job Variances in MES (Doc ID 1611992.1)

Last updated on FEBRUARY 11, 2019

Applies to:

Oracle Cost Management - Version 12.1.3 and later
Information in this document applies to any platform.


On : 12.1.3 version, WIP Costing

 backflush of a lot controlled component, in a serial-tracked job where the transaction is Flagged as Final Completion, is being costed after the wip completion transaction.
This is obviously incorrect, and will give rise to Job Variances at job close

no job close variance

The issue can be reproduced at will with the following steps:
1. average costing org, project job for serial tracked assembly.
This was first job for this assembly for this project/project cost group.
All components issued (2 Push components).
No existing costs for assembly in project cost group.
Job qty was for 19 off.
19 individual WIP Completion transactions performed, 1 for each serial number using MES (assembly pull transaction of single component automatically performed by each transaction).

The job was substantially over relieved, with one transaction being significantly overcosted and several transactions generating Final Completion Variances.
The project cost type for the assembly now has a cost that overvalues the stock on hand

If one of the completion transactions was accidentally flagged as 'Final Completion' before the actual last transaction, I would expect that transaction to be 'overvalued' and the subsequent transactions at zero cost, so that the overall value of the completion transactions equals the cost incurred, so that the stock valuation is correct.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.