L2 Sprint 2 2.3.9.1 Import data DATA02 shipping metrics

Import Ignored most likely due to different dimensions. However I don't see anything in original excercise saying dimension should be weekly in the data hub module, please assist ?

DATA HUB it is Model calendar year

>> Time scale Year

In Supply chain this is based on time range.

>> Time scale Week

Supply Chain Module

Accepted answers

All comments

AjayM

Hi @akrem ,

Please set target module's time scale to YEAR (not WEEK). You can't import data from YEAR scale to WEEK scale. The action result might say ‘success’ considering the dimension mapping, but the columns got ignored as WEEK doesn't match with YEAR.

Cheers!

akrem

Hello,

I adjusted this in supply chain import worked. Is there any reason it was set to week instead of year in supply chain module ? There was no mention of adjusting this in tutorial for level 2.

» Changed to year then import worked

This is import result.

AjayM

As we proceed with exercises and levels of model building, not everything is explicitly detailed all the way, and we are expected to apply logical thinking, as we are getting used to the use case, purpose of each activity and the model building itself.

Whenever we create a new module with time dimension, it gets created with lowest time level (based on our model's time settings). And hence, by default, the module got created at week level in supply chain model.

Also, though it looks like it worked, I see another issue in your time setting of DAT02 in Supply Chain model. You have set it to time range FY19-20, while the shipping metrics data (DAT02) in data hub is for FY20 and FY21 years. This means you would be able to import data only for FY20, the common year between hub and supply chain model currently.
Please change your DAT02 time setting in supply chain model to model calendar, which gives you the correct years (FY20 and FY21), for successful complete import at this step.

Quick Links

Can you help?

Unanswered questions

ERROR 16020 |-- Anaplan API: Invalid key path
Hello everyone, We are trying to use Anaplan Connect in order to push data from a dwh to Anaplan Data Hub. To do so, we need an authentication by token. We can't make it work, we receive the following error: ERROR 16020 |-- Anaplan API: Invalid key path Any suggestions? Thank you all in advance for the help! Michele
AnaplanXL Difficulties
Has anyone found success using Anaplan XL with Polaris models in a shared drive with or without concurrent users? My team has experienced a variety of errors, login failures, etc. sometimes it works, sometimes it doesn't. We've been recommended to save and edit files locally, which helps but certainly with its limitations…
Looking for Anaplan End-Users to take a short survey!
We are looking for Anaplan end-users to provide feedback on their experiences with the Excel add-in. Interested individuals will respond to this 5-minute survey to help us understand personal needs and behavior when using the add-in. The feedback provided by survey takers is essential to the roadmap of Anaplan's products.…