溫馨提示×

溫馨提示×

您好,登錄后才能下訂單哦!

密碼登錄×
登錄注冊×
其他方式登錄
點擊 登錄注冊 即表示同意《億速云用戶服務條款》

WIP Completion Return Wrong value

發(fā)布時間:2020-08-17 16:40:39 來源:ITPUB博客 閱讀:165 作者:chenshm329 欄目:大數(shù)據(jù)

      <thead id="atk6o"><kbd id="atk6o"></kbd></thead>

        <i id="atk6o"><input id="atk6o"></input></i>


        1. Wrong Value In Accounting Of Wip Completion Return Transaction (文檔 ID 1101430.1) WIP Completion Return Wrong value

          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 <Patch 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.

          向AI問一下細節(jié)

          免責聲明:本站發(fā)布的內容(圖片、視頻和文字)以原創(chuàng)、轉載和分享為主,文章觀點不代表本網(wǎng)站立場,如果涉及侵權請聯(lián)系站長郵箱:is@yisu.com進行舉報,并提供相關證據(jù),一經查實,將立刻刪除涉嫌侵權內容。

          AI