My Oracle Support Banner

FAW|FDIP|FDI - SCM - Inventory Valuations.Accounted On-Hand Amount Default Aggregate Not Correct (Doc ID 3040675.1)

Last updated on AUGUST 13, 2024

Applies to:

Fusion Data Intelligence - Version N/A and later
Information in this document applies to any platform.

Goal

Data Validation/Mismatch

ACTUAL BEHAVIOR
---------------
SCM - Inventory Valuations.Accounted On-Hand Amount default aggregate not correct

Subject Area: SCM - Inventory Valuations
Folder: Facts - Cost Currency
Measure: Costed On-Hand Amount
This was first noticed via Data Validation screens but can be seen via OAC project writing screens as well.
Create a table visualization with 3 fields:
(1) [Cost Organization Book Details] Cost Organization
(2) [Cost Organization Book Details] Cost Book
(3) [Facts - Cost Currency] Costed On-Hand Amount
In the filter bar add [Time] Fiscal Period.
If multiple Fiscal Periods are selected the resulting value will be the LAST period. This looks to be the default behavior in 22.R4. See data lineage metric calculation: https://docs.oracle.com/en/cloud/saas/analytics/22r4/fascm/chapter-data-lineage.html
Last(Sum(IfNull(IfNull(IfNull(Standard Cost, Perp Average Cost), Vu Unit Cost),0.0) * Quantity Onhand) By Fiscal Calendar)
If you right click on the 'Costed On-Hand Amount' and change the Aggregate from 'Auto' to 'Sum' then the query changes and gives you the proper SUM. Look at the current data lineage metric calculation:
Sum(IfNull(IfNull(IfNull(Standard Cost, Perp Average Cost), Vu Unit Cost),0.0) * Quantity Onhand)
Why is this measure using "LAST"? This measure won't be able to be used very well in the data validation screens if LAST is the default behavior.

Solution

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