Hi Sreenu,
Consider you have a plant and 2 DC.
The demand from DC is as follows:
Period : 1 2 3 4 5 6 7 8 9 10
DC1 Dmd: 5 4 6 6 3 7 8 4 0 6
DC2 Dmd: 4 5 7 5 4 6 9 5 4 3
Plant supply: 8 9 9 8 7 8 6 9 8 8
Pull deployment horizon: Time window during which planned distribution demand is confirmed. The demand categories (what constitutes of your distribution demand) are represented by ATD Issues (category group). Assume your pull deployment horizon is 7 periods.
Then, your planned distribution demand will be
Period : 1 2 3 4 5 6 7
Dmd: 9 9 13 11 7 13 17
Push deployment horizon: Time window during which eligible supplies can be used to confirm planned distribution demand. The categories of supplies are represented by ATD Receipts category group. Assume your push deployment horizon is 5 periods.
Period : 1 2 3 4 5
Supply : 8 9 9 8 7
Deployment horizon: Time window considered by the deployment engine to execute deployment run. Outside of the horizon, the engine does not take account of the demand and supply in its execution. Consider your deployment horizon is 5 days.
The demand and supplies considered for the deployment as follows:
Period : 1 2 3 4 5
Supply : 8 9 9 8 7
Typically, in interactive planning, your data view's future TB profile will represent the deployment horizon. For background execution, you can specify the deployment horizon flexibly.
Thanks,
Rajesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.