Batch Close Variance Is Not Being Applied To the Expected Co-Product’s Cost
Last updated on JUNE 21, 2017
Applies to:Oracle Process Manufacturing Financials - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version, Actual Cost Process
Batch Close Variance is not being applied to correct period and Co-Product’s Cost
Batch close variance should be applied to the newly added product's cost, not to the previous product that did not have transactions in the new period
The issue can be reproduced at will with the following steps:
In our PMAC environment, Org/Item Level $ reconciliation differences at month end does not tie to the BCV
1) In period1 a batch is created, released and product1 is transacted (WIP Completion), and then
2) In period2, co-product (line2) product2 is added and is transacted (WIP Completion) and the batch is closed with a BCV
The BCV is then applied to Product1’s actual cost transactions in Period2 where as it should be applied to product2's cost in period2, when the batch was closed.
The logic for selecting the item to apply all of the BCV to its cost appears to be the product transacted first and should be the product transacted last.
Why is this occurring and what can we do to change it?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms