WIPReturnCost

In this Document

成都创新互联长期为超过千家客户提供的网站建设服务，团队从业经验10年，关注不同地域、不同群体，并针对不同对象提供差异化的产品和服务；打造开放共赢平台，与合作伙伴共同营造健康的互联网生态环境。为余姚企业提供专业的网站制作、网站建设，余姚网站改版等技术服务。拥有10余年丰富建站经验和众多成功案例,为您定制开发。

Applies to:

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 100 Quantity.
later on "user" did a "WIP Completion Return" of 100 Quantity for the same job, this time system picked unit cost "22,942.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