Hello Everyone,
Can anyone please help on this? I am not able to upload data on SKU level in UX page.
Thanks
@Shitanshu
I don't think you need to upload anything instead it's a calculated module. This module needs to be dimensioned by SKUs, Time and calculate the values based off of the logic given.
Misbah
Miz Logix
In Activity it says P3 SKU Autoagreegation P1 Product Family, However in my case it didn't autoagreegate. Do you think I missing anything while mapping?
Please advise.
Thank you.
I think the calculations and formula is fine. It is doing what it is supposed to do (auto-aggregating) as I see there are numbers in here. I would say please check exception count line in INV01 module if you feel that there is a discrepancy in numbers.
Thanks,
@Misbah I created two Two grids successfully as per the activity however I need SKU In 3rd Grid to finish the activity. I checked the exception count line in INV01 module and I don't think any discrepancies.
Great! Go ahead and create that module which will be dimensioned by SKU and TIME and do the calcs.
@Misbah Do I need to Create New Module for that, I thought it suppose to come with INV02 Country Summary only according to the activity.🤔
INV02 is not dimensioned by Products, it is dimensioned by Product Family. So you will have to create another module INV03
@Misbah I just created the module as per the activity where it says Dimension - P1 Product Family List and it would autoagreegate the sku. I saw your response on one of the post.
Auto aggregation happens from bottom to top not from top to bottom. For example P3 SKUs can aggregate to P2 Products and P2 Products can aggregate to P1 Product family.
Now if your module is dimensioned by P1 it can not aggregate to P2 or P3. It's the other way around.
Hope that helps,
@Misbah Thanks for explainging and I got your point, so everybody go through the same way I guess. I will simply create seprate module for sku grid. Hope it won't impact on my sprint exam.
Thank you once again.
Hi,
I might be a bit late to this discussion, but for anyone referring to this later, I think there’s no strict need to create a separate INV03 module for this activity.
You can directly use INV01 Inventory Ordering and keep only the Safety Stock Exception Count line item for the SKU level grid in the UX page. This approach also aligns with using INV01 for SKU level details as mentioned in similar discussions.
I believe creating a new module (INV03) mainly makes sense only when there’s a dimensional difference or a clear reuse requirement. Otherwise, it just adds unnecessary complexity and extra maintenance effort.
Check out the latest Anaplan feature updates and enhancements in our April 2026 official release notes. There you'll find information on: Polaris Trigonometry functions MOVINGSUM on general lists Line item limit Security and tenant administration CAPTCHA on basic authentication Anaplan XL (version 2604) Offline writeback…
If you missed our April 29, 2026 platform release event, the recording is now available! In this webinar, we highlighted the most recent feature releases and how to take advantage of these in your environment. Our expert-led session demonstrated new features and innovations, provided a technical deep-dive and “how-to”,…