SAFE HARBOR
Coming soon to Kinetic 2024.1 is a new feature I know will be popular because I have heard it in discussions (even though hardly any of you voted for it in Epicor Ideas ERP-I-1761
Here is a little video demonstration of the new feature… note that while I only demonstrated it at the order header level, it also does this for the Order Detail and Order Release.
10 Likes
Will this take the new 2023.2 shipping calendar into consideration? Example: Delivery Days = 2, but exactly two days would be a Sunday. If I had a shipping calendar entered, that indicates to avoid weekends, would it back the shipment up to Friday?
Yes the new delivery days features interacts with the shipping calendar, and will throw warning/error if the calculated date falls on a non-shipping date.
2 Likes
Are we getting a new-style Navigation Tree in 2024.1? The one in the video looks really nice - looks much cleaner and easier to navigate.
Edit: just saw the post announcing it 
1 Like
@timshuwy So this is the same as what EDI has had in the past, just now pushed for all orders?
1 Like
not sure that it works exactly the same as EDI, but it does calculate when entering orders.
This already works for EDI customers/orders. You can set the delivery days at the Customer, and also the Ship To level. Will this also let you set delivery days at the ship to level?
e: Whoops thanks!
He shows in the demo that he is working in Customer Ship To.
3 Likes
I don’t suppose periodicity works too?
Is there a way to turn this feature off in 2024.1?
1 Like
there is nothing built in, but it could probably be done with a simple BPM…
After you change the need by date, there are two processes called. The first one is the Validate Shipping date. I would first try to associate a BPM to interrupt what is happening there.
Thanks for letting me know so quickly. I’ll see if we intercept this event.
Genius! Further enhancements to this date calculation should have the option to factor in how we are shipping it, from the ship-via. For example, FedEx Overnight, versus standard FedEx ground. Food for thought.
1 Like
We are testing this in 2024.1 and finding that it works for both order header and order dtl if you populate the order header need by date first. However, if we leave the order header Need by date blank and create an order detail record and enter the need by date at the line/detail level the ship by date on the order dtl record does not populate.
Please report this. It should work correctly.
2 Likes
I’m not going to use this right now, but will in the future. Thank you Tim, for putting 2024.1 and Delivery Days in the title - should make it easy to find in the future. Probably one of the most frustrating things is knowing I saw something here and spending way too much time trying to find the right words to find the post. Of course, that’s a good thing - means there’s a lot of info here!
Happy 4th to all the US-based members!
1 Like
For anyone interested, to disable this feature to auto calculate the RequestDate (Ship By), I found a post about an override hook, so I created an override event to cancel the original event ChangeRequestDate.
This is nice and easy for Kinetic (web), but we have users still on classic, any thoughts on how to handle there?
I think maybe, catch when NeedByDate changes (pre-processing), save the value for RequestDate, then in NeedByDate post-processing restore the request date.
ShipBy/NeedBy…yuck.
EDI customers that send a requested ship date…nice, terrific, makes it easy.
EDI customers that send a requested delivery date? Fuhgeddaboudit. Way too many variables to really get the NeedBy right.
1 Like