Skip to Content
avatar image
Former Member

Short term deployment has changed

HI Experts,

The deployment is working correctly, the problem is that the push deployment horizon is set to 21 days, but orders that were 23 days in the future were being deployed.

I tested a sku this week where I changed the push deployment horizon to 18 days. This job was scheduled to run on Friday 15th March. On Thursday 21st February in the morning this order was not deployed, this morning (on Friday 22nd February) this job did get deployed for the first time. The horizon is set to 18 days, but from 22/02/13 to 15/03/13 is 21 days.

It seems that horizon is acting three days longer than stated in the master data.

How to correct it.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Feb 23, 2013 at 11:38 PM

    Hi Surya,

    Push deployment horizon, Pull deployment horizon, and deployment rules influence the deployment functionality. You mentioned only push horizon in your query which considers only the receipts at source that are eligible for deployment.

    Depending on your push deployment rules, for instance Push by demands, your entire ATD qty will be pushed to destination locations irrespective of demand dates.

    • Pull deployment horizon defines the period over which distribution demand (ATD issues) at source location should be considered.

    • Push deployment horizon defines the period over which supply available (ATD qty) at the source can be deployed.


    Add comment
    10|10000 characters needed characters exceeded

    • Hi Surya,

      Check mode influences GATP only.

      Push distribution rule X does not respect the pull deployment horizon and hence, the huge number 999 was set for pull deployment horizon. There might be a business reason for those settings you mentioned in your post.

      With these settings, the deployment engine tries to push all the supplies within 21 days (from today) to the destination locations in proportion to the demands at these locations.

      With Push by demands, the entire supply is distributed immediately to the demand locations for the entire planning horizon to cover all demands. The pull deployment horizon is ignored in this instance .

      Since there is not much information available about SNP planning (heuristics/CTM/optimizer), calendar changes, t.lane settings, etc, it's difficult to comment on why this issue appear for the first time with same settings that were in place for a long time.