KayZed
Member
Hi,
I would like to see if anyone has had this issue before and any resolution. I couldn't find any fixes on Oracle Support. It looks like a genuine bug but our extended support has expired and we cant log it as a bug with Oracle. If this is affecting someone else, and has extended support, please take this up with Oracle and we all can benefit from it.
>>> Problem Description:
(JDE 8.12, Tools 8.98.3.4, Windows Server 2003 R2, MS SQlServer 2005)
We have had incidences where the cost has overblown and exceeds the database numeric limitations in the GL. We had to reverse out transactions, fix up GL amounts and Item Ledger amounts via SQL to get the system going again.
The issue is caused by weighted average cost runaways and traced the cause to the weighted average calculation with the following scenario which often occurs in our environment.
Currently the workaround is to advise users to not enter in and out to the same location in a single transaction.
>>> How to Replicate the Issue
We have tried this in Pristine and the miscalculation still occurs.
1.Create a Item Number = CHV9 and Inventory Cost Level = 3 using P4101
2.Create Item Branch Branch = 30 and Item Number = CHV9 Setup 4 locations
1.A.1
1.A.2
1.B.1
1.B.2
3. Enter an inventory adjustment transaction to adjust qty on hand for location 1.A.1 to 5000 units with unit cost of 1.00. The weighted average cost for 1.A.1 should now be 1.00 (as expected, this sets up the base scenario)
4.Enter a single inventory transfer transaction with the following lines.
a. CHV9 qty 1000 from location 1.A.1 to location 1.A.2
b. CHV9 qty 800 from location 1.A.2 to location 1.B.1
c. CHV9 qty 200 from location 1.A.2 to location 1.B.2
5.Check weighted average cost for these locations.
1.A.1 = 1.00 (as expected)
1.A.2 = 5.00 (not as expected) (would expect 1.00)
1.B.1 = 0.00 (not as expected) (would expect 1.00)
1.B.2 = 0.00 (not as expected) (would expect 1.00)
Weighted average calculation is incorrect when transferring the qty from one location to another within the same B/P for the item in a single transaction. If these transactions in step 4 is entered in separate transactions, the calculations will be correct.
--------
I would like to see if anyone has had this issue before and any resolution. I couldn't find any fixes on Oracle Support. It looks like a genuine bug but our extended support has expired and we cant log it as a bug with Oracle. If this is affecting someone else, and has extended support, please take this up with Oracle and we all can benefit from it.
>>> Problem Description:
(JDE 8.12, Tools 8.98.3.4, Windows Server 2003 R2, MS SQlServer 2005)
We have had incidences where the cost has overblown and exceeds the database numeric limitations in the GL. We had to reverse out transactions, fix up GL amounts and Item Ledger amounts via SQL to get the system going again.
The issue is caused by weighted average cost runaways and traced the cause to the weighted average calculation with the following scenario which often occurs in our environment.
Currently the workaround is to advise users to not enter in and out to the same location in a single transaction.
>>> How to Replicate the Issue
We have tried this in Pristine and the miscalculation still occurs.
1.Create a Item Number = CHV9 and Inventory Cost Level = 3 using P4101
2.Create Item Branch Branch = 30 and Item Number = CHV9 Setup 4 locations
1.A.1
1.A.2
1.B.1
1.B.2
3. Enter an inventory adjustment transaction to adjust qty on hand for location 1.A.1 to 5000 units with unit cost of 1.00. The weighted average cost for 1.A.1 should now be 1.00 (as expected, this sets up the base scenario)
4.Enter a single inventory transfer transaction with the following lines.
a. CHV9 qty 1000 from location 1.A.1 to location 1.A.2
b. CHV9 qty 800 from location 1.A.2 to location 1.B.1
c. CHV9 qty 200 from location 1.A.2 to location 1.B.2
5.Check weighted average cost for these locations.
1.A.1 = 1.00 (as expected)
1.A.2 = 5.00 (not as expected) (would expect 1.00)
1.B.1 = 0.00 (not as expected) (would expect 1.00)
1.B.2 = 0.00 (not as expected) (would expect 1.00)
Weighted average calculation is incorrect when transferring the qty from one location to another within the same B/P for the item in a single transaction. If these transactions in step 4 is entered in separate transactions, the calculations will be correct.
--------