L2 2.3.9.1 Import data into DAT03 - Issues with timescale & SKU list

Options
learncw1
learncw1 Member, ALL USERS Posts: 5 Occasional Contributor

Hello,

Been stuck in a loop for a while on this now - I can see a few other users have been caught out as well - so perhaps needs to be made more explicit in the guidance. 

 

I am having two problems. 

1. I do not understand how to map the timescales together

2. The SKUs lists between the two models are different - Did I do something wrong in the datahub?

 

 

Comments

  • learncw1
    learncw1 Member, ALL USERS Posts: 5 Occasional Contributor

    @JaredDolich Thank you very much. I have gone back through the end of Sprint 1 and imported the SKU details into the Supply Chain Model. Still stuck on the timeline however. 

     

    As far as I can see - I have attempted matched the dimensions of the target module of the source model.

    I have tried many different options for the time settings in the import file - but I keep getting variants of the same result, so clearly I have missed something fundamental.

     

    Thanks

    C

  • learncw1
    learncw1 Member, ALL USERS Posts: 5 Occasional Contributor

    @JaredDolich. Thank you for responding. 

     

    My time range matches the below. The DAT03 module export matches the requirements for 1.5.8.1. 

    When I apply the filter it shows the summary month columns as blank (this is the saved view which matches the requirement) if I switch off then reapply the filter the summary month column disappears. When I rerun the import action I still get the same error. 

     

    Any ideas?

    Thanks

    C

     

  • learncw1
    learncw1 Member, ALL USERS Posts: 5 Occasional Contributor

    Ah i think you have zeroed in on the source of the problem. 

    My calender settings in both models match the below. 

    So I have checked SYS01 has a Weeks Only line item - I think this is ok. 

    When I apply this as a  time filter in the DAT03 module - I just get blanks  - This is where I played with filter settings until I was able to match the requirement view rather than landing on the right solution.