Skip to main content
juil. 16, 2018 1:12 PM UTC
New Idea

Demand re-alignment

If you want to plan with new hierarchy as of a certain point in time in the future, the system must realign the data for the demand history of the affected skus.

If, for example, you change the entry location within your hierarchy, your hierarchy changes. Due to this change, the demands of the previous and new entry locations may change. For each location product of the hierarchy, the system must create a demand history up to the point at which the new hierarchy is valid and a demand history as of the point at which the new hierarchy is valid.

    2 commentaires

    oct. 24, 2018 11:39 AM UTC
    Status changed to: New Idea

    Hi Travis,

     

    Can you please explain with an example.  Demand is supposed to be captured at the location where it got generated. Then if we change the hierarchy, SPM accordingly changes the rollup of child location's demand(i.e replenishment or internal stream) accordingly to new hierarchy when it is in effect. Is that what you are talking about?

     

    Thanks,

    -Jai

    DSPMAuteur
    juin 6, 2022 1:01 PM UTC

    hello Jai,

     

    Wanted to revisit this topic and see I never did share an example.  We currently collect demand on a dealer location in Mississippi against our Atlanta Georgia distribution center for example and do all our planning accordingly.  Because of some changes, the business would now like to to service this Mississippi dealer from our Dallas Texas distribution center.  We would like all the demand for this dealer transferred from the Atlanta DC to the Dallas DC for future forecasting and planning purposes.  Hope this helps and makes sense.