Level 2 - Sprint 1

In the activities, we were to import into SYS07 - Location Details and SYS12 - SKU Details.

The Distribution Center for the above were loaded. As they both appear to be independent, does it mean that there is always a chance of mismatch between them?

E.g. In SYS12, Chicago is selected but in SYS07, it is not selected.

If this is so, how can these two be integrated so resolve possibility of such occurrence.

I am a newbie and just checking my understanding.

Comments

davidmccarty

Hi @lps - A bit confused by your question as I don't have any SKUs in SYS12 - SKU Details module with "Chicago" as their Distribution Center. Is your concern that a user could select Chicago as a Distribution Center location in SYS12 and then SYS12 would be out of sync with SYS07?

Misbah

@lps

Distribution centres that are marked as booleans can be used to create a subset of. As long as you are using that subset in the formatting of line items in SYS 12 module it is never going to throw you off.

einas.ibrahim

Hi @lps

You are worried that Chicago - which is not a distribution center (SYS07) - could be inputted as the distribution center to one of the SKUs in SYS12.
This is a very valid concern, however, since these are System Modules, they are not intended to be accessible to the End User.
If you want the user to add a new SKU and assign a distribution center for it or update the distribution center for an existing SKU then when you create that output module, you should format the Distribution Center Line item in that module as a list. This list is the Distribution Center subset list.

This is how you ensure the integration of the data in Anaplan.

lps

@einas.ibrahim
Yes, that's exactly my concern.

The examples given were from the activities in the Data Hub model.

lps

David, yes, you are spot on with the concern. As data for both of these are imported, this leaves a potential for out-of-sync.
I am aware that in a spoke Model, e.g. Supply Chain, subsets can be defined and thus eliminating the out-of-sync issue.

There seems to be a potential for out-of-sync in Data Hub model as these are imported in SYS07 and SYS12. Please refer to @einas.ibrahim 's reply.
I would like to hear from those who are experienced if importing this way is a best practice and what are the reasons not to define Distribution Center as subsets in a Data Hub model?

Below is the activity for SYS12 from Level 2 - Sprint 1 - Data Hub

einas.ibrahim

@lps

Here is the best practice answer:

There are 2 issues in play here:

1. Why not build the subset in the datahub?

2. The integrity of the data

For the first point, it is best practice to build subsets in the spoke model and not in the datahub. It is best practice to import to lists from saved views and not other lists in the Datahub. So if you create the subset list in the datahub how will you access it in the spoke model according to best practice?

For the data integrity issue, remember this is the Datahub. No user will have access to it, so changes to the data are limited to imports and actions. If your imports are wrong - assigning Chicago to an SKU - then there is a bigger issue that should be addressed outside of Anaplan. According to the Anaplan Way, "Cleaning" the data is a process done by the customer and should be finished before model building starts.

Quick Links

Recent release news

November 2025 platform releases and what’s next
Check out the latest Anaplan feature updates and enhancements in our November 2025 official release notes. The information below offers supplemental information to that post. Intelligence Anaplan Forecaster: General enhancements Anaplan Forecaster now supports list subsets for the item ID list and custom time, list format…
October 2025 platform releases and what’s next
Check out the latest Anaplan feature updates and enhancements in our October 2025 official release notes. The information below offers supplemental information to that post. Planning experience Combined Grids This new capability gives page builders the ability to combine multiple modules into a single, unified grid on a UX…