千家信息网

WIP Completion Return Wrong value

发表于:2025-02-14 作者:千家信息网编辑
千家信息网最后更新 2025年02月14日,Wrong Value In Accounting Of Wip Completion Return Transaction (文档 ID 1101430.1)In this DocumentSymp
千家信息网最后更新 2025年02月14日WIP Completion Return Wrong value

Wrong Value In Accounting Of Wip Completion Return Transaction (文档 ID 1101430.1)

In this Document


Symptoms

Cause

Solution

References


Applies to:

Oracle Cost Management - Version 12.1.1 and later
Information in this document applies to any platform.
***Checked for relevance on 03-JUN-2013***

Symptoms


On : 12.1.1 version, Costing Transaction Errors

Find Wrong value in accounting of WIP completion return transaction and the unit cost has been wrongly calculated.


Issue verified as below:


ITEM_ID ORG_ID WIP_ENTITY_ID
23040 277 18069
-----------------------------------------
Transaction ID: 1467130 - WIP Assembly Return transaction (Creation Date: 02/24/2010 15:15:31)
TRX_QTY VARIANCE_AMOUNT ACTUAL_COST PRIOR_COST NEW_COST
-1,000 -104,228,197 104,333 35 0
Transaction Date:02/24/2010 15:13:21


Find a discrepancy in the creation of the transactions. Note that the WIP
assembly return has a transaction id smaller than the WIP completion though the creation times differ in this aspect.

Cause


In this case, the txn id of completion is larger than return txn. So, in processing return txn, the prior completion qty was zero. That made the return value so big and hit variance account for the discrepancy btw returned value and reduced inventory value.




This is explained in the following bug:
Bug 9502821> - WRONG VALUE IN ACCOUNTING OF WIP COMPLETION RETURN TRANSACTION

Solution


To implement the solution, please execute the following steps:

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


2. Ensure that you have taken a backup of your system before applying the recommended patch.

3. Apply the patch in a test environment.

4. Confirm the following file versions:
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

5. Retest the issue.

6. Migrate the solution as appropriate to other environments.

0