In the past when we enter a sales order release need by date, the ship by date would populate automatically. I don’t think this was done by any directives (not any that I found). Is there a flag someplace that changed? Can we get this functionality back?
Thanks for your time!
In the 10.2 version, either field was calculated automatically by adding/subtracting non-zero delivery days.
I’m getting the same question from my users after 2024.1 update. No directives on our side.
1 Like
There is a new feature in 2024.1: Kinetic 2024.1 Feature Preview - Delivery Days
There could be an issue if calendars or Delivery Days fields are not set… I’d open a support ticket.
1 Like
I did create a ticket. It does work on the header level of the order but not the line or release. Appears there no ‘link’ between those fields at all any more. Any need by updates on the line or release does nothing on the ship by.
1 Like
the dates only stay aligned from the top down… so if the order header, order detail and order release all have the same date, then when you change the header, the detail and release will update. BUT… if you changed the RELEASE, then the Detail and header will not change. they will not resync until you manually make them all the same again.
1 Like
Not really concerned with the release or line updating up. The issue is changing the need by does not update the ship by on the same line or release level. I see directives in my future.
2 Likes
Same here. We just want the ship by to update to the need by date, like it used to.
2 Likes
The Ship By dates on the header and line level really only exist for the people using the system, Epicor itself does not use these dates for anything aside from the auto-population @timshuwy mentioned to make manual data entry easier.
I guess aside from trying to make data entry faster, putting a Ship By date on the header stops me from having to look at each individual release Ship By? Not sure this is a good idea anyway, a Ship By on an order header breaks down pretty quickly as soon as you have releases with different ship by dates on the same order.
As @Ernie mentioned, with the addition of the Needy By → Delivery Days → Ship By functionality that used to only be reserved for EDI orders now being applied to manually keyed in orders, it seems like these 2 ‘features’ are now bumping heads.
2 Likes
This is where the needs of the many different customers can conflict with the needs of the few.
- Some customers make complete orders… all lines have only one release, and all lines ship at the same time… orders must ship complete
- some customers have multiple lines, but only one release per line
- Some customers (like my former employer) create an order with one line, but many releases of the order
- then there are the really complex orders with many lines, and many releases per line.
In all but the first and second instance, the dates on the header help… but if you are a company that aligns to the last two, then the dates on the header may be totally useless, except to set the FIRST shipment date.
The good news is that you, as a company can choose to hide these fields if they don’t do any good for you. They are only really used as a default for new line items.
1 Like
The ShipBy date on the Sales Order Release… that is the date that MRP uses for any demand requirements (both direct purchase, job due date, and therefore materials on said jobs).
@NateS, you still on Classic forms?
From my ticket… "This is a Classic UI only issue. I can submit to development to review "
I tested and the Kinteic UI gives a prompt asking if you want to also update the Ship By.
1 Like
Yep, still stuck firmly in classic. I will ask our order entry person to try browser to see if it is still an issue.
1 Like