cancel
Showing results for 
Search instead for 
Did you mean: 

Non cumulative measure in Datasphere

murali_balreddy2
Active Participant
0 Kudos
1,011

Working with non cumulative measure in an analytic model. Stock movements by itself shows correctly in the date hierarchy.  

murali_balreddy2_0-1714582720751.png

 

But the non cumulative stock level does not show up correctly. It just shows the latest value for all nodes of the date period. Expectation is to show the stock level at node level by period (movement doesn't show up when both measures are displayed)

murali_balreddy2_1-1714582864145.png

Here is the definition of the non-cumulative measure, Stock Level

murali_balreddy2_2-1714583000879.png

Sample data used =>

DateProductMovementRecord Type
2022-12-07BX-1011-162
2022-12-10BX-1011122
2022-12-14BX-1011192
2022-12-31BX-10113901
2023-01-09BX-1011-80
2023-01-14BX-1011-130
2023-01-15BX-1011-160
2023-01-18BX-1011170
2023-01-22BX-1011-100
2023-02-03BX-1011110
2023-02-06BX-1011250
2023-02-07BX-1011-200
2023-02-08BX-1011-90
2023-02-12BX-1011200
2023-02-15BX-101190
2023-02-17BX-1011110
2023-02-20BX-1011250
2023-02-25BX-1011-200
2023-02-28BX-101140
2023-03-04BX-101170
2023-03-14BX-1011-50
2023-03-15BX-1011100
2023-03-21BX-1011200
2023-03-22BX-1011230
2023-03-25BX-101190
2023-03-29BX-1011-110
2023-03-30BX-1011-130

 

What am I doing wrong here?

Thanks.

0 Kudos
Hello, I am working on a new analytic model that uses Non-Cumulative Measures. I noticed that it does not work with the SAC Excel Addin. A colleague of mine could replicate this issue with a separate model. Is this a known issue?
Roberth_Reyes
Discoverer
0 Kudos

Hello,

 

I'm wondering with approach did you use to load the stock data from S4 to Datasphere? 

Thanks and regards.

Accepted Solutions (1)

Accepted Solutions (1)

tmeyer
Explorer

Hi,

I tested it with your example data and it works fine. I only had to adjust the time frame because it is different with your data vs. Screenshots

 

murali_balreddy2
Active Participant
0 Kudos

Thanks for pointing it out. My bad, I had the wrong reporting period than the data.

Answers (0)