Sage 100

S/O line promise dates periodically not being updated from ship date Client running MAS 200 4.5.3 is periodically experiencing some Sales Orders where they update the Ship Date on the main S/O Entry screen, but it's not correctly updating all the Line promise dates. And for the 1 particular order that I'm working with where I can actually re-create this issue, changing the Ship Date only correctly updates the 1st line item's promise date (which happens to be a Kit item). All other line (components, kits, items) promise dates remain unchanged. This order also happens to have /C's for the first 2 lines, but upon manually replicating the lines via a new order, I couldn't re-create the issue. HOWEVER, if I simply create a new Order by ""copying"" from the problematic order, and then change the Ship Date, it correctly updates all the Line promise dates. It's interesting that the issue doesn't occur in this ""copying"" scenario, but I'm not sure what that's telling us. Did something in the Order get ""rebuilt/reindexed"" upon copying? At this point it doesn't appear to have anything to do with whether the order was created directly in S/O Entry or from within Sage CRM, nor does it appear to have to do with whether it's a Standard Order or Quote, or a Quote that was converted to a Standard Order. And Rebuilding Keys / Sorts didn't help, and I didn't see anything in DFDM that might be causing this. Haven't been able to isolate the issue as of yet, so we haven't been able to determine any rhyme or reason - and I'm waiting for the client to get back to me with at least 2 more Sales Orders where this is happening - in hopes that'll help to find some consistency.

If you change the ship date on the main tab in SO entry, it does not update line dates that are already there. I believe it's always been that way, the logic being that you can change the promise date on the lines tab so if you change the header ship date, would you really want to update the individual promise dates already entered?

You could do that with an event script on the Ship Date field.

+1 on @ThereseLogeais 's answer. I'm a little confused as to why it seems that some of the lines promise dates are being updated, though. But that's a good idea @DanBurleson .

Thank you but on the contrary, @ThereseLogeais and @BrettLyder, I'm pretty sure the logic that has always been there is that when you change the Ship Date, it flows thru to the Line Promise Dates (although I know in older versions it was somewhat problematic). I justed tested it again just to make sure I wasn't crazy. This allows you to update the Promise Dates all at once rather than doing them individually - which is especially useful when you have an Order with 100+ lines that need their Promise Dates adjusted. Having to always do that manually would be a bit of a nightmare for this client because a good portion of their Orders have lots and lots of lines.

Perhaps it worked so inconsistently that we just ""assumed"" that the individual lines would not update. I can see it both ways and always assumed that once the once the individual line had been overridden with a different date, that changing the header date had no affect on the detail line.

LOL! Wow, is it possible that we are all sort of right? I think if you manually overide the promise date on a line, then changing the ship date doesn't change the date.(I'm guessing it only changes the lines that have the same promise date as the current ship date.

Whew, I thought I was going crazy for a minute!! (Which is still a possibility...)

Just tested in v4.5.4. If you manually override the line, the new header date has no impact. Header date change only impacts those lines that defaulted from the header date.

So getting back to Brett's original issue, Brett, are you saying the line dates have NOT been changed and are not updating after changing the header ship date, even for non-kit items?

Nice collaboration!!! Waiting to hear back from the client as to whether they previously manually changed the Promise Dates of the lines that are now not being updated when they change the Header Ship Date. Anyone know off-hand where the system stores the flag that says whether the Promise Date has been manually changed previously? And if this is the case, I'm guessing they'll next want to know how they can then re-change all those Promise Dates (on 100+ lines). Easiest might be: Copy-Paste-down arrow, Paste-down arrow, Paste-down arrow...

I don't see any 'promise date overridden field' so I'm wondering if it isn't what @BrettLyder said - it only changes lines with the original ship date?

An idea @BrettZimmerman - check the Sales Order History files for a flag - provided the the customer is retaining sales order history.

My recollection is that in prior versions, editing the header ship date would change line promise dates as long as you had not previously edited the line promise date. Once edited, changing header had no impact on line.

There does not appear to be a flag in any file that says whether the Promise Date has been changed previously; it just seems like there's some programmatic logic that simply compares Ship Date vs. Promise Date. And therefore, as seems to be the concensus now in this thread, changing the Ship Date will only impact the line promise date if the promise date has not been previously changed. HOWEVER, it appears it goes one step further because even if a promise date had been previously changed, but has since been changed again and now matches the Ship Date, changing the Ship Date now ""will"" impact that promise date. So for example, if I enter a sales order with a 7-11-12 Ship Date which obviously flows to the line promise dates, and then I change one of those promise dates, changing the Ship Date will only impact the lines without a changed promise date (as expected). But if I then change that promise date again - to match what the Ship Date currently says - and then change the Ship Date again, it'll update ""all"" the promise dates - even the one I had previously changed. I found this KB write-up which seems to reiterate this, except for the part that the promise date will be impacted if it matches the Ship Date even after the promise date was previously changed. (http://infosource.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=406575).

Got some new information on this issue. Apparently it's specific to converting a Quote to a Standard Order: In 4.40.0.6 & .7 (unsure about other versions) when changing a Quote to a Standard Order, the Ship Date reverts back to the original Order Date. But now in 4.5, the Ship Date changes to today's date / system date. And in both 4.40 and 4.5, the line Promise Dates will now show as the Order Date. However, in the 4.5 scenario (assuming the Quote was changed to a Standard Order on a different day than the Order Date), this makes the Ship Date no longer match the Promise Dates, so therefore making a change to the Ship Date does not correctly update the Promise Dates - whereas it did in 4.40. A workaround for this appears to be to change the Ship Date (after changing from Quote to Standard Order) back to what it was so that it matches the Promise Dates, tab out of the Ship Date field, then change the Ship Date to what is desired - and that should update the Promise Dates.