About smithevan18

smithevan18 · ‎01-22-2021

HI @hpatel I believe this is because you are looking at "All Regions" in the L3 Location list in your import view, which shouldn't cause a problem with your import. When you run the import it should still import your demand values. However, if you want to make your import more efficient, I would remove all summary levels from your saved view. In your saved view, I would pivot your L3 locations down to your rows, and in "Select Levels to Show" I would uncheck all levels except the L3 Location Level. Then Pivot it back up to be a page selector and resave the view. You should then hopefully see the location and SKU codes in your import view.

smithevan18 · ‎09-22-2020

Hi @Rakesh_24_7 You shouldn't need the conditional portion of that formula because the PO submitted line item is already taking into account whether or not you've submitted a PO. You are only trying to move the value in PO Submitted by your shipping time in weeks. Hope that helps!

smithevan18 · ‎08-16-2020

Hi @kunal_311 What I meant by that was you have to hide all your summary levels by utilizing the "Select Levels to Show" functionality in Anaplan. You can only do that when your dimension is pivoted to your rows or columns. So you should pivot all your dimensions off of your page selectors and manually select just the lowest level of your hierarchy. Let me know if that helps clarify.

smithevan18 · ‎07-24-2020

Hi @sdavidko When you pull from a weekly timescale into a monthly timescale, if you have your summary methods turned on, Anaplan will automatically aggregate up to the monthly amount. So your monthly module (Dem 04) should be using the monthly data that is in your weekly module (DEM 03). I think you're potentially missing the sum on the locations dimension because that is the added dimension in your source module. Hope that helps!

smithevan18 · ‎07-24-2020

hi @sdavidko I would check your Demand formula. It looks like you have data in there that should be 0 for a lot of those SKUs. Hint, you might be missing a sum.

smithevan18 · ‎07-14-2020

@AntonMineev What is the dimension on the rows? And are you trying to filter out that entire row if all versions are 0? Or just filter out the versions that are all 0?

smithevan18 · ‎07-13-2020

Hi @AntonMineev I would use a boolean line item in a module that has versions as a dimension. That module can have just versions or any combination of dimensions (countries/brands) if you are trying to filter on underlying data. Then your formula would pull from your data module with a formula to say it's true if any of the intersections have data greater than 0. You should then be able to apply this filter to any module with those same dimensions. Hope that helps.

smithevan18 · ‎07-02-2020

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

smithevan18 · ‎07-01-2020

Hi @rdp284_1991 I would just flip your time and line item mappings. Set your time dimension to your column headers and your line items to a fixed line item and select Volumes from the dropdown on that mapping tab. Hopefully, that helps with your import. Thanks, Evan

smithevan18 · ‎07-01-2020

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

smithevan18 · ‎05-27-2020

Currently, there is an option to "Omit Summary Items" when you are exporting data designed to exclude parent hierarchies. However, there is no such option for imports and this requires users to create saved views that manually exclude parent levels and can cause a lot of manual work for model builders. Without removing parent levels the import will have several unnecessary failures/ignores. I know this will be successful when you can automatically remove summary levels from imports via a boolean checkbox in the import mapping screen.

smithevan18 · ‎05-27-2020

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. 2. Put a filter on time to only show the months 3. Put a filter on the P3 SKU dimension to only show anything not equal to 0 Now when I try and import into the FP&A model this is what the import screen looks like: 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.

smithevan18 · ‎05-27-2020

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!

smithevan18 · ‎05-26-2020

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.

smithevan18 · ‎05-21-2020

Hi @JenniferMontgomery Here is a way you can do it based on holding certain values constant and overriding others. In this example the East region is held constant, the South region is overridden, and the Central and West regions are allocated the remaining amount of the total initial target based on a percentage of their values to the total region. Therefore, your initial target total for USA is the same as the total for the region target. I'm assuming you could recreate this same functionality utilizing percentages instead of dollars. You could also try and utilize the breakback functionality but that doesn't work for percentages.

smithevan18 · ‎05-20-2020

Hi @Star, Post and Offset are very similar functions, however, they are going to give you very different results. Offset is going to give you the value from your selected line item x number of periods in the future or in the past. For example, in your line item Confirmed PO Delivery, week 6 is looking back 1 period (Final Shipping Time Weeks = -1) and resulting in your value of 1 since there is a 1 value in Confirmed PO Delivery in week 5. Post, on the other hand, is going to push the value from your selected line item x number of periods in the future or in the past. For example, in your module, the 1 value in week 5 in your Confirmed PO Delivery line is being pushed 2 periods into the future because that is value in your second argument in your function (Final Shipping Time Weeks = 2). This function also allows you to sum values if they point to the same period. For example, if you also had a 1 in the Confirmed PO Delivery line item for week 6 it would be pushed forward 1 week into your week 7 and combine with your 1 value from week 5 to give you a value of 2 in week 7. Offset will not let you combine values in the same way.

smithevan18 · ‎05-20-2020

Hi Star, Can you please include a screenshot with your "Final Shipping Time Weeks" line item? It looks like you are comparing it to your "Shipping Time Weeks" line item in your screenshots, which has 1 as the value, but your Final line item might have some other value and this is what you are including in your formula.