Sage 300

 View Only
  • 1.  Hi All -Just upgraded a site that uses Order Ent

    Posted 05-12-2015 06:26
    Hi All - Just upgraded a site that uses Order Entry ALOT. They moved from 6.0 to 2014. Now in 2014 they are enjoying all the new features except the Deliver By date on the order header and line item details. Seems any old orders prior to the upgrade give a warning about the ship date being different than the delivery date. Anyone have any insight on how / what to do here? I know the issue will wane as the old orders get shipped out or canceled over the next month, but its an annoyance now and also something that i'd like to avoid on the next customer upgrade. Any ideas?


  • 2.  RE: Hi All -Just upgraded a site that uses Order Ent

    Posted 05-12-2015 06:34
    Marc - we just used SQL and did an update on all of the old orders setting the Deliver By Date = Expected Ship Date for all of the open line items in OEORDD.


  • 3.  RE: Hi All -Just upgraded a site that uses Order Ent

    Posted 05-12-2015 06:46
    Thank you @LloydSmith that is a great idea! I'll go about updating them that way.


  • 4.  RE: Hi All -Just upgraded a site that uses Order Ent

    Posted 05-12-2015 06:56
    Just finished and that worked great. Here is the sql I used for the detail line update: update OEORDD set oeordd.requesdate=oeordd.expdate where oeordd.COMPLETE = 0


  • 5.  RE: Hi All -Just upgraded a site that uses Order Ent

    Posted 05-12-2015 08:36
    Not very elegant, but here is the sql for updating the order header field too: UPDATE OEORDH1 SET REQUESDATE = (SELECT EXPDATE FROM OEORDH WHERE (oeordh1.orduniq = ORDUNIQ)) WHERE (ORDUNIQ = (SELECT ORDUNIQ FROM OEORDH AS OEORDH_1 WHERE (OEORDH1.ORDUNIQ = ORDUNIQ))) The date mismatch on the header fields of older orders ~appears~ to be what triggers the message box (but i'm not sure). This one updates ALL the records not just the non-complete orders.