You should be able to validate that it is working by looking at the weeks, and the value should match the source that is input by Year. If you can validate that the intersections match the yearly input, then it is working properly.
Hello @jasonblinn , I am a having a really hard time understanding how using YEARVALUE will convert the years to weeks. From the documentation, I thought YEARVALUE just returns the aggregated values for the year. Therefore, to convert to weeks, I would think you would use YEARVALUE and then divide by 52. That seems like hard coding though. Please explain when you get the chance. Thank you!
You are right in saying that YEARVALUE takes the aggregated value of the years but you are not supposed to divide the numbers equally from Years to Weeks - so no need of hard coding it & dividing it with 52. What you are supposed to do is to get the year values from Source module (which is dimensioned by Years) and populate it in every week of that year in the target module - hence the need of YEARVALUE function.
Say for example if Shipping Time for Nutzo Bar using Air Mode is 1 for FY20, then the expectation is that number 1 be flat lined to every week of FY20. Every week of FY20 should reflect 1 in the line item.