Shulou(Shulou.com)06/03 Report--

Unexpected Variation In Item Unit Cost During "WIP Completion Return" (document ID 1603855.1)

In this Document

Symptoms

Cause

Solution

Applies to:Oracle Cost Management-Version 12.1.3.3 and later

Information in this document applies to any platform.

Symptoms

On: 12.1.3 version, Other Inventory Issues

ACTUAL BEHAVIOR

-

(Finished Good) Item was Manufactured through a Discrete job "F1309056". This job was completed at a unit cost of "229.42310" for 100Quantity.

Later on "user" did a "WIP Completion Return" of 100Quantity for the same job, this time system picked unit cost "22942.31000" for return transaction.

This was a huge unexpected variance...

Cause

The cause of this issue:

When we calculate return txn value, the formula is like below.

Relieved_matl_completion_value * return_qty / prior_completion_qty

Then cst_comp_snapshot.prior_completion_quantity was zero when processing assembly return.

The issue was clarified in details with the same scenario in

Bug 9502821-WRONG VALUE IN ACCOUNTING OF WIP COMPLETION RETURN TRANSACTION

Solution

Data fix:

=

There is no way to recost already costed txns. And, now the assembly item cost is wrong after the return txn, it became 0. So, CT should do average cost update for that item to make it correct. And, for already

Happened wrong accounting entries in the wip job, CT should do manual GL, because we can't recost txns.

Code fix:

=

Download and review the readme and pre-requisites for Patch.9502821:R12.BOM.C

File (include directory) Version

+ +-

Patch/115/sql/CSTLCWPB.pls 120.1.12010000.2

Patch/115/manualsteps/ad_apply_patch.xml 120.4

Patch/115/sql/CSTPACPB.pls 120.1.12010000.2

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.