Level 2 - Conclusion - INV05 and DEM04 - Import with Subsidiary View

Highlighted
Occasional Contributor

Level 2 - Conclusion - INV05 and DEM04 - Import with Subsidiary View

Hi

In importing from INV05 and DEM04 (both having Subsidiary Views which are used for mapping) via 'Connect to Anaplan Model', I tried different Saved View pivotings until I successfully imported from a Saved View with no page selector.

Based on the various tries above, my observation is that the Saved View must not contain page selector in order such import to work.  I hope this is not the case due to the number of rows that can potentially be generated (row limit per module?).  Grateful for ideas from the community for further understanding 😊

 

15 REPLIES 15
Highlighted
Contributor

Re: Level 2 - Conclusion - INV05 and DEM04 - Import with Subsidiary View

Hi @lps 

 

What was the error that you were receiving when you tried the import from your original saved views? Would you be able to share some screenshots of your saved view and the mapping page of your import? You should be able to import with page selectors in your saved view. 

Highlighted
Occasional Contributor

Re: Level 2 - Conclusion - INV05 and DEM04 - Import with Subsidiary View

@smithevan18 

Below the screenshots.

E.g. DEM04

lps_1-1590588016214.png

 

FP&A model

The Location and SKU Codes are in Column 3.

lps_3-1590588457276.png

 

 

 

 

 

 

Highlighted
Contributor

Re: Level 2 - Conclusion - INV05 and DEM04 - Import with Subsidiary View

Hi @lps 

 

Thanks for providing the screenshots. In this situation, you will have to pivot your view slightly to get his import to work but you do not have to put all dimensions on the rows and columns. As you can see your location and SKU dimensions automatically dropdown to the rows in your import mapping. However, you will have to move your line items dimension to the columns because you have to map the dimensions in your target module to the line items in separate columns and you can't do that when they are in your rows. Additionally, you can move any combination of your other dimensions to the rows, but you don't need to pivot all of them down.

 

I hope this helps!

Highlighted
Occasional Contributor

Re: Level 2 - Conclusion - INV05 and DEM04 - Import with Subsidiary View

@smithevan18 

 

Below is the Saved As another view to be imported in FPA.  In FPA, only All Regions data are read (as per mapping screen) .  As expected, when this 'Run Import' was clicked, the import failed.  

 

lps_0-1590608587678.png

 

lps_1-1590608627704.png

 

 

 

 

 

 

Highlighted
Contributor

Re: Level 2 - Conclusion - INV05 and DEM04 - Import with Subsidiary View

Hi @lps

 

A best practice for saved views for exports is removing all upper levels of hierarchies. This might help with your export as you're missing codes for all your summary levels. I have created the following saved view in my Supply Chain model.

 

1. I hide all levels in the SKU and Location lists except the lowest level. You can do this by pivoting your dimensions to the rows and manually reselecting only the lowest level of each dimension. Then I pivoted the locations back up to page selectors. 

 

smithevan18_0-1590611730863.png

 

2. Put a filter on time to only show the months

smithevan18_1-1590611887153.png

3. Put a filter on the P3 SKU dimension to only show anything not equal to 0 

smithevan18_2-1590611935051.png

 

Now when I try and import into the FP&A model this is what the import screen looks like:

smithevan18_5-1590612266074.png

 

As you can see it is bringing in more than what is shown in the saved view as it is including all locations and months as well. This import ran successfully for me and imported all the necessary data. 

 

Highlighted
New Contributor

Re: Level 2 - Conclusion - INV05 and DEM04 - Import with Subsidiary View

Hi @smithevan18 ,

 

After doing all the steps you mentioned, I am still unable to get the desired line items as Columns in the mapping to import data into Data02 SKU Volumes and hence receiving a failure on import. Request your help to resolve this.

Highlighted
Contributor

Re: Level 2 - Conclusion - INV05 and DEM04 - Import with Subsidiary View

Hi @Karan.dhanak 

I would check to make sure your saved view saved correctly or that your import is selecting on the correct saved view. From your import screen, it looks like your time dimension is still on the columns. 

Thanks,

Evan

Highlighted
New Contributor

Re: Level 2 - Conclusion - INV05 and DEM04 - Import with Subsidiary View

Hi @smithevan18 ,

 

I created a new saved view and tried to import and it worked fine now.

 

However, I want to understand why didn't it work previously. Earlier, i just saved the layout like you had suggested as the default module layout and was importing from the module rather than create a new layout and import from saved layouts. Would that be causing the issues? If yes, I would like to understand the reasons.

 

Thanks in advance.

Highlighted
Contributor

Re: Level 2 - Conclusion - INV05 and DEM04 - Import with Subsidiary View

Hi @Karan.dhanak 

I'm not exactly sure why your import from the module didn't work if you saved the view as the default. It might be that the module import will import the original pivot no matter what the default saved view is. Either way, I would always recommend importing from a saved view, even if the saved view is the same as the default view. This is because the default view has a higher possibility of being changed by another user, while someone saving over the saved view is a lot less likely. Hope that helps!

Evan