Push by demand works as you mention for 5 days even if you don't like. The available qties are pushed out as soon they are available. See push horizon on source and pull horizon on destination also restrict the mentioned dates in calendar.
Thanks for your response. The fact is we are not using TLB in APO just deployment
1. We have transportation lane duration 5 days in APO.
2. In ECC Route time as defined as Transit time =5 days and Transportation planning lead time as 5 days.
3.Now when i create my STR in deployment example: my STR start date will be 24th May and end date will be 29th May. When it goes to ECC to convert to STO Route will take 10 days forward meaning
from 23rd till 5 days 28th is transportation planning time and transit time 5 days which is 28th may till 2nd june which is not in sink with APO.
After many discussions we found that if we restrict in deployment to stop creating STR for 5 days which is current day till 5 days then it should work.
SNP deployment does not consider stock transfer horizon. However, you can use SNP heuristics to generate STR out side of stock transfer horizon (in your case, STR horizon may be 5 days). These proposals can be further refined by deployment considering ATI and ATR quantities, push/pull deployment horizons, etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.