My Oracle Support Banner

Cost Adjustment Not Considered During Pac Costing (Doc ID 755856.1)

Last updated on JUNE 07, 2021

Applies to:

Oracle Cost Management - Version 11.5.10.0 to 11.5.10.3 [Release 11.5]
Information in this document applies to any platform.

Symptoms

On 11.5.10 in Production:


1) There is a problem in Periodic Average Cost (PAC calculation). We have noted the cost is changed in a very "strange" way
for the item 036825 from 8,9€ to about 221€.
2) The PAC period related to 3rd Quarter 2008 is closed.
3) As of today we discovered a couple of items but we are not sure if other items are impacted.
This issue can affect our inventory valuation.

It's likely the problem started after installing patches 5838178 and 6597280 (and prerequisites).
The problem is related to items having different UOM between Primary and child  organization.
For instance, item 036825 has NR (number) as Primary UOM in Primary organization and MT (meters) in
child org .
The problem is in PAC calculation. We have noted the cost is changed in a very "strange" way, from
8,9€ to about 221€.
All transactions records are correct. The item is a "buy" item and no list price changed occurred.
You can see in attachment records in table CST_PAC_ITEM_COSTS for that item.
Also I send you screenshots of the receipt transactions for the item. Since conversion rate
between MT and NR is 76,22 for the item, you can notice that till a certain period layer
quantities in this table are in meters. After that period (and patches installation), layer
quantities are in NR. The unit of measure is not a field in the table.
According to me it's correct to have the Primary UOM of the Primary as the UOM considered in the
cost calculation. The reason is that in the same legal entity and cost group, the calculation
could include organizations with different UOMs. However the change in behavior occurred with
transactions and layers existing.
What happens is that in average cost calculation system mixes together a layer in MT with a new
one in numbers without conversions. This takes wrong values for PAC.
If ours is the correct explanation (please confirm) we need a datafix for existing layers and
items (not many items in that situation).


EXPECTED BEHAVIOR
Expect ...no problems with pac calculations

-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. NA


Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.