Uniqueness

To support the mass configuration of staffing requirements across an enterprise, you must define distribution types. The types must be:

• applicable to distributions defined across all stores
• unique within a store and the store’s hierarchy

Distribution types need to be unique in your store in order for complex screens (such as staffing requirements) to work properly and to enable you to identify a specific distribution by referencing a distribution type. For example, you could update all requirements for hardware sales across all stores because their unique distribution types allow you to specifically identify them.

Some entity types have a location anchor point. (For example, activities.) When this location is specified at the regional level (rather than the Parent level), only stores within the specified region can see that activity.

Distribution types have a location anchor point as well. They can exist at the store level or higher (region, district, entire enterprise). Distribution types need to be unique in your hierarchy because, when a distribution type has an anchor point at a level higher than store, you cannot add a distribution with that distribution type at a level lower in the hierarchy.